Shipping production software as a one-person studio

“Solo developer” sounds like a constraint. Run deliberately, it is an architecture: no coordination overhead, no diffusion of responsibility, and a brutal forcing function for scope. Here is what actually makes it work at Crypton Studio.

Scope is the real engineering skill

Every feature carries three costs: building it, maintaining it, and explaining it. A team can amortise those; a studio of one cannot. So the first version of anything answers a single question — what is the smallest thing a stranger would pay for or keep installed? ScanCrypt launched far smaller than it is today and grew to 70+ tools through releases, not through a two-year beta.

Boring technology, deliberately

The stack page on this site is intentionally unexciting: Kotlin, Next.js, PostgreSQL, Firebase, GitHub Actions. Novelty is a tax paid in debugging time, and a solo studio pays it alone at 2 a.m. The budget for “interesting” goes to the product — on-device OCR, encrypted vaults — never to the plumbing.

Automation is the second employee

• CI builds, tests and signs every release — a laptop dying must never block a launch.
• Crash reporting triages itself into a weekly review; not every exception is urgent.
• Store listings, screenshots and release notes live in the repo, versioned like code.

Support is product research

Answering every support email personally sounds unscalable. It is also the highest-signal research channel a product gets: the same hands that read the complaint fix the bug. The promise this studio makes clients and users is the same one — the person you brief is the person who codes.

What it costs

Honesty section: solo means slower parallel work, no built-in code review (linters, static analysis and discipline stand in), and bus-factor one — mitigated by boring tech, documentation and reproducible builds. For focused products, the trade holds. That is the studio’s whole thesis: one developer, whole products.