Your AI, inside your stack.
A private AI operating system we fork from our own CalmOS, deploy into your infrastructure, integrate with your existing tools, and hand to you on paid invoice. Audit-ready for the EU AI Act by default.
Good morning.
A platform we run, forked into your stack.
A real platform we use daily
CalmOS runs Calmworks: our pipeline, projects, tasks, Calmo interviews, Spar research, Composer design. You start from the same code we rely on.
Forked for you
We fork CalmOS into a private repo for your org, keep the modules you need, add the ones your workflows demand, and hand you the keys.
Lives in your infrastructure
Your Vercel project, your Supabase, your tokens, your data. EU AI Act Articles 4, 10, 52 covered by default. No sending your data through a vendor.
Nine modules, wired together.
Keep what you need, leave what you don't. Everything speaks to everything else through one governance layer.
Pipeline
Deals, leads, and status in one place. Surfaces what moved overnight.
Projects
Active engagements with milestones, docs, and cross-team context.
Tasks
Three-tier task structure that rolls up to projects automatically.
Knowledge
pgvector-backed RAG across your docs, emails, transcripts, and wikis.
Composer
Inline AI image generation (gemini-3-pro-image-preview) on any page.
Calmo interviews
Mass voice interviews with synthesis into editable reports.
Spar research
Voice + text research agent with per-session token budget tracking.
Workflows
Triggers, recipes, and a visual command center. Our n8n replacement.
Governance
Org scoping, tiered access, audit log, RLS. The foundation every module sits on.
This is what we run Calmworks on.
Your fork starts from the same code. Pipeline, projects, tasks, Calmo, Spar, Composer, workflows — all shipping in production.
Good morning.
Talks to the tools you already pay for.
Connections ship as first-class modules with refresh-token handling, scoped per user, and logged through governance.
Plus anything with an OAuth flow or a stable API. We add connectors as engagements demand them.
Live in eight weeks.
Diagnostic, fork and configure, adopted. Eight-week core cycle. Scope determines how much goes in.
Diagnostic
We scope which modules you need, which tools we're orchestrating, and what your org's reality looks like. No slide decks. We write a one-page brief you sign.
Fork and configure
We fork CalmOS into your private repo, wire up auth against your identity provider, connect your existing tools, and bring over the first three workflows that move the needle.
Live, adopted, audited
Your team is onboarded inside the platform. Articles 4, 10, 52 are logged and audit-ready. We hand over code, docs, and admin access. On paid invoice, it is yours.
It's yours.
Client AIOS is proprietary Calmworks software. You receive an unlimited internal-use license for your organization: run it, extend it, modify it, deploy it anywhere in your estate.
Calmworks retains the upstream code and the right to reuse patterns, modules, and primitives in future engagements. You cannot resell or sublicense the platform to third parties. Your bespoke modules, configurations, and your data stay yours. No subscription, no per-seat fees, no lock-in.
Common questions.
SaaS means you rent access to a shared multi-tenant app. Client AIOS is a private fork of our own platform, deployed inside your stack, running on your infrastructure with your data. No shared tenancy. No subscription lock-in. When you pay the invoice, the code is yours.
You keep running. The code is in your repo, the data is in your Supabase, the tokens are yours, the runtime is your Vercel project. Nothing about your operation depends on a Calmworks server being online.
You get an unlimited internal-use license to the fork for your organization. Calmworks retains the upstream code and the right to reuse patterns and modules in future engagements. You cannot resell or sublicense the platform. Your bespoke modules and your data are yours.
Yes. The auth module ships with adapters for magic-link and OAuth, and is designed to swap in OIDC or your existing SSO. We wire it up during the fork + configure phase.
No, not to run it. Yes, eventually, to extend it. Day one operates out of the box. Over time, teams who want to build custom modules, connect bespoke tools, or add workflows hire or assign an engineer. We transfer capability as part of every engagement.
Want to see it running?
Book 30 minutes. We walk you through our own CalmOS, then scope what your fork would look like.