One record for the company,
and agents that work inside it.
MiraOS is the operating system for a company: its people, its work, its customers, its money and what it knows, in one application instead of a dozen. Seven agents read and write that record with the permissions of the person who asked, and the audit log names both of them.
Live at os.miranium.ai, with workspaces opened on request.
The whole company, in one record.
MiraOS is the operating system for a company. It holds the four things every company runs on — its people, its work, its customers and what it knows — plus its money, in one record, so a promotion, a won deal and the project that follows it are the same history rather than three exports.
Agents work inside that record rather than beside it. Ask Mira a question and she consults the specialist that owns the answer: people, delivery, revenue, the librarian or meetings. Every tool runs as the person who asked, through the same tenancy checks and the same permissions, and the audit log names both the agent and the person it acted for.
Automations are the same agents on a trigger. When a deal is won, the revenue assistant briefs delivery; when somebody is hired, the people assistant checks onboarding; every Monday at nine, the chief of staff writes the week’s digest. Each one starts by reporting what it would do, and a person decides when it may write.
Miranium AI is tenant one: the first company in the database, holding the same privileges as every company after it. MiraOS runs this company every day, which keeps the path a customer uses the path its builders use.
-
One record
A customer’s account page shows the deals and the delivery work together, because they are one relationship. A person’s record keeps its history: every promotion, move and change, dated.
-
One permission model
Compensation is visible to an administrator, to your manager, and to you, enforced in one function every screen and every agent calls.
-
One assistant
Mira answers across every area, cites the page or record each answer came from, and works within what the person asking may see.
-
One audit log
Every change is recorded against the person who made it, or against the agent and the person it acted for.
Everything a company runs on, in one place.
MiraOS replaces the project tracker, the HR system, the CRM, the wiki and the spreadsheet that joins them. Each area below is a module of the same application, reading and writing the same record.
Work
A key, a board, milestones and stable task references
Every project, sprint and milestone with a date
What the company is aiming for, and the tasks underneath
Share one project with a client, who sees that project alone
People
Who reports to whom, drawn from the record
Requests, approvals, and balances computed from them
Review cycles, pay bands and raises
One action creates the employee and starts a dated onboarding board
Pay periods, what was paid, plans offered and elections
Customers
Each stage carries its own probability, and closing a deal is a stage too
A product catalog, priced quotes, and campaigns to leads
Tickets against the account they came from, with internal notes kept separate
Each time entry attached to its invoice, so it is billed once
Money, knowledge and meetings
Bank and card lines, categorised with tax lines, by month, quarter or year
Nested pages, saved as you type, and answerable by the agents with citations
Joins the call, transcribes it, and turns what was agreed into tasks
Control
Ask for a role; your manager approves first, then an administrator
What is changing, when, the rollback plan, and who agreed
The record of getting a service back, as it happened
Every change anybody made, filterable by time
Seven agents, each with a job.
Ask Mira anything and she consults the specialist that owns the answer. Each agent has its own tools and its own model tier, and every one of them works as the person who asked.
| Mira | The one you talk to. Reads the question, consults the right specialists, and writes the answer with its sources. |
|---|---|
| People assistant | The directory, time off, reviews, hiring and the handbook. |
| Delivery assistant | Projects, tasks, sprints, milestones and logged time. |
| Revenue assistant | Leads, the pipeline, accounts, quotes and campaigns. |
| Librarian | The knowledge base: finds the page, quotes it, and cites the section. |
| Meetings assistant | Notes, decisions and follow-up tasks from the company’s calls. |
| Chief of staff | Runs the automations and the scheduled digests, with the widest set of tools. |
-
The roster is the ceiling
What each agent may do is written in code and reviewed like code. A company’s settings narrow it from there.
Code -
The person’s permission
Every tool runs as the person who asked, through the same tenancy checks and the same 67 permissions a screen uses.
Same rules -
Reads first, writes by choice
An automation starts in reports-only mode and shows what it would do. A person reads a few runs, then lets it write.
Reports only → writes -
Logged as both
A write is recorded as the agent, for the person, in the same transaction as the change itself.
agent:revenue, for Amara
Runs on the model you choose
Anthropic or OpenAI, chosen per deployment, with each task assigned a tier — fast, standard or deep — that maps to a model. Every call is charged to the company it served, against a monthly allowance a platform operator sets. A built-in deterministic planner covers local use, answering from the read tools alone.
When something happens, an agent acts on it.
An automation is a sentence: when this happens in the business, ask this agent to do that. It runs with the same tools, the same permissions and the same audit trail as a person’s question, through a durable queue that picks up where it left off after a restart.
On a business event
Twenty-one events named after the business rather than the table: deal.won, employee.hired, change.approved, task.blocked, document.published and sixteen more.
On a schedule
A cron line in the company’s own time zone. The Monday morning digest runs at nine and tells the team what happened last week and what is due.
With its reasoning shown
Every run keeps its transcript: which tools it called, what came back, and what it said. Test an automation before it goes live and read exactly what it would have done.
The front door for the rest of your tools.
MiraOS signs people in, signs them in to the rest of the Miranium product family, and lets outside agents and apps work with the record as the person who connected them.
Company accounts, placed in their company’s workspace by domain
One account for MiraShield and every app after it, with an entitlement per person per app
An outside agent acts as the person who connected it, and the log reads “Claude Code, for Ray Han”
Add an app for the company; removing one hides it and keeps its records
Transactions arrive categorised, with a CSV import beside them
A notetaker joins the call; notes from a customer call land on that account’s timeline
The CRM itself is a marketplace app, installed by default: its screens, its API and its agent tools all follow the installation, which is how every app after it will work.
Every company apart, every change attributed.
MiraOS holds salaries, customers and bank lines for many companies at once. The separation between them is enforced twice, and every change carries a name.
| Tenancy in the application | Every query is scoped to the company in the request, and fetching a record by its id checks the company as well. |
|---|---|
| Tenancy in the database | Postgres row-level security on every company-owned table, applied to the role the application connects as. |
| Permissions | 67 permissions in one model. Compensation, for example, reaches an administrator, your manager, and you. |
| Audit | Recorded inside the same transaction as the change, so the log and the data always agree. |
| Agents | Logged as the agent and the person it acted for, so every agent action traces to an accountable human. |
| Platform operators | One permission, held in one company and assigned through IAM, so every operator is visible and audited. |
Live, and running this company.
MiraOS is in production at os.miranium.ai, and Miranium AI runs its own work, people and customers on it every day.
The approval contract and the audit discipline MiraOS runs on are the same ones behind Gable Pro and MiraShield.