From empty to real

Cloud Control runs only real environments — there is no demo or dummy data anywhere. A brand-new organization is honest about being empty, and switches cleanly to real data the moment its first connection turns healthy.

Before your first connection

An organization that has never had a healthy cloud connection is served an empty console on every screen — an honest empty state with a Connect a cloud account call-to-action. No screen shows fabricated inventory, topology, cost or incidents.

The moment of cutover

The first time any of your connections reaches healthy, Cloud Control records that fact on your organization. The cutover is sticky — once set, it is never cleared — so a later connection problem does not throw you back to the empty state. From that point, `GET /api/console/data` serves your real, synced inventory, topology, resource detail and dashboard, shaped into the console's data types.

Per-section provenance and freshness

The cutover is per-section. The response carries a sections map labelling each area real, partial or empty, and a freshness map with a last-synced timestamp, a stale flag and an SLA per section. Inventory, topology and the dashboard cut over as soon as sync produces data; cost cuts over once billing has been ingested. A section with no real data yet is empty and shows an on-brand empty state rather than anything fake.

Non-destructive and isolated

• Real sections only ever contain your synced data — the shaper reads nothing else.
• A section with no real data yet stays empty rather than showing fabricated content.
• The cutover is a property of your organization alone; it has no effect on any other tenant.