Your Pies. Your infrastructure. Your record. No lock-in.
PAI runs a governed AI workforce — your Pies — on infrastructure you own: your servers, your keys, your team, your memory, completely controllable. Deploy on-premises or Bring Your Own Cloud with PAI Private, and every action passes the Governance Plane before it runs. No lock-in, no chat held hostage, no skills you can't take with you — a private AI ecosystem you own, not a subscription you're trapped inside. Each worker is a Pie: a slice of the whole, put to work on one role. Your Pies. Your premises. Your keys. Our guardrails.
Say PAI. Or Pie. Or π. It answers to all of them.
PAI — Private, Physical, Provable AI, on your own premises. Your keys, your infrastructure, your signed record: one platform you own.
PAI is the whole pie. A Pie is one slice you put to work — a single role an agent picks up and runs, under your keys, your budget, and the Governance Plane.
Own it, don't rent it — the infrastructure, the workers, the memory, and the record.
PAI Private deploys the whole stack behind your perimeter — the OpenPie Engine, the PaperPie Workforce and the Governance Plane in your VPC or on your own hardware. Your servers, your keys, your memory. No chat export, no skills export, no ransom for leaving: cancel any time and keep everything.
Wire in Slack, Gmail, GitHub, your databases — or any MCP tool server — through Governed Connectors. They ship in the stack and switch on with configuration; first use asks you, and after that every call passes policy, allowlisted per role and autonomy level. Desktop Reach turns your own machine into a governed tool the same way — the pod reaches out, nothing reaches in. Connect everything, governed →
Model your org the way it runs: roles, teams, and whole companies, each Pie with one manager and a job description, under a CEO Pie that reports to you from PieHub. Per-company memory is isolated by the database — not by a policy promise — so one company's context is invisible to another's Pies. Each venture gets a Founder OS — a private operating plane your leadership Pies keep current.
Track every Pie's spend and state, cap it with hard-stop budgets, and route across 35+ providers on your own keys (BYOK) or local models. Every action is written to an Ed25519-signed, hash-chained audit — the Driver Record, verifiable offline. Governed AI workers you can prove, not just trust.
Paste a token for Slack, Gmail or GitHub; point the pod at any MCP tool server for your databases and SaaS; or turn your own desktop into a tool. Whatever it gains, every call passes the same gate — first use asks you, and it's signed on your own device.
signed on the chain — mcp:id.tool · params hashed
Own-token integrations (Slack, Gmail, GitHub, coding CLI) go in once and reach every Pie — tokens stay write-only in the pod's vault. Or point at any MCP server over streamable-HTTP / SSE.
Every tool becomes a governed action: first use asks you, risky classes park for approval, a server that changes a tool re-earns trust, and internal hosts are refused. It fails closed.
Every call lands on the Ed25519 audit chain as mcp:id.tool with its params hashed — what ran, what it cost, who approved it, verifiable offline.
“We pointed a Pie at our internal orders database over MCP. First time it tried to run a query, it asked. We approved. When the vendor pushed a tool update, the schema hash changed and it asked again — exactly what we'd want. Every query is on the chain, so finance can see who ran what, when, for how much.”
A representative scenario, not a named customer. Behaviour matches the shipped governance tests (first-use approval, schema-drift re-approval, signed chain).
From signup to working Pies in three steps.
Serve from the Pie Menu — 33 ready-made Pies from Executive PA to Collections to Legal Review — or let the Bakery bake a custom one from a two-minute brief. Each comes with a persona, skills, and a budget you control.
Paste your own Anthropic/OpenAI/Google keys — they stay on your device, never on our servers. Pair WhatsApp and Telegram for briefings and approvals.
Your Pies handle the routine. Anything sensitive — sends, payments — waits for your one-tap approval. You see every action and every rupee.
Five launch Pies below, security-hardened — plus 28 more in the Pie Menu and the Bakery for custom ones. Every Pie has a "what it did yesterday" feed you can audit line by line.
Email triage and drafts, calendar, reminders.
Invoice chasing with a polite-to-firm escalation ladder. Proposes payments — never executes them.
Lead and WhatsApp follow-ups, CRM notes — no lead goes cold.
Competitor and news watch, distilled into your morning brief.
Instant answers over your own business documents — contracts, SOPs, price lists.
33 pre-built Pies, each with a persona, a reviewed skill set, conservative autonomy defaults, and a budget you set — plus The Bakery when you need one that doesn’t exist yet.
Your day, triaged, prepped, and closed out
operationsEmail triage and replies in your voice
operationsScheduling without double-bookings or lost focus time
operationsMinutes, actions, and follow-ups from every meeting
operationsPipeline follow-ups that never go cold
growthPolite, relentless invoice chasing up the ladder
financeExpenses categorized, invoices prepped, books tidy
financeYour numbers, digested into weekly insight
knowledgeDeep research briefs with sources you can check
knowledgeInstant answers from your own documents
knowledgeCustomer replies drafted with your patience
growthCampaign copy in your brand's voice
growthPosts and replies, proposed before they go public
growthKeyword and content briefs that earn rankings
growthEvery word checked against your voice
growthOnboarding plans and policy docs, DRAFT-first
peopleSourcing screens and interview kits, ready to run
peopleContract review in DRAFT, never files or signs
operationsFiling calendar and DPDP register, always current
operationsSOPs written, vendors managed, operations humming
operationsQuotes compared, savings found, owner decides
financeCode review and scripts, sandboxed and gated
technicalTest plans and bug triage before users notice
technicalTrips planned to the gate; you tap pay
personalDeal briefs and talk tracks before you walk in
growthStrategy, priorities, and the operating cadence — framed as decisions
leadershipBudgets, funding, unit economics, and honest cost models
financeArchitecture, tech decisions, and chunked delivery with acceptance gates
technicalExecution — the month-1 plan, roles, and the operating rhythm
operationsPositioning, GTM, verticals, and messaging that stays honest
growthThe decision register, open questions, meeting prep, and the update log
leadershipPRDs, product decisions, and the roadmap — written to be built
knowledgeEntity, IP, compliance, and risk — flagged early, never guessed
peopleThe Pie that bakes new Pies, safely
describe a role · AI bakes the Pie · you set its leashEvery action your AI takes is signed, chained, and verifiable. See every rupee spent, approve what matters, and stop everything in one tap. That's not a chatbot — that's governance.
Every Pie's cost, per company, against a hard-stop budget you set. It cannot overspend the cap.
Sends, payments and anything sensitive wait for your one-tap approval — on WhatsApp or in the Companion.
Every action Ed25519-signed and hash-chained into the Driver Record — verifiable offline, years later, without us.
Pause one Pie, one company, or everything — instantly, from any screen. The default on a missed approval is deny.
24 live · 17 enableable (ships in the stack, switched on at setup) · 1 on the roadmap. Grouped so you can see the whole surface — every one carries its honest status on the explorer.
The leash and the flight recorder.
Under one roof, every call gated.
Roles you serve, not staff you configure.
The boss's chair is your chat app.
Isolated by the database, not a promise.
One image, no lite edition.
Govern the pair, not just the agent.
A private operating plane per venture.
One stack with three layers: the reach, the company, and the trust between you and both.
The reach. Every chat channel, a real browser, your devices as hands and eyes, voice, installable skills — the reach of the most capable worker you’ve ever had.
The company. Org charts, goals, tasks, heartbeats, and salaries in tokens — your Pies get a boss, a title, and a job description.
The trust layer. One-tap approvals, autonomy floors, hard-stop budgets, a signed audit chain, and the kill switch — the leash and the flight recorder.
Built on the open-source OpenClaw & Paperclip projects (MIT) — credited, not hidden.
The Companion is an installable app that talks only to your pod. You pair it once with a bearer token over loopback or your private network — never a public port — and approve, watch and steer the workforce from your pocket.
The app holds a single bearer token on your device and reaches the pod over loopback or your Tailscale network. No inbound port is ever opened; nothing on the public internet can reach your pod.
Your model keys and connector tokens live in the pod's AES-256-GCM encrypted vault, write-only — the Companion never holds them, and they never reach our cloud.
When you enrol with our cloud, the pod initiates every heartbeat and reports a secret-free rollup. The control plane never reaches in — even in your own VPC.
Installable and offline-capable: approvals, budgets, the kill switch and the audit status stay in reach even without a connection, and sync catches up later.
The full pod on your own laptop or a box in the cupboard — nothing leaves it.
A hosted pod with the Fleet console — seats, org policy, one pane over every pod.
The same image inside your own cloud; your keys, your data, outbound-only.
Opt-in: keep a copy of your data in your own Postgres, MySQL or MongoDB.
Mysty is the voice on every page — it narrates what the Governance Plane decided and the chain recorded, and answers from what actually ships, with an honest Live, Enableable or Roadmap status. It never decides, approves or acts; that is the Pies’ job, under your leash.
The difference between hiring staff and subscribing to someone else's.
| Aspect | PAI | Cloud AI SaaS |
|---|---|---|
| Where your data lives | On your device or your private pod | Their multi-tenant cloud |
| Whose AI keys | Yours — you pay providers directly, at cost | Theirs — usage marked up, limits theirs |
| What happens if you cancel | You keep the box, the agents, and all your data. Only our dashboards stop. | Access ends. Export what you can, while you can. |
Not four products. The same container, the same governance, the same Pies. What changes is where it runs and who holds the keys.
Solo
An individual, a founder, an operator with their own hardware.
Your Pie runs on your own Mac or a Box on your desk. No account with us is required and no cloud is involved — point it at local models and nothing leaves the room. You are the owner; there is no admin above you.
Your box. Your keys. Optionally your own models.
Run it on your own Mac →Org
Typically ₹2–200 Cr, often more than one company.
A pod for the organization, a Pie per person, budgets per driver. Invite your people, give a mentor read-only sight of decisions, and keep the kill switch on your phone. This is the mode the cloud sign-up creates.
Our cloud or yours. Provider keys stay in your pod.
Start in the cloud →BYOC
Regulated, or simply not willing to move the data.
The pod runs inside your VPC. Your keys, your data, your network — we orchestrate, we never hold it. The pod calls out to enroll and heartbeat; the control plane never connects in. That invariant is the whole reason this can be honest rather than a checkbox.
Your VPC. Your keys. We never reach in.
Read the security design →Partner
Miatz, ashr.work, and others packaging it as their own.
Sell it inside your package. A training cohort gets a Pie per learner, a mentor console, and an auditable record of what each learner decided — signed, and verifiable after they leave. Demystify also delivers it directly as a forward-deployed engagement.
Your customers. Your brand. Our governance.
See what it does →Pod from ₹12,000/mo DRAFT — or own the hardware outright with a Box. All plans include the Control Plane. Annual = 2 months free. Prices exclusive of GST.
Three ways, your pick — the setup wizard asks once. Bring your own key and your data goes straight to the provider under your account, at cost, no markup; the key lives in your pod's vault, never in our code or logs. Run local models and nothing leaves the box at all. Or take metered access on an org pod, where each person gets their own key with their own budget and a hard stop. Whichever you choose, nobody using a Pie ever holds the provider key.
Your device keeps working locally and queues its audit telemetry for up to 72 hours. Agents that need cloud AI models pause gracefully; anything running on local models (Box Plus) keeps going. When the connection returns, everything syncs — with zero gaps in the audit chain.
Only with your approval. Payments are propose-only by design — a Pie can prepare a payment and send you the link, but a human always taps pay. That's a platform rule, not a setting you can accidentally switch off.
Owner-led businesses — typically ₹2–200 Cr revenue, often running more than one company — where the owner lives on WhatsApp and wants outcomes (chased invoices, answered leads, a daily brief) with control (what did it do, what did it cost, stop it now).
An open-source agent stack you can inspect — agent runtime, organization/governance layer, a model gateway for your keys, a local database for memory and documents — plus our governance daemon that signs every action into a tamper-evident audit trail. No public inbound ports; management traffic only over a private network.
They govern the agent. We govern the pair: one named human — the Driver — bound to their Pies, their budget, and their own chain of custody. That pair is the thing nobody else models, and it's why spend, approvals and the audit trail all line up per person instead of per bot. The runtime underneath is an implementation detail we could swap; the accountability layer is the product.
Yes, and without us. Every action is Ed25519-signed and hash-chained on your device, and any person's decisions can be exported as a portable credential that verifies offline with no access to your systems or ours. Not “trust our dashboard” — check it yourself, anywhere, years later.
Yes — same container, your VPC. It's one image with four modes: your laptop, our cloud, your cloud, or a demo. The pod always calls out to enroll and report; we never need inbound access to your network, and your keys, your data and your signing key never leave it. A firewall that allows only outbound HTTPS is enough.
Three routes. Direct from Demystify Systems — with a forward-deployed engineer to stand it up, or as the replacement for hiring one. Through a partner who resells it inside their own package (Miatz for training cohorts, ashr.work, and others). Or self-serve on your own hardware, where you get the full stack and no reseller at all.
