PolicyFiles
DefinitionsKnowledge
1Resolve the company context
MEANING
Company knowledge, business definitions, files, and policy are resolved before the work starts.
Make the company
understandable and executable.
Company OS connects what the company knows, what its work means, who has authority, how people and AI execute, and what evidence proves the outcome.
Start here
Invite-only private alpha
See how work is proved
Also available through the Company Console, the desktop app, and APIs when configured.
Works with
Claude CodeCodexOpenCodePiOMP
See how it works
One operating loop.
Every outcome proved.
Meaning, work, proof, and learning stay connected from the request to the reviewed result.
Task
Invoice issue detected
OwnerFinance
Statusassigned
2Give the outcome an owner
WORK
Requests become owned tasks with authority, execution, and an outcome someone answers for.
Datacited
Taskslinked
Riskwaiting
3Keep evidence with the result
PROOF
Important evidence stays with the result, and consequential actions pause for approval.
ProposalMemory
Improvement proposal
Recurring escalation friction
1Approve2Revise3Reject
4Propose reviewed improvements
LEARNING
Reviewed outcomes and recurring friction become improvement proposals a person approves.
Start here
Free · 3,000 credits to start · Console and desktop app
One company system. Several front doors.
Start with the surface that fits the work. Company identity, policy, tasks, evidence, and outcomes remain under Company OS.
Company Console
The primary browser workspace for business operators and first-time users.
Desktop app
Direct governed agents inside project folders and inspect their work.
Agent runtimes
Use Codex, Claude Code, OMP, or another admitted execution environment.
Approvals
Bring consequential decisions back to an authorized person.
APIs and automations
Connect governed workflows to other systems when configured.
Company record
Return tasks, evidence, receipts, and outcomes to the same authority.
Agents can act. Risk waits.
Company OS makes the operating boundary visible: what was used, what was protected, what needs a person, and what entered the company record.
Every run has a receipt.
01 / VisibilityOperators can inspect context used, tools called, data touched, policy decision, evidence produced, and tasks created.
Company data stays intentional.
02 / RedactionPrivate context is scoped, sensitive values are redacted from receipts, and external tools receive only the slice they need.
Consequential work pauses.
03 / ApprovalFinance, customer, legal, HR, security, and infrastructure actions can require a human yes before mutation.
The company remembers.
04 / AuditApprovals, rejections, corrections, rollbacks, outcomes, and papercuts remain reviewable. Only curated knowledge becomes reusable memory.
See the work, the evidence, and what still needs a decision.
An important result should not end as an unexplained answer. Company OS keeps the request, action, evidence, approval state, and outcome together.
Customer complaint triaged
Support data checked, account history cited, follow-up task created.
Sensitive reply waiting
Draft prepared, reputation and policy gate require operator approval.
Invoice issue detected
Finance record mismatch found and routed to the right owner.
Forecast scenario created
Assumptions, data used, simulated timeline, and recommendations saved.
The company remains, even when the agent session ends.
An AI assistant helps inside a conversation. Company OS preserves the company task, authority, evidence, outcome, and reviewed lessons around the work.
Normal AI chat
- Answers questions, then the user manages follow-up.
- Depends on pasted context or uploaded files.
- Follow-up, risk, and approval often live elsewhere.
- The transcript is usually the main record.
Company OS
- Connects requests to owned work, authority, execution, and outcomes.
- Uses company knowledge, business definitions, files, and policy.
- Keeps important evidence and pauses actions that need approval.
- Turns reviewed outcomes and recurring friction into improvement proposals a person approves.
Pricing
Credits are used when Company OS runs agent work. Longer tasks use more. Approvals and receipts are free.
Free
$0
Try Company OS
Console and desktop app
Includes:
- 3,000 credits to start
- +100 credits daily, capped at 1,000
- All 40 templates, run on demand
- Approvals and receipts on every action
- Console and desktop app
Free to start. No purchase needed.
Operator
Save 17% annual$20/mo
For getting more done, solo
Everything in Free, plus:
- 10,000 credits / month
- Up to three companies
- Email, Slack, Notion, GitHub, Stripe connectors
- Top up credits anytime
Purchasable after the private alpha.
Company
Save 17% annual$50/seat/mo
For shared workspaces
Everything in Operator, plus:
- 25,000 pooled credits / seat / month
- Company packs: roster, policies, document profiles
- Centralized billing and usage analytics
- Dedicated support channel
Purchasable after the private alpha.
Preview pricing. Paid plans cannot be purchased yet: Company OS is in an invite-only private alpha, and these tiers may change before general availability.
Questions
What is Company OS?
Company OS connects business meaning, governed work, people, AI agents, evidence, and reviewed institutional memory in one accountable operating system.
Can agents act without me?
Agents can act. Finance, customer, legal, HR, security, and infrastructure actions can require a human yes before mutation.
Which agents does it work with?
Use Codex, Claude Code, OMP, or another admitted execution environment. Company identity, policy, tasks, evidence, and outcomes remain under Company OS.
What happens to company data?
Private context is scoped, sensitive values are redacted from receipts, and external tools receive only the slice they need.
What does the company remember?
Approvals, rejections, corrections, rollbacks, outcomes, and papercuts remain reviewable. Only curated knowledge becomes reusable memory.
How is this different from an AI chat?
An AI assistant helps inside a conversation. Company OS preserves the company task, authority, evidence, outcome, and reviewed lessons around the work.
How should I start?
Open the guide, choose the Company Console or desktop path, and run one small task with clear boundaries and proof. Learn the operating loop before expanding authority.
What is a work credit?
One agent step: reading a page, calling a tool, or drafting an artifact. A typical scheduled template run uses 20 to 80 credits.
Does an approval cost credits?
No. Approving, rejecting, or reading a receipt is never metered.
Can I run it on my own machine?
Yes. The desktop app keeps the company record local. Credits meter model work, not storage.
What happens when I run out?
Scheduled workflows pause and read-only templates keep running from the daily allowance. Nothing is deleted.
Start with one bounded outcome.
Open the guide, choose the Company Console or desktop path, and run one small task with clear boundaries and proof. Learn the operating loop before expanding authority.