The monthly fee buys an automated loop, not a support inbox. Here is exactly what runs, and what a person still does.
The maintenance loop
This runs continuously against every app we operate, including this one.
Every app exposes a structured API that Nokemo polls every five minutes for new errors, unresolved user feedback, and pending change requests. No screen-scraping, no guesswork.
A local model triages the raw error stream first, so transient blips and duplicates get resolved automatically instead of becoming work.
What survives triage is turned into a task in your queue — tagged with the app, the repository, and the full error context. Your own change requests land in the same queue.
A Claude Code agent takes the top task, opens your repository, writes the fix, runs the tests, and commits it with a message explaining what changed and why.
The commit triggers your pipeline — dependencies, stylesheet compilation, deploy to production, cache flush. Live in minutes, with a full audit trail.
Digest emails summarise what was checked, what was fixed, and what is still open. Critical failures alert immediately rather than waiting for the digest.
Where humans stay in the loop
We would rather tell you this up front than have you discover it later.
Compiling and signing your mobile builds is automated. Submitting them, responding to Apple's review, and managing your store listings is done by a person on our side — the review process is a conversation, not an API.
Apple and Google require the accounts to be in your legal name. We guide you through creating them and adding us as a delegate — we never create them for you, because then they wouldn't be yours.
The blueprint, the specification, and every major direction change are reviewed with you by a person. The AI executes decisions; it does not make the ones that cost you money.
Under the hood
Authentication, sessions, database sharding, email queueing, notifications, and GDPR compliance come from a core platform that already runs every app we operate. Your build starts from working software, not an empty folder.
Your app exposes its own tools over MCP, the open protocol AI agents use to read and act on real systems. That is what lets maintenance be automatic and auditable instead of a bot clicking around your admin panel.
Your mobile apps are built from the same screens as your web app rather than written a second time. A change you approve on the web is the change that ships to the phone.
PHP 8.2 and MySQL on standard shared hosting. No Kubernetes, no serverless bill that scales with your success, no platform that can deprecate you.
The blueprint turns what's in your head into a written spec and a fixed price.
Generate your system blueprint