celest Explore the demo

Agent-native control plane for Microsoft

Turn agent sprawl into governed action.

Celest joins identity, ownership, tools, usage, cost, and risk across the Microsoft estate—then gives humans and agents one explicit path from evidence to a verified outcome.

Live in Dev · read-only Estate Review Next gate · propose + approve
estate / agent-042 illustrative
R
Renewals CopilotPublished · 214 assigned users
Finding
Identity
Studio ↔ Entra joined
Owner
unknown
Tools
4 connectors · 1 MCP
Cost
source unavailable
  1. 01DiscoverEvidenceSnapshot
  2. 02DiagnoseFinding
  3. 03ProposeLifecyclePlan
  4. 04ApproveAuthorityDecisionauthority gate
  5. 05Executebounded action
  6. 06VerifyExecutionReceipt
  7. 07Reconcilefresh observed state

The product earns autonomy. It never assumes it.

The operating gap

One agent.
Six partial truths.

An agent can cross products. Its identity, ownership, reach, tools, spend, and risk usually cannot. Each admin center is truthful about its slice—and blind to the whole.

Entra IDidentity · permissionsowner not recorded
Copilot Studiomodel · tools · statespend unavailable
Microsoft 365assignment · usagesource unknown
Power Platformmaker · environmentlineage incomplete
GitHubcode · reviewsruntime unlinked
Azurecost · runtimeagent attribution 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

The result is not another dashboard. It is durable state that humans and agents can safely reason from—every field traceable, every gap kept honestly unknown.

One governed loop

Start read-only.
Earn the right to act.

The interface is replaceable. The durable product is the evidence and authority accumulated between observation and outcome.

  1. 01Discover

    Collect scoped state with source health and provenance.

    Live · Dev
  2. 02Diagnose

    Turn supported evidence into deterministic findings.

    Live · Dev
  3. 04Approve

    Make human or policy authority explicit and inspectable.

    AuthorityDecision
  4. 05Execute

    Use provider-native actions inside a bounded scope.

    Roadmap
  5. 06Verify

    Observe the outcome; never confuse an API 200 with proof.

    Roadmap
  6. 07Reconcile

    Close the finding against fresh state—or reopen it loudly.

    Roadmap

Start here

The Microsoft Agent Estate Review.

A two-week, fixed-scope, read-only engagement. Software gathers and normalizes the evidence; together we turn fragmented ownership, capability, usage, cost, and risk signals into an operating plan.

2 weeksFixed scope Read-onlyLeast privilege Evidence-backedNo invented zeroes
Request an Estate Review

What you receive

  • 01Normalized agent inventory with source and join provenance
  • 02Ownership, lifecycle, tool, MCP, usage, cost, and risk findings
  • 03An executive posture report that preserves unknown and unavailable
  • 04Prioritized proposed work with evidence and expected outcomes
  • 05An authority workshop and 30 / 60 / 90-day AgentOps plan

Customer zero

We reviewed ourselves first.

Every claim is labeled by evidence. Live means implemented and tested in a bounded development environment—not a production service.

Live · Dev

Estate Review API

Fail-closed scoped sync, inventory, detail, findings, and local acknowledgement. Microsoft-facing routes remain read-only.

Live · Dev

Entra + Dataverse boundary

Claims-derived tenant and environment policy with dedicated control-plane persistence and source isolation.

Live · Dev

Power Apps surface

A signed-in Code App calls the protected API through one solution-owned connector with truthful provenance.

Experimental

Headless agent authoring

Copilot Studio model and tool discovery, create, save, and publish exercised end to end; private contracts remain quarantined.

Celest's cloud-infinity bird mark

YC W24 → now

Same insight.
Larger layer.

Dillon created Amplify Flutter at AWS, then took the original Celest through Y Combinator as “the Vercel of Flutter.” It removed the seams between what a developer intended and what the cloud required.

The actor has changed: it is now an organization of humans and agents operating the Microsoft cloud together. The seams moved up a layer—to identity, authority, evidence, cost, and work. The mission did not.

Remove the seams between intent and the cloud.

The loop is open

Your agents already span the estate.
Their operating model should too.

Explore the fictional estate, or bring us a bounded scope of your own.

Explore the live demo Talk to Dillon