Celest
Sections
See review scopeReview scope

For teams running agents on Microsoft

Your Microsoft agents are real.
The seams around them are too.

Your agents already live across Copilot Studio, Microsoft 365, Power Platform, Azure, GitHub, and Azure DevOps. Celest shows you what exists, who owns it, and where things break across them.

Request an Estate Review Explore the demo See what you receive
  • Read-only first see the estate before action
  • Authority stays explicit action waits for a real decision
estate / agent-042 illustrative
R
Renewals CopilotPublished · 214 assigned users
Identity
Studio ↔ Entra joined
Owner
unknown
Tools
4 connectors · 1 MCP
Cost
source unavailable
  1. 01DiscoverEvidenceSnapshot
  2. 02DiagnoseFinding
  3. 03ProposeLifecyclePlan
  4. 04ApproveAuthorityDecisionauthority gateawaiting authorityapproved
  5. 05ExecuteRoadmap only · bounded action
  6. 06VerifyRoadmap only · ExecutionReceipt
  7. 07ReconcileRoadmap only · fresh state check

Roadmap only Stages 05–07 show the broader operating model after approval. This read-only Estate Review stops at discovery, diagnosis, proposal, and authority.

The control plane earns autonomy. It does not assume it.

Illustrative Celest lifecycle view.

Why Celest

Microsoft is building the platform.
You still own the seams.

Celest exists because we ran into this ourselves. An agent can cross Entra, Microsoft 365, Copilot Studio, Power Platform, Azure, GitHub, and Azure DevOps, while ownership, tools, usage, spend, and risk stay scattered across them. Each admin surface is truthful about its slice and blind to the whole.

Microsoft source records joined into one canonical agent record

Entra IDidentity · permissionsowner not recorded
Copilot Studioagent · tools · statespend unavailable
Microsoft 365assignment · usagesource unknown
Power Platformmaker · environmentlineage incomplete
GitHubcode · reviewsruntime unlinked
Azure DevOpswork · release stateagent join missing
canonicalagent:0426 source observations
Identity
Renewals Copilot Studio + Entra
Owner
unknown no accountable sponsor
Lifecycle
published · assigned · idle 41d
Cost
unknown billing source unavailable
Source health
5 / 6 available

Celest turns scattered admin truth into one accountable view.

The real comparison

“Doesn’t Microsoft
already do this?”

Pieces of it — and that is the problem. Agent governance on Microsoft is real, but it is distributed across more than a dozen admin surfaces, each with its own scope, licensing, maturity, terminology, and admin boundary. Each one answers its own question truthfully. None of them answers the question you actually have: what do our agents look like as one estate?

Microsoft 365 admin center + Agent 365registry · access · observability
Entraagent identity · lifecycle · Conditional Access
Purviewdata compliance · DLP · audit
Defenderthreats · posture · incidents
Power Platform admin centerenvironments · makers · connectors
Copilot Studioagent definitions · channels · analytics
SharePoint Advanced Managementcontent access · oversharing
Security Dashboard for AIAI-specific security posture
Foundrymodel + agent runtime telemetry
Fabricdata estate + capacity signals
GitHub Copilotcoding agent usage + policy
Security Copilotsecurity workflow agents
Dynamics 365business-process agents

Agent 365 is an important part of that picture — not the whole answer. Celest joins these surfaces into one accountable record per agent, with evidence, unknowns, and next steps attached. And the better Microsoft’s primitives get, the more Celest can join: every new admin surface is more evidence for the estate, not a replacement for it.

Start here

Start with a read-only Agent Estate Review.

A fixed-scope, read-only review for teams that already feel the sprawl. We gather the evidence, show what actually exists, name what is still unknown, and turn it into a practical operating plan.

2 weeksFixed scopeRead-onlyLeast privilegeActionable30 / 60 / 90-day plan
Request an Estate Review

What you get

  • 01A normalized inventory of agents, owners, tools, and environments
  • 02Findings on overlap, gaps, risk, usage, and unknowns
  • 03An executive readout your team can actually act on
  • 04A prioritized 30 / 60 / 90-day operating plan

See a sample readout

The product

Don’t take the narrative’s word for it.

The public demo runs the same review surface on a clearly labeled illustrative estate — no login, no connectors, nothing leaves the page. Open it, click through a finding, and check whether the evidence separation is real. Then read the matching sample readout.

The Celest agent estate view: a selected agent record showing its mandate, accountable owner, authority boundary, tools in scope, risk assessment, and recent activity.
One accountable record per agentMandate, owner, authority, tools, risk, and activity — joined from the systems that actually hold them.
The evidence coverage view: three sources listed with separate freshness, coverage, and collector status, including one collector marked not established.
Unknowns stay unknownCoverage, freshness, collector state, and known limitations are separate fields — missing evidence is a named gap, never a silent zero.
The review queue: one high-severity least-privilege finding waiting for a human decision, with evidence attached and a note that nothing executes from the preview.
The human stays the authorityFindings arrive as proposals with evidence attached. Approval is a decision a person makes, not a default the system takes.
A focused review walking from finding to evidence, proposed work, approval, work item, and receipt, keeping each stage separate.
From signal to receiptFinding, evidence, proposed work, approval, work item, and receipt stay separate — so approval never implies execution.

The demo estate is fictional and labeled as such. Explore the demo  ·  Read the sample readout

Celest's cloud-infinity bird mark

Why us

We built this by living the problem.

Dillon created Amplify Flutter at AWS, then took the original Celest through Y Combinator as “the Vercel of Flutter.” Celest started with the same instinct it has now: remove the gap between what people mean to do and what the cloud makes painful.

Now the builders are humans plus agents, and Microsoft is assembling the substrate where they work. We are building Celest by running straight into these seams ourselves, which is why the product starts with accountability instead of magic.

Today that means a live Estate Review API, a signed-in review surface, a public demo that does not fake liveness, and a headless Microsoft path that stays clearly experimental until it earns more trust. Live means a mature capability Celest is prepared to contract, deliver, operate, and stand behind.

See Celest's YC W24 origin Read the source-backed methodology
The agents are real. The operating model has to be too.

A deeper Celest path

Bring us the seams
your estate can't explain.

Two weeks from scattered Microsoft records to one accountable operating picture and a plan.

Request an Estate Review Start here