Studio

One person, one machine, 64 days.

Zaparo is written by one person. Not alone: AI agents work alongside, but the decisions, the products and the mistakes belong to one person. Day one was July 29, 2026; since then, 5,101 commits across 116 repositories and about 506 thousand lines of Kotlin, TypeScript and Python.

Everything runs on a single ARM server: the live services, the module APIs, the Android builds, the signed bundles and this site. Even the site is not written by hand; it is regenerated every hour from what the server is serving, what the store says and what git remembers. Every number on this page was read from somewhere; none was typed.

The method is one sentence: write a job once. If a game needs a leaderboard, a module does it, not the game; the second game takes the same module. When a module has a defect, it is fixed in the module, never worked around in the app. That discipline came back, within a month, as 67 modules and 23 products.

The rules are written down too: legal, safe, honest growth. No incentivised installs, no fake reviews, no dark patterns. Every app is free to use; what one sells is chosen app by app, and the ad network carries the rest.

Since July 29, 2026

repositories: 116
commits: 5,101
thousand lines of code: 506
products: 23

Tools

What we built to run this.

Tools nobody sees, used only by the studio. None of them has a link; all of them run every day.

The server monitor: load, disk, traffic, services, the last day, and what is eating memory.

Server monitor: A one-page monitor with no dependencies: CPU, memory, disk, network, services and the last twenty-four hours, sampled every second. Backups, apps and modules on the same page; nothing that is not deviating is shown.
Games panel: The database panel for the games: players, ghost runs, the cast. Every change is written to an audit log.
Ship deck: Version number, store graphics, the upload to Play and the gates that stop a release, on one screen. A release does not count until it runs on the phone.
Inventory: Which apps exist, which module is at which version, what is on the store, which content is on the shelf: every answer is derived from its sources the moment it is asked, and no list is kept. It has no write path.
Phone tunnel: The real phone reaches the server over its own cellular line. Installs, logs and screen driving are done under a lease; a job that drives the screen rings the phone, and a red press stops it.
Gate: The one Google sign-in in front of the internal panels. Every panel uses the same door; a second login is never written anywhere.
Browser probe: Opens every published page the way a phone would and catches the error, the broken request and the screen that shows only its background colour. Then it walks past the first screen by tapping at random.
Foundry: The factory that produces the levels, questions, word lists and voice clips. It proves with a solver that every puzzle has one solution; what cannot be proven is not published.

Work with us

If you run a process by hand, let us wire it up.

We build automation and integrations on n8n, with 344 workflow templates behind us. We write Android and browser apps too; everything on this site is the proof. Describe the process; we deliver it running.

To talk about a job

Automation, integration, an Android or a web app. Write what you do and what wears you out; that is enough.

privacy@kbsoap.com

If you need a module

Some of the modules on the platform page will open to outside use later. If one of them is exactly what you are looking for, write and we will talk.

See the modules

Contact

One address.

Products, the ad network, work, privacy: the same box for all of it.

privacy@kbsoap.com