Freelance · fixed scope

One engineer who owns it end to end.

Alongside my role at G2A I take on a small number of fixed-scope projects. You get the design, the code, the deployment and a clean handover from the same person, and a price agreed before the work starts.

Tell me about your projectEmail me

What I take on

  • Performance and reliability review

    A Rust or Go service that is slow, falls over under load or is hard to operate. I profile the real call path, find what matters and either fix it or hand you a prioritised plan your team can carry out.

    At G2A: 60–70 ms → 15–30 ms

  • A product backend in Rust

    The API and background workers for a new product, or a rewrite of one that grew out of control: Axum, SQLx and PostgreSQL, idempotent commands, an outbox for anything external, Stripe payments done properly.

    CrowdRelay and AhojBus

  • A fast website that does real work

    Static-first Astro that scores 100 in Lighthouse, with the dynamic parts that matter: a shop, payments, sign-ups, events. The page stays fast and keeps working when a backend is slow.

    virya.music, below

Case study

virya.music: a band website that became a small platform

It started as a fast, multilingual place for music, videos, concerts and press. Then came merch, a location-based game, fan accounts, concert reminders, draws and tickets with QR check-in.

The public pages stayed static-first in Astro and still score 100 in Lighthouse. Prices are checked on the server before a Stripe checkout exists, and payment is confirmed by the webhook, not the redirect. When the backend or a third party is slow, the pages still render.

Read how it was builtVisit virya.music
Virya website: “We are Virya”, a modern metalcore band from Poland

How a project runs

  1. 01

    Tell me about it

    What you have, what hurts and when you need it. A few paragraphs are enough.

  2. 02

    A short call

    Thirty minutes to check the fit and the real problem behind the request.

  3. 03

    A fixed proposal

    Scope, deliverables, price and timeline in writing. No open-ended hourly billing.

  4. 04

    Build in the open

    A working demo every week, so you see progress instead of status reports.

  5. 05

    Handover

    Code, documentation and a runbook in your repositories. You own everything.

The practical part

  • Fixed scope and price, agreed in writing before the work starts.
  • Invoiced B2B from Poland. Remote, CET (UTC+1/+2), in English or Polish.
  • A few projects at a time, so the start date depends on what's already booked. Ask.
Tell me about your project

Loading…