Tech Stack
The stack is intentionally deployable.
The platform is built so the marketing site can be static, the operating system can run behind admin auth, and the automation layer can be upgraded through Cloudflare services without forcing a massive backend first.
| Layer | Purpose | Why it matters |
|---|---|---|
| Static public site | Explains, sells, educates, and qualifies prospects | Fast deployment, easy SEO, low hosting cost |
| Admin OS | Owner-only automation command center | Protects founder credentials and production connectors |
| Customer SaaS layer | Signup, onboarding, service selection, workspace setup | Customers can configure their own company OS without entering admin |
| Cloudflare Workers | API layer for routing, tasks, approvals, ledgers, social drafts | Server-side secrets stay protected |
| Cloudflare D1 | Persistent records for customers, workspaces, approvals, tasks | Moves the system beyond browser-local demo mode |
| KV / Queues | State cache and async task processing | Supports autonomous workflows and deferred actions |
| Resend | Approval notifications | Risky actions can ask the owner before going live |
| 0meg4kAI | QA/security assistant brain | Blocks unsafe customer access and reviews actions before escalation |
Built around a safety-first autonomy model.
Drafting, routing, scoring, and task creation can happen automatically. External actions — publishing, outbound client communication, payment-sensitive steps, contract-sensitive claims, and owner credential usage — should route through approval rules.