P-01 / AGENTS
Run the agents you need.
Agent fleets on owned compute. Always-on, predictable cost, behaviour shaped to the operator's business — not the model provider's defaults.
// 04 — PLATFORM · 404 OS
REF 404.PLT.LIVE
404 OS — operating layer for the network.
The platform underneath operator businesses. Agent fleets, voice automation, workflows, dashboards, internal OS. Deployed on owned compute. Controlled by the operator.
AGENTS · VOICE · CRM · WORKFLOWS · DASHBOARDS · OPERATOR OS
// PILLARS · WHAT 404 OS RUNS
REF 404.PLT.04
Four runtimes. One platform.
404 OS is the operating layer that ties them together — so an operator deploys one stack and runs the whole operation, instead of stitching together five SaaS tools and three integrations.
P-02 / VOICE
Run the conversations.
Inbound and outbound voice. Sales, qualification, appointment setting, lead resurrection. Real conversations with sub-second turn time.
P-03 / WORKFLOWS
Run the workflows.
CRM orchestration, lifecycle triggers, pipeline routing, M2M automation. Wired into the business OS rather than bolted on top of it.
P-04 / INTEL
Run the operation.
Dashboards, reporting, anomaly alerts, the control plane underneath everything. Operator-grade telemetry, not investor-deck graphics.
// MODULES · THE STACK
REF 404.PLT.MOD
Nine system blocks.
Each is independently deployable. Mix what you need; replace what you don't. The whole stack is API-first, so blocks drop into existing tooling and get swapped out piece by piece.
AI Agents
Always-on agent fleets. Sales, ops, intake, qualification, follow-up — running on owned compute, not rented APIs. Predictable cost, behaviour shaped by the operator.
- FLEET84
- TASKS/HR11.4k
- UPTIME99.997%
Voice Agents
Outbound and inbound voice. Sales, appointment setting, lead reactivation, intake. Sub-second turn time. Transcribed and routed live to the right human when the conversation needs it.
- CALLS/DAY14.2k
- ASR96%
- LATENCY280ms
CRM Automation
Pipeline orchestration, lifecycle triggers, lead enrichment, deal routing. Wired into the business OS — not bolted onto someone else's CRM as a Zapier afterthought.
- WORKFLOWS312
- LEADS/DAY8.2k
- ROUTING24ms
Lead Resurrection
Reactivate cold pipeline at scale. Multi-touch, multi-channel, conditioned on intent signals from the network — not blind blast. Built for operators sitting on dead CRMs that still have value.
- REACT %18
- TOUCHES4.2
- NET LIFT6.4×
Appointment Setting
Calendar-aware agents that qualify, propose, and confirm. Hand-off to humans when the conversation needs it. Full audit log for every booking — operator can replay anything.
- SET/DAY412
- SHOW %76
- NO-SHOW11
Client Dashboards
Real-time view of every workflow, agent, and signal running in a deployment. Operator-grade telemetry. The dashboard you actually open at 2am when something looks off, not the one you screenshot for a deck.
- TILES218
- REFRESH1s
- TENANTS84
Workflow Automation
Visual + code workflows. Triggered by events, schedules, signals. Drop into existing stacks. Replace piece by piece rather than rip-and-replace.
- NODES2.1k
- RUNS/DAY142k
- FAIL0.003%
Reporting + Intel
Live metrics, anomaly alerts, weekly operational briefings. Numbers you act on. Routed to the operator's inbox or the on-call rotation — not just rendered in a tab nobody opens.
- ALERTS/DAY86
- TENANTS84
- UPTIME99.997%
Operator OS
The control plane underneath everything. Roles, permissions, immutable audit, billing, multi-deployment management, API surface. Every block is replaceable; the OS keeps the operator in control.
- ROLES14
- EVT/s224
- API/s1.2k
// SPEC · WHAT IT RUNS ON
REF 404.PLT.SPEC
Deployed on owned infrastructure.
404 OS isn't a SaaS sitting on someone else's cloud. The compute, the data, the routing, the audit log — all run on infrastructure Project 404 owns or the operator's own nodes. No third-party processors.
COMPUTEARM64 + GPU pools
LATENCYsub-12ms transatlantic
UPTIME99.997% SLA · Operator tier
DATAstays in network
INTEGRATIONAPI-first · REST + webhook
DEPLOYMENT7-day onboarding cycle
TENANCYmulti-tenant by default
AUDITimmutable event log
// TIERS · OPERATOR ACCESS
REF 404.PLT.TIER
Three operator tiers.
Access starts at Operator and moves up by demonstrated track record on the platform. Network and Channel Partner tiers are invite-only — the larger the deployment, the more accountability the network requires.
Operator
Single business, single deployment. The standard entry into 404 OS.
- All 9 module blocks
- Single-tenant dashboard
- 99.997% uptime SLA
- Standard onboarding (7 days)
- Access to the Operator room in the Network
Network Operator
Multiple deployments, locations, or franchises. One pane, many nodes.
- Everything in Operator
- Multi-tenant dashboards
- Cross-deployment workflows
- Dedicated routing + reserved capacity
- Priority operator support
- Access to the Network Operator room
Channel Partner
For partners who deploy 404 OS into their own customer base. Reseller-grade.
- Everything in Network Operator
- White-label deployment surface
- Revenue share + partner economics
- Dedicated onboarding engineer
- Direct line into Project 404 ops
- Access to the Channel Partner room
// READY TO DEPLOY
Wire 404 OS into your operation.
Operator-tier access starts with a 24–72hr intake review. Network and Channel Partner tiers are invite-only. Send your intake — the right operator gets back to you.