A command centre for the one-person company
Empire OS turns the businesses you run into divisions, each with its own AI agents that do real work in your real files — researching, writing, shipping — while you watch every move on a native macOS dashboard. Every change is checkpointed. Anything can be undone.
Native macOS · runs on your machine · bring your own AI keys — pick the models, control the bill
Chat windows forget. Scripts run blind. Most "agent platforms" ask you to trust a black box with your actual files and give you nothing when it goes wrong. Empire OS was built the other way around: observability and reversibility first, autonomy second.
How it works
Your businesses and projects — each with status, health, revenue targets, its own colours, and a folder of documents that is its knowledge base.
The work queue, classified agent-ready or needs you. Due dates flow into Apple Calendar and Reminders — and checking off a reminder closes the task.
Standing missions with scoped tools and schedules. Run on demand or hourly-to-weekly, even while the app is closed.
SOPs and skills discovered from your folders, MCP servers, and API credentials injected at run time — never shown to the model.
A local engine on your Mac that runs agents, fires schedules, writes your daily briefing, and streams every event to the dashboard live.
Why you can let it run
File and shell tools resolve every path against your content root and refuse anything outside it — backed by an OS-level sandbox profile.
Every run and doc rewrite is bracketed by git commits. The Changes panel shows exactly what was touched; revert restores the pre-run state.
Agents log each call to the live feed with its input and result. The trace reads like a flight recorder, not a mystery.
Limit any agent to exactly the tools it needs — read-only research agents stay read-only.
Mail integration composes drafts for your review. By design, the system cannot send a message on its own.
Turn limits, command timeouts, and output caps mean a runaway agent stops itself.
The surfaces
The portfolio at a glance — a territory card per division with health arcs and agent pips, the pinned morning briefing, and a live feed where errors float to the top and agent activity collapses into an expandable trace.
The live cockpit. Type a command, scope it to a division, and watch the agent think and act — every tool call streaming in. Replay any past run with its cost, duration, file changes, and revert button.
Describe a goal and the Studio drafts the mission and system prompt, scores capability, flags gaps, and suggests what to equip. Tool policy, schedule, and deploy — one surface. It will even audit your division's documents and propose rewrites you review as line diffs, with batch apply and undo.
A persistent, tool-equipped chat per division. Sessions save automatically, resume with full context, and export to Notes or markdown.
Always present: attention items, what's next, recent changes. The empire runs even when the window is closed.
Your models, your bill
Empire OS doesn't resell AI — you plug in your own Anthropic and Gemini keys and pay your providers directly, at their prices. Pick the model for each job right in Settings: a frontier Claude model where agents touch your files, a fast Gemini model for briefings and document audits. The dashboard shows what every division spent this month, so the bill is never a surprise — it's a metric you manage.
Local-first
The Brain runs on your machine — no third-party server holding your company. API keys live in a private file on your Mac and are never echoed back, never synced, never stored in a shared database. Model calls go to the providers you chose; everything else stays home. Multi-Mac setups share one database; your documents sync however you already sync them.
FAQ
A Mac on Apple Silicon (macOS 15+) and an Anthropic API key — paste it during the guided setup and you're running in about fifteen minutes. Add a Gemini key any time to route the lighter work to a cheaper model.
Different jobs deserve different price points. Agent execution — the part that touches your files — runs on Claude, the strongest tool-using model family. Briefings, document audits, and command dispatch can run on Gemini Flash for a fraction of the cost. You pick both dials in Settings.
No. Paths are resolved and refused outside the content root, and shell commands additionally run under a macOS sandbox profile that denies writes elsewhere. With no root configured, execution is refused entirely.
Open the run, read the Changes panel, click Revert. Every run is bracketed by git checkpoints in a repo the agents can't touch. Document rewrites from the Studio have their own one-click undo.
Model calls go to Anthropic (that's the AI). Everything else — your database, your files, your credentials — stays on machines you control.
You pay your AI providers directly at their list prices — Empire OS adds no markup and meters nothing. Costs scale with how much you delegate, and the dashboard attributes every dollar to the division that spent it. Choosing smaller models for routine work keeps a busy portfolio surprisingly cheap.
Yes — a personal edition drives everything through a Claude Max login on your own Mac with no per-token cost at all. It's how Empire OS runs its own maker's company every day.
Not a demo
Empire OS isn't a mockup with sample data. It runs Ayres Capital Enterprises — a real portfolio of Canadian businesses — every day. These are the divisions on the dashboard. Each one is a live company; go have a look.
AI automation consulting for small business — and the maker of Maestro.
An independent imprint publishing near-future fiction under the pen name Dewar Yearns.
Home services done right — landscape & interior design, maintenance, smart-home & security.
Curated goods from Canadian makers.
Learn real-world skills, one hands-on micro-lesson at a time. iOS.
Sourcing the collector cars of the 80s, 90s & 00s for the people who love them.
Empire OS runs a real multi-brand portfolio every day — briefings at dawn, agents on schedule, every change revertible. Early access is opening to a small group of operators. Bring your keys; keep your margins.