CloudNexis · Operations infrastructure
We build agentic tooling that runs business operations and repairs infrastructure without a human in the loop, plus the software around it. Every action is logged, verified, and reversible.
Three lines, one system
The lines share one runtime. Work done for one becomes infrastructure for the others.
Long-running agents that hold the state of your systems, detect drift, act on it, and prove what changed. Not chat over a knowledge base.
Product-grade builds, not template assembly. Design system, motion, and performance treated as engineering, not decoration.
A shipped product: spaced recall, quizzes, weak-spot tracking and FAA exam figures for five certificate paths.
Architecture
Every agent run follows the same path. The dashed return is the part most demos leave out: a failed verification re-enters the loop rather than reporting success.
Specification
| Layer | Choice | Why |
|---|---|---|
| Edge runtime | Cloudflare Workers | Runs in every region without a fleet to manage. |
| State | Durable Objects + KV | Single-writer consistency where it matters, cheap reads where it does not. |
| Agent channel | MCP over JSON-RPC 2.0 | Tenant identity comes from the credential, never from a tool argument. |
| Auth | Scoped write-only tokens | A token can add material and cannot read the account it writes to. |
| Delivery | Static output, no build step | Nothing to break between the repo and the edge. |
A technical review is a working session, not a sales call.