APIs and backends
REST APIs, auth and roles, payments, background jobs, the database schema under all of it.
Built before: FundOS, SCP Portal
I'm Yash, a backend and DevOps engineer in India. I take a small number of fixed-scope projects at a time. Work is split into priced milestones, and I invoice each one after you approve it.
REST APIs, auth and roles, payments, background jobs, the database schema under all of it.
Built before: FundOS, SCP Portal
Workers, D1, Durable Objects, R2 and Queues. Fast to run, cheap to host, no servers to patch.
Built before: Babel Room, BrainMCP, Angel OS
CI/CD, Docker, VPS setup, backups and uptime checks. Deploys you can run without me.
Built before: Vessel, Health Check
Admin panels and ops dashboards that replace the spreadsheet your team keeps fighting with.
LLM pipelines, MCP servers, and evals that pick a model on measured cost and accuracy.
CLIs, Git infrastructure and small utilities that remove one daily annoyance for your team.
30 minutes, free. You describe the problem, I ask about constraints.
Milestones, each with a deliverable, a date and a fixed price.
Updates on your project page as work lands, with preview links.
Each milestone is invoiced only after you approve it.
Code, docs and credentials, all in your accounts.
Every client gets a page at clients.yashlunawat.com showing:
A defined build with milestones and a fixed price for each. Most work fits here.
A set number of days each month for ongoing features, maintenance and on-call fixes.
A short, fixed engagement: I review your backend, infra or cloud bill and hand you a written report with the fixes ranked.
Prices are quoted after the first call, once I know the scope.
You do. The repository lives in your GitHub organisation and everything deploys to your own cloud accounts from the first day. Nothing is locked to me.
Each milestone has a price agreed in the written scope. When a milestone is done, you review it and approve it on your project page, and then I send the invoice. You can see every invoice and payment on the same page.
India, on IST. Calls can be scheduled for European or US hours, and most communication is written, so timezones matter less than you'd think.
Yes. Send it over before the first call if you'd like.
We add it as a new milestone with its own price, or swap it for one that hasn't started. The page shows the change, so nobody has to remember what was agreed.
Yes, if the scope is clear. A one-week fix or a deploy setup is a fine first project.
Tell me what you're building and where it's stuck. I reply within two working days.
Prefer email? hi@yashlunawat.com