Game live-ops platform
Calamity
One platform runs the game’s analytics, campaigns, updates and player tools — no rented services.
- 141 API endpoints
- 16 analytics tables, 0 SaaS
- 14 languages auto-translated
01 / Independent full-stack engineer
No fixed packages. One engineer stays responsible from the first conversation to launch — and after it.
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 workWhat I can build
A useful first version can be small. The same collaboration can grow into the system that runs the business.
Selected work
Each case shows what the business needed, what was built and what changed — with the real interfaces recreated on the page, not screenshots.
Game live-ops platform
One platform runs the game’s analytics, campaigns, updates and player tools — no rented services.
Business platform
The studio’s website, payments, reception admin, two native apps and a Telegram bot work as one product.
Publisher site & release outreach
A console games storefront that also collects developer pitches and builds the press list for releases.
Banquet menu builder
Guests assemble their own banquet order from the real menu and send it straight to the cafe’s Viber.
Tools in production
Everything here already runs in the products above — chosen for the job and for the people who will maintain the result.
Working together
We start from how the business actually runs: who does what, where time is lost and what must never break.
You get the smallest version that solves the problem, and a clear picture of what it can grow into later.
Working software early, honest progress along the way, and a launch on real infrastructure — with tests wherever money or data is involved.
The products on this site run daily without a developer on call. Support, improvements or a clean handover — whatever fits.
About
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.