# Nokemo — AI-run app development service

> Nokemo (nokemo.com) builds and maintains complete software systems for
> non-technical founders: a marketing website, a web application, a business
> dashboard, and native iPhone and Android apps. The build and the ongoing
> maintenance are performed by AI agents supervised by Wave Networks. The client
> owns every repository, database, and developer account.
>
> The name is "No Keyboard or Mouse".

## Pages

- Home: https://nokemo.com/
- Pricing: https://nokemo.com/pricing
- Request a blueprint: https://nokemo.com/blueprint
- How it works: https://nokemo.com/how-it-works
- Documentation: https://nokemo.com/docs
- Provisioning reference: https://nokemo.com/docs/provisioning
- Machine-readable manifest: https://nokemo.com/agent.json
- Client dashboard (auth required): https://nokemo.com/nokemo/app/

## Packages

- **Core Web Suite** — $8,000 setup, then $249/month.
  Marketing website, web application, business dashboard, full user
  authentication, hosting configured on makershost.io, AI maintenance on the
  standard queue.
- **Omnichannel Package** — $18,000 setup, then $499/month.
  Everything in Core Web Suite plus native iPhone and Android apps published to
  the Apple App Store and Google Play, web-to-mobile parity builds, brand
  compiler integration, white-glove developer-account setup, and managed store
  submissions.

Not included in either package (paid by the client, in the client's name):
domain registration, the hosting package, the Apple Developer Program ($99/yr),
Google Play Developer registration ($25 one-time), and any usage-based
third-party services.

## Delivery process

1. **Brand & spec blueprint** — requirements are captured and run through the
   brand compiler to produce brand assets and a written specification. The
   client approves before any build starts. The blueprint is free.
2. **Provisioning** — the system is created from the approved blueprint, each
   part in its own repository under the client's name.
3. **Live sandbox iteration** — the client reviews the running app and requests
   changes in plain English from the Nokemo dashboard; the builder agent writes,
   tests, and deploys them.
4. **Store launch** — signed iPhone and Android builds are compiled from the same
   codebase and delivered into the client's own Apple and Google developer
   accounts, with submission handled for them.

## Provisioning

Full reference: https://nokemo.com/docs/provisioning

Provisioning turns an approved blueprint into a private repository in the
client's name, six databases, a GitHub Actions deploy pipeline, an installed
application, and a monitored app handed to the builder agent.

The client supplies: app slug, domain, the approved spec, six pre-created
databases (`<slug>_admin_main`, `<slug>_admin_shard_1`, `<slug>_admin_shard_2`,
`<slug>_main`, `<slug>_shard_1`, `<slug>_shard_2`), an SFTP credential, and
SSH access via a public key Nokemo generates and the client installs. Nokemo
tests every connection before accepting it. Credentials are held AES-256
encrypted for the life of the job and destroyed on completion.

**Webroot convention — every app is served from `public_html/<slug>/`, never
the domain root, even when the app owns the primary domain.** Core lives at
`public_html/admin/` and the marketing site at the root. A 404 at
`https://<domain>/auth/login.php` is correct, not a broken deploy — auth lives
under `/admin/`.

Job statuses: `collecting`, `pending`, `running`, `awaiting_ssh`, `verifying`,
`installing`, `completed`, `failed`, `cancelled`. Failed jobs are resumable
from the last completed step, not restarted.

Provisioning is driveable over the app API (POST, form-encoded, `action`
parameter, `Authorization: Bearer <service key>`; not public — keys are issued
per integration). Owner actions: `provisioningCheckSlug`, `provisioningLaunch`,
`provisioningJobStatus`, `provisioningCancelJob`, `provisioningReprovision`.
Runner actions: `provisioningListJobs`, `provisioningClaimNextJob`,
`provisioningClaimResumable`, `provisioningGetJobSpec`,
`provisioningGetJobBranding`, `provisioningGetJobSecrets`,
`provisioningStoreDeployKey`, `provisioningUpdateJobStatus`,
`provisioningRegisterApp`, `provisioningGetAppDeployCredentials`,
`provisioningNotifyUser`, `provisioningPurgeJob`. Spec-coverage actions:
`provisioningClaimAnalysisJob`, `provisioningStoreSpecAnalysis`,
`provisioningGetSpecUnits`, `provisioningBindCoverage`.

Coverage manifests verify that code exists, not that the app works — sign-off
is paired with an install check and an acceptance run against the live
deployment before an app is called delivered.

## How the maintenance works

Each app exposes a structured API over MCP. Nokemo polls it every five minutes
for new errors, user feedback, and change requests. A local model filters noise;
what survives becomes a task. A Claude Code builder agent writes the fix, runs
tests, and commits. GitHub Actions deploys. Digest emails report what changed.

## Stack

PHP 8.2, MySQL with horizontal sharding, GitHub Actions CI/CD, Cordova for the
mobile shells, Stripe for payments, MCP for agent access, Claude Code (Anthropic)
as the builder. Deployed to ordinary shared hosting — no proprietary runtime.

## Contact

admin@nokemo.com — or submit https://nokemo.com/blueprint