These aren't hypothetical. They are the everyday moments where having your products working together — instead of four disconnected tools — pays for itself.
HR creates the person in the HR system. IT gets an email. IT creates an account in the directory, adds them to the VPN, creates an email mailbox, adds them to the ticketing system, provisions a wifi certificate, grants file server access, adds them to the CRM, and sends the welcome email. Six systems. Forty-five minutes of clicking. One of those steps gets forgotten this week — we won't find out which one until they can't open a ticket.
HR enters the person in the directory. Role: "Account Manager." The event propagates through the databus: this person exists, their role is account-manager, their certificate is issued, their policy is loaded. Every connected product updates: the firewall lets them in, VPN accepts them, wifi issues their device a certificate, CRM grants them the right permissions. Done in 60 seconds. Consistent across everything.
HR closes their record. IT gets an email. IT disables the directory account — but forgets the VPN database, which is separate. Forgets the firewall rule granting their laptop SSH access to production. Forgets the SaaS apps. The employee's credentials remain active, across multiple systems, for days or weeks. This is one of the most common breach vectors — "ex-employee still had access."
HR closes their record. The revocation propagates through the databus to every connected product. VPN disconnects. Wifi certificate revoked. Firewall rule withdrawn. SaaS apps notified. Audit log records the full sequence — time-stamped, signed. Next time the auditor asks "when was this person's access removed?" the answer is a single query.
You have 400 devices with certificates. You have spreadsheets tracking expiration dates. You have email reminders set up — that nobody reads. Every 90 days from now on, someone on your team will spend a full week rotating certificates, remembering which devices got skipped last time, and apologizing to customers who hit expired-certificate errors on the weekend.
Your internal services use certificates issued by your own authority — managed through coordinated certificate management across your products. The rotation schedule is your choice. The process is automated. Public-facing certificates are still issued by a public CA (where appropriate), but those are a small minority of your total. The 90-day change affects a handful of public-facing endpoints, not 400 internal systems.
That data lives in three places: the database's own audit log, the VPN connection log, the identity provider's sign-in report. Reconciling them takes a week. Some entries don't match because clocks drifted. Some entries are missing because the database's log rotated early. You produce a report that you're 80% confident in.
"Show me everyone who accessed the customer database last month." One query against the shared audit log. Every connected product reports into it — time-stamped, signed, tamper-evident. The auditor gets the answer in five minutes. The report is verifiable. Your audit findings go down.
Employees can't log into the VPN, the CRM, the ticketing system, or anything else that federates through the cloud identity. Your own infrastructure — your servers, your switches, your backups — is fine. But your people can't get to any of it. You spend 6 hours fielding "is it just me?" calls.
Your core identity lives on your own product appliances. Employees log into your VPN, your internal tools, and your local services just fine — those rely on your sovereign identity. External services (the ones that actually integrate with the cloud identity) are affected, but your core operations continue. You open a ticket with Microsoft and get back to your day. For a trading floor or a financial services firm, those 6 hours of downtime aren't just inconvenient — they're measurable in missed trades, regulatory exposure, and client trust. Sovereign identity means the core of your business never stops because someone else's cloud had a bad day.
Your employee directory lives in a cloud identity provider, with data in four regions across two continents. The migration project means rebuilding every integration that depended on the cloud directory. Cost: 4 months of engineering, 6 figures in professional services, 2 planned outages.
Your directory runs on your DEC-LLC appliances — in your datacenter, your cloud tenant, wherever meets the residency requirement. You write a two-sentence compliance attestation: "Our employee directory is stored on appliance X, physically located at address Y." The auditor nods. The law is satisfied. You get back to your actual job.
Not to sell you a separate product. To remove the class of problem these stories describe — by making the coordination layer something that emerges when your products work together, on hardware you own.
Back to Vision See How It Works