A small software studio. We build our own products and take on a few client projects each year — SaaS platforms, mobile apps, web apps for founders who want the engineering done properly the first time.
Focused engagements where one engineer owns the architecture and ships the code. No agency layer, no handoff chain — you work directly with the person building it.
Multi-tenant web products with auth, billing, dashboards, and admin tooling. From first login to first paying customer.
Android apps and games, built native where it matters. Last Pixel is a 60 FPS Kotlin/Canvas game with no engine. If we can build that, we can build your app.
Dashboards, internal tools, marketplaces, API platforms. Clean data models, real auth, and tests that actually run in CI before anything ships.
You describe the product. We ask pointed questions about users, data shape, and edge cases. By the end of the call, both sides know if there's a fit.
A short document: what gets built, what's explicitly out of scope, the architecture, and a clear price. A signed scope — not renegotiated weekly.
You get regular working builds and walkthroughs as things come together. Nothing surprising lands at the end.
Full repo, deployment, and documentation. Reasonable bug fixes after launch, with an optional retainer if you want ongoing support.
The studio's first product. Written in pure Kotlin on Android Canvas — no Unity, no Unreal, no engine. 60 FPS, procedural synthwave audio, zero pre-made assets. A proof of what one engineer with modern tooling can ship.
The last pixel alive in a dying digital world.
Run, jump, and survive through 20 hand-tuned levels across 4 zones as the system collapses behind you. Procedural synthwave score. Ghost replay. No engine — every frame is code.
Ivnoworks is run by a single engineer. For eight years we've shipped production software — enterprise platforms with thousands of daily users, real-time robotics systems where a dropped frame is a real-world problem, and mobile apps built on nights and weekends.
This is the studio we always wanted to work with: one engineer who designs the system, writes the code, and stays on the call when something breaks at 11pm.
AI is part of the toolchain — used every day. But only to go faster at work already known how to do. The architecture, the hard decisions, the debugging of the weird stuff — that's still a human with eight years of scars.
The system gets drawn before it's written. You get an architecture doc in week one — not a surprise at handoff.
Kotlin, TypeScript, Python, Go, Swift — they're all just syntax. The parts that matter are the data model and the failure modes.
Regular demos. Working features every sprint. No three-month silences ending in a surprise.
One engineer, one project at a time. Your deadline isn't competing with another client's.