The Vercel of Flutter
Developers defined cloud infrastructure in their own language and IDE, instead of fragmenting themselves across consoles and domains. Celest removed the seams between what a developer intended and what the cloud required.
The agent-native control plane for the Microsoft cloud
Mission control for the Microsoft agent estate.
Enterprises are deploying AI agents across Microsoft 365, Copilot Studio, Power Platform, GitHub, and Azure — then operating them by clicking through a dozen disconnected admin centers. Celest is the control plane that gives humans and agents one canonical view of the estate, and a governed path from what's true to what's done.
Microsoft 365·
Copilot Studio·
Power Platform·
Entra·
Azure·
GitHub·
Azure DevOps
2024 → 2026 · the same insight, one layer up
Celest is reborn — not pivoted.
The control plane for the Microsoft cloud
The builder grew from a Flutter developer into a human-plus-agent organization. The cloud narrowed to the Microsoft substrate where enterprise identity, work, code, and automation already live. The seam is the same — and it's wider than ever.
“Celest removes the seams between what a builder intends and what the cloud requires.”
The problem
One agent. Six admin centers.
No single source of truth.
Microsoft is assembling an agent platform across Entra, Microsoft 365, Copilot Studio, Power Platform, Foundry, Agent 365, GitHub, and Azure. Each product exposes a slice of state. The operating lifecycle crosses every boundary — and no one owns the whole.
Entraidentity, permissions
Copilot Studiomodel, tools, publish
Power Platformmaker, environment
Microsoft 365usage, sharing
GitHubcode, reviews
Azurecost, runtime
canonical join
A
Aurora Support
one identity · one owner · one lifecycle
join confidence 0.94 · environment matched
- Which agents exist — and which records refer to the same agent?
- Who owns and sponsors each one?
- What models, tools, connectors, and identities can it use?
- Is it published, deployed, blocked, or quietly abandoned?
- Who uses it, what does it cost, and is it failing?
- What should happen next — who can authorize it, and did it actually work?
The control plane
Knowing isn't doing.
Celest owns the transition.
Native dashboards can show you a slice. The missing product is the governed path from fragmented evidence to a verified outcome — with explicit identity, authority, evidence, policy, and receipts at every step.
01Discover
Snapshot the estate with source health and provenance.
Live
02Diagnose
Deterministic findings — never from a guess about state.
Live
03Propose
Proposed work and predicted effects, with rationale.
Next
04Approve
An explicit human or policy authority decision.
Roadmap
05Execute
Provider-native mutation, in bounded scope.
Roadmap
06Verify
Re-read the world — an API 200 is not an outcome.
Roadmap
07Reconcile
Close the finding against an immutable receipt.
RoadmapEvidence before action.No lifecycle step begins from an unproven guess.
Unknown is not zero.Missing data stays unknown — it can't justify cost, risk, or deletion.
Authority is data.Every consequential action has an inspectable actor, scope, and policy basis.
Receipts close the loop.A success response is not the same as an observed outcome.
The Microsoft AI Operations Stack
Land on one layer.
Expand across all of them.
LicenseOps
Seats, adoption, utilization, renewal evidence.
CreditOps
Attribute Copilot Credits and agent spend to owners and outcomes.
GuardOps
Readiness, oversharing, identity, and policy risk — evidence-backed.
AgentOps
The canonical registry, lifecycle, authority, and receipt layer.
Celest's wedgeWorkflowOps
Transform business processes with agents and Power Platform.
The user interface is replaceable. The durable product is the canonical lifecycle and the evidence it accumulates — reachable from Web, Power Apps, chat, MCP, API, and CLI.
What's real today
We label our own evidence.
A YC-honest ledger. Live means implemented and tested in the current dev boundary — not a production service. Experimental is quarantined and replaceable. Roadmap is intent, not a promise.
CapabilityWhat's establishedStatus
Canonical contractsVersioned collection runs, agent snapshots, identity & join provenance, findings.Live
Read-only Estate Review APIFail-closed scoped sync, inventory, detail, findings, local acknowledgement.Live
Entra & environment authValidates Entra access; enforces claims-derived tenant + exact environment policy.Live
Durable Dataverse persistenceFive-table schema, alternate keys, canary roles, app-user boundary — proven in dev.Live
Power Apps Code AppSigned-in app calls the protected API through one solution-owned connector, with live provenance.Live
Hosted Azure control planeDigest-pinned Container Apps revision passed health, workload identity, and readback checks.Live
GitHub review & issue stewardshipAgentic workflows review PRs and reconcile issues — our own lifecycle laboratory.Live
Copilot Studio authoringHeadless OAuth, model/tool discovery, create/configure/publish. Some contracts are private.Experimental
Azure DevOps adapterCanonical provider strategy articulated; no product adapter implemented yet.Roadmap
Multi-tenant commercial serviceArchitecture anticipates tenant partitioning; onboarding, billing, and SLAs are not built.Roadmap
The supported live source has so far produced a valid empty estate. That's not a gap we hide — it's the difference between zero, false, unknown, and unavailable, honored end to end.
Why now
Microsoft is building the substrate.
The customer still owns the seams.
The window won't stay open. Microsoft will improve its native dashboards — so Celest wins on cross-surface workflow, evidence continuity, customer policy, provider breadth, and speed of operationalization, not on a temporary endpoint.
01Canonical longitudinal state
A normalized history of identity, config, evidence, decisions, and outcomes across surfaces.
02Lifecycle semantics
Tested contracts for partial knowledge, authority, reversibility, receipts, and reconciliation.
03Provider capability graph
What each provider can observe or do, under which identity and stability boundary.
04Embedded workflows
Present where humans and agents already work: Power Apps, M365, GitHub, MCP, and APIs.
Why this founder
Built a platform inside a hyperscaler. Built a startup to remove cloud fragmentation. Doing it again — one layer up.
Dillon created Amplify Flutter at AWS, saw developers struggle with the seams between application and cloud, and built the original Celest around that pain — through YC W24. Reborn Celest emerged from directly reverse-engineering and operating a real Microsoft tenant, not a market map. And Celest is Customer Zero for the agent-native operating model it sells.
Put your agent estate under mission control.
Celest is onboarding a small number of Microsoft-centric design partners. If you're feeling agent sprawl, governance pressure, or unexplained Copilot cost — let's talk.
Read-only by default · least privilege · tenant identifiers excluded · every consequential action leaves a receipt.