# Celest > An entire company behind every person. Software gave every person tools. AI can give every person a company. Celest is building the operating system for AI coworkers: humans set direction, teammates carry real work, and one shared operating model keeps the company understandable. Celest is independent software and is not affiliated with or endorsed by Microsoft. ## Canonical facts - Company: Celest. - Category: The operating system for AI coworkers. - Homepage promise: An entire company behind every person. - Current commercial starting point: A fixed-scope, read-only Microsoft Agent Estate Review that turns scattered agent evidence into an accountable operating picture and a 30/60/90-day plan. - Day One promise: Show us your website. We'll build your team. - Product relationship: Agent Estate Review is the current starting point. Day One is the public proof of the same operating discipline applied to one new assignment. - Scope: Microsoft is where Celest goes deepest today, not where the company vision ends. - Team: Scout researches and cites; Manny builds a briefing; Harold independently reviews and accepts or materially revises it. They are generated roles, not Microsoft or Entra identities. - Personalized context: A submitted public company website seeds cited public-web research; it is not tenant evidence. - Live demo: When active, Day One runs bounded model and tool work in a disposable workspace with no Microsoft, customer-estate, mailbox, publication, or other external effect. - Northstar journey: The sample company path uses the same three role-separated turns and runtime as a personalized assignment. - Recorded/offline evidence: Recorded evidence shows the interaction; it is not a live run. - Retention: Disposable Day One sessions expire and are deleted within 30 minutes. - Lifecycle: Context, assignment, roles, capabilities, sources, handoffs, review, authority boundaries, artifact revisions, readback, receipt, reconciliation, and retirement/disposal remain one connected operating trace. Governance is the view that lets you inspect those bindings. - Current lifecycle: Agent Estate Review discovers and diagnoses read-only evidence. Day One demonstrates intent, team formation, equipping, work, review, and proof when its deployment is active. Connected teams that carry operating context forward are roadmap. - Authority model: Approval, execution, verification, and reconciliation remain separate gates, so every consequential step has a named owner and proof. - Trust model: Evidence before action, unknown remains unknown, authority stays explicit, and receipts close the loop. - Microsoft relationship: Celest complements Microsoft-native platforms and products; it is not affiliated with or endorsed by Microsoft. ## Primary pages - [Celest](https://celest.dev/): One place to understand and operate agents across Microsoft. The homepage leads with Agent Estate Review and uses Day One as public proof of the larger company thesis. Also available as [Markdown](https://celest.dev/index.md). - [Agent Estate Review](https://celest.dev/agent-estate-review): A read-only review that connects fragmented Microsoft agent records into one accountable operating picture and a 30/60/90-day plan. Also available as [Markdown](https://celest.dev/agent-estate-review.md) and [JSON](https://celest.dev/agent-estate-review.json). - [Estate Review preview](https://demo.celest.dev/reviews): Launch a preview of the Estate Review mission at `/reviews`. - [Day One team experience](https://demo.celest.dev/): Bring a public company website or start with Northstar, then watch the team research, build, and review. Live work and recorded playback are labeled directly. - [Sample Estate Review readout](https://celest.dev/agent-estate-review/sample): The shape of the deliverable on a labeled illustrative estate — canonical agent records, evidence-backed findings, named unknowns, a 30/60/90-day plan, and source coverage. Also available as [Markdown](https://celest.dev/agent-estate-review/sample.md) and [JSON](https://celest.dev/agent-estate-review/sample.json). - [The Agent Estate Review methodology](https://celest.dev/learn/agent-estate-review): Source-backed five-pass method for bounding an estate, qualifying evidence, preserving unknowns, producing deterministic findings, and creating an operating plan. Also available as [Markdown](https://celest.dev/learn/agent-estate-review.md), [JSON](https://celest.dev/learn/agent-estate-review.json), and a [Scoped MCP](https://celest.dev/learn/agent-estate-review/mcp). - [Celest Learn](https://celest.dev/learn/): Canonical, source-backed answers about operating and governing AI agent estates. - [What is an AI agent control plane?](https://celest.dev/learn/ai-agent-control-plane): Celest's definition, seven-stage operating loop, minimum canonical record, authority model, and limitations. Also available as [Markdown](https://celest.dev/learn/ai-agent-control-plane.md), [JSON](https://celest.dev/learn/ai-agent-control-plane.json), and a [Scoped MCP](https://celest.dev/learn/ai-agent-control-plane/mcp). - [Evidence, authority, and receipts](https://celest.dev/learn/evidence-authority-and-receipts): Celest's control model for keeping evidence, findings, proposals, authority decisions, handoffs, execution observations, and terminal receipts distinct. Also available as [Markdown](https://celest.dev/learn/evidence-authority-and-receipts.md), [JSON](https://celest.dev/learn/evidence-authority-and-receipts.json), and a [Scoped MCP](https://celest.dev/learn/evidence-authority-and-receipts/mcp). - [Analytics is evidence, not authority](https://celest.dev/learn/analytics-is-evidence-not-authority): A practical guide to using adoption, cost, and value analytics as evidence without mistaking a dashboard for ownership, authority, execution, or verified state. Also available as [Markdown](https://celest.dev/learn/analytics-is-evidence-not-authority.md), [JSON](https://celest.dev/learn/analytics-is-evidence-not-authority.json), and a [Scoped MCP](https://celest.dev/learn/analytics-is-evidence-not-authority/mcp). - [A practical guide to governing AI agents at work](https://celest.dev/learn/agent-governance-controls-matrix): A friendly guide to finding your AI agents, assigning owners, checking access and activity, and following changes through to verification. Also available as [Markdown](https://celest.dev/learn/agent-governance-controls-matrix.md), [JSON](https://celest.dev/learn/agent-governance-controls-matrix.json), and a [Scoped MCP](https://celest.dev/learn/agent-governance-controls-matrix/mcp). - [How to govern AI agents across Microsoft](https://celest.dev/learn/microsoft/agent-governance): A practical guide to reviewing one agent across truthful but partial records in Microsoft 365, Agent 365, Entra, Copilot Studio, Power Platform, Purview, Defender, Foundry, and GitHub. Also available as [Markdown](https://celest.dev/learn/microsoft/agent-governance.md), [JSON](https://celest.dev/learn/microsoft/agent-governance.json), and a [Scoped MCP](https://celest.dev/learn/microsoft/agent-governance/mcp). - [Privacy](https://celest.dev/privacy): Celest's first-party, no-cookie website analytics boundary, including a [machine-readable event manifest](https://celest.dev/analytics/manifest.json) and [Markdown](https://celest.dev/privacy.md). - [Celest on GitHub](https://github.com/celest-dev): Public open-source work from Celest. ## Agent interface - [Celest Learn MCP](https://celest.dev/learn/mcp): Public, anonymous, read-only Streamable HTTP server over the finite reviewed corpus. It exposes exact canonical Resources and two closed-world tools: `ask` and `similar`. - Every canonical Learn resource advertises a scoped `/mcp` child with the same two-tool interface. Scoped `ask` stays within that resource; scoped `similar` traverses to neighboring published resources. ## Evidence levels - Live: a mature capability Celest commits to contract, deliver, operate, and stand behind for every admitted customer scope. - Live when active: the Day One disposable model/tool journey described by the exact reviewed deployment and its receipt; it is not a Microsoft/customer effect. - Sample: a named, fictional company journey that still runs through the same real three-turn runtime when the live deployment is active. - Recorded/offline: deterministic browser evidence that demonstrates a projection without claiming a contemporaneous model or provider run. - Experimental: proven research behind replaceable or private contracts; not part of the durable public API. - Roadmap: intended product direction, not shipped capability. ## Contact - Email: founders@celest.dev