01 / Independent full-stack engineer

No fixed packages. One engineer stays responsible from the first conversation to launch — and after it.

The site, the admin panel, the app — built to fit your business.

Some businesses need a clean site that sells their service well. Others need bookings, payments, a staff panel and a mobile app. Both are normal work here: a small project gets the same care as a platform.

See the work
products live in production
4
projects built, awaiting launch
2
engineer from brief to production
1

Live now

Four products you can open and verify.

What I can build

Start with the result, not the technology list.

A useful first version can be small. The same collaboration can grow into the system that runs the business.

See services and proof

Selected work

Four live products. Open the cases and try the working screens.

Start with a real production surface, then use the safe interactive version to inspect the workflow without exposing private data.

In progress

Built, not launched.

These two projects are shown as work in progress: their case studies are real, but no public launch or business result is claimed.

Tools in production

The right stack follows the job.

Everything here already runs in the products above — chosen for the job and for the people who will maintain the result.

Web product

  • Next.js
  • React
  • TypeScript
  • Vercel

Backend & operations

  • FastAPI
  • PostgreSQL
  • Strapi
  • Resend

Growth

  • Meta
  • Google Ads
  • Google Analytics
  • PostHog

Mobile & desktop

  • Kotlin
  • SwiftUI
  • Tauri
  • Telegram

Working together

From a first call to a launched product.

01

Understand the work first

We start from how the business actually runs: who does what, where time is lost and what must never break.

02

Right-size the solution

You get the smallest version that solves the problem, and a clear picture of what it can grow into later.

03

Build and launch

Working software early, honest progress along the way, and a launch on real infrastructure — with tests wherever money or data is involved.

04

Stay close after launch

The products on this site run daily without a developer on call. Support, improvements or a clean handover — whatever fits.

About

I build the whole system, then stay close enough to see it run.

My work spans product, frontend, backend, data and operations. That range matters when a payment callback changes an admin screen, a report changes a campaign, or a staff habit should change the interface.

The projects here are live: a yoga studio platform, an online game’s live-ops stack, an indie publisher storefront and a cafe’s banquet builder.

I prefer few dependencies, explicit rules and software a non-technical team can run without a developer on call.