Trust & status

What cloud-itonami actually is, what it actually measures, and what is actually true right now — including the parts that aren't finished yet.

Live numbers

Verified against the live GET /api/status and GET /api/fleet/metrics endpoints below — not hand-typed, not a stale snapshot from an older doc. site-ui.js re-fetches both through Re-frame on every pageview and updates this section if the numbers have moved since generation.

External free tenantsliveself-registered, passkey-authenticated
External paid customerslivelive value; 0 means pre-revenue, and free tenants or agent runs are not revenue
Agent runs / 7dliveaggregate across free-path dry-run verticals
Operational surfacelivecurrent route, contract and integration checks; adoption volume is reported separately
Open business modelsliveforkable OSS blueprints, ISIC Rev.5-coded
Jobs indexedlivelive meta-search over Arbeitnow + Jobicy

Loading the current live snapshot. Re-verify yourself:

GET /api/statusGET /api/fleet/metricsGET /api/billing/statussource (AGPL)

What cloud-itonami is

The governed business OS where organizations install Bots to carry bounded work across capture, identity, work, communication and execution on one auditable product surface.

Each Bot works inside tenant identity and permissions, records its run, and stops at human-approval or independent Governor gates. Kotoba defines procedures, Kotobase persists facts and audit trails, and Murakumo supplies inference; Cloud Itonami owns the integrated product and deployment surface.

Operator: see the footer of this page, or the Terms of Service / Privacy Policy.

How to read the evidence

  • Product evidence: the installable clients, public routes and source show what has shipped; they do not prove adoption or a completed customer outcome.
  • Customer evidence: the live external-tenant counts show provisioned tenants; they do not become a case study, endorsement or paid customer without separate evidence.
  • Operational evidence: agent-run and product-surface checks show recorded activity and exercised contracts; they do not by themselves prove a stable deployment or successful business result.
  • Financial evidence: only the live paid-customer and billing records support a commercial claim. Free tenants, agent runs and checkout readiness are not revenue.
  • Deployment evidence: the served API version and health/status receipts identify the live release and its observed checks; a repository commit alone does not prove that release is serving traffic.
GET /api/healthGET /api/statusGET /api/fleet/metricsGET /api/billing/status

Known limitations (stated plainly)

  • This remains an early-stage product. The live externalPaid value above is the commercial proof; do not infer revenue from free tenants or agent runs.
  • Terms, Privacy and the DPA are owner-approved as of 2026-07-24; Stripe checkout E2E and foreign-company registration remain open release gates.
  • External tenants currently use the free self-claim path; no customer case study or logo is claimed here.

We would rather state these plainly than omit them — see the go-live runbook for the full internal operating detail this summary is drawn from.