Hardened governance for complex reality.
Closed-loop identity governance across legacy, cloud, non-human identities, and AI agents — without rip-and-replace, inbound firewall changes, or year-long implementation cycles.
30-Day Proof of Revoke POC. Outbound-only mTLS. Immutable SHA-256 evidence chain. Founder-led implementation.
Available Now, Private Beta, and Roadmap states are documented per module in the Connector Maturity Matrix.
Names of third-party products are trademarks of their respective owners. Maturity breakdown at stratusaccessgov.com/trust
The big IGA platforms were built for the world you used to have — massive deployments, rip-and-replace migrations, modules priced like enterprise software, months of network team negotiation to open ports.
The cloud-first IGA platforms were built for the world that doesn't exist yet — everything in SaaS, mainframes don't matter, PeopleSoft is somebody else's problem.
STRATUS is built for the world you actually run. Active Directory and Workday. Mainframe and Snowflake. Service accounts and AI agents. PeopleSoft you can't replace and a network team that won't open a port.
Neither incumbent is wrong for what they are.
They're just not built for the team that needs governance shipping in 30 days, not 30 months.
A CISO, a CIO, an IAM Director, and a Compliance lead each evaluate STRATUS through a different lens. The system is one platform — here is what matters to each seat at the table.
Outbound-only mTLS architecture. Closed-loop revoke with cryptographic Evidence Pack. Kill switch with two-person approval and 24-hour reversibility. Independent immutable evidence chain separate from application/database audit controls — for the breach investigation no one wants to need.
Start the conversation →
30 days to closed-loop revoke on a real production target — not 30 months. No rip-and-replace of your existing identity stack. Coexists with SailPoint, Saviynt, or whatever your enterprise IGA program looks like today. Founder-led implementation; the team that ships the product is the team that takes your call.
Start the conversation →
AD, Okta, AWS, Workday, Entra, GCP, Salesforce, GitHub, Snowflake — Available Now. PeopleSoft, Oracle EBS, SAP, ServiceNow — Private Beta with explicit per-system maturity in the Evidence Pack. Roadmap influence as a Founding Partner; the next connector we build is the one your stack actually needs.
Start the conversation →
NIST 800-53, SOX § 404, HIPAA § 164.308, CJIS § 5.5, HITRUST CSF — control mapping documented. SoD enforcement at request time, not after the violation. Independent immutable evidence chain separate from application/database audit controls. Sample Evidence Pack and methodology note available under NDA.
Start the conversation →
Identity sources, target systems, evidence destinations, and the legacy stack other vendors will not talk about. Available Now, Private Beta, and Roadmap states are documented per system in the Connector Maturity Matrix.
Names of third-party products are trademarks of their respective owners and are used here in their nominative sense for compatibility reference. STRATUS is not affiliated with, endorsed by, or sponsored by any of these vendors. Full per-system Discover / Certify / Revoke / Evidence breakdown lives in the Connector Maturity Matrix.
Okta authenticates. SailPoint governs at enterprise scale. STRATUS proves revoke across the messy systems you already run — in 30 days, outbound-only, with immutable evidence. We sit alongside, not in front.
You don't have to rip out a working IGA platform to get hardened forensic evidence and zero-inbound architecture. STRATUS deploys as a fast-start governance layer alongside your existing stack — designed for high-density governance without administrative overhead, closing gaps your incumbent doesn't reach.
Traditional IGA audit trails often depend on application-layer and database controls. STRATUS sits adjacent and writes SHA-256 hash-chained Evidence Packs to S3 Object Lock in Compliance Mode — tamper-evident, retention-protected, auditor-grade independent of the source IGA. Same controls. Independent proof layer.
The legacy targets your incumbent struggles with — governed via outbound-only HCG. AD, Okta, AWS, and SaaS available now. PeopleSoft and Oracle EBS in Private Beta. RACF/mainframe on the Roadmap — disclosed upfront. No firewall change requests. No VPN. Network review is simpler because there is no inbound listener, VPN, or firewall opening — they still evaluate egress, mTLS, logging, data flow, and vendor risk, but the surface to be evaluated is much smaller.
Your 18-month SailPoint migration doesn't have to deliver year-one value. STRATUS surfaces ghost accounts in 72 hours and runs closed-loop revoke in 30 days — buying you time, evidence, and a working control while the bigger program continues.
STRATUS does not replace your IdP. We treat Okta as an authoritative identity source — STRATUS proves revoke across Okta, AD, AWS, SaaS, and your legacy stack without changing your authentication path. Okta keeps doing what it does best; STRATUS handles the closed-loop offboarding evidence Okta never claimed to.
SailPoint is governing at enterprise scale on the systems it has reached. STRATUS adds outbound-only coverage and immutable evidence for the gaps your migration has not closed yet — PeopleSoft revoke flows, legacy AD edges, non-human identities, AI agents. Run STRATUS in parallel as the fast-start layer while the broader program matures.
Most IGA platforms make you choose: rip-and-replace your legacy stack, or live with the leaver bleed. STRATUS does neither. We bridge what you have today, and close the bleed in 30 days — no replacement, no inbound ports, POC-ready before broader procurement.
Govern legacy and cloud side by side. PeopleSoft you can't replace works alongside the AWS account you provisioned yesterday. No rip-and-replace. No big-bang migration.
Hybrid Connector Gateway dialed in over outbound mTLS. HR signal in, revoke fans out across connected systems in seconds — each connector labeled by its Discover / Certify / Revoke maturity. Every ghost account surfaced and closed.
Every policy decision SHA-256 hashed and written to S3 Object Lock in compliance mode. STRATUS adds a separate hash-chained evidence layer so tampering becomes mathematically detectable. The auditor sees the chain; the attacker leaves a verifiable trace.
A flat row in a database, dependent on RDBMS access controls. An attacker with sufficient privileges can edit or remove records, and the standard log structure does not preserve a tamper-detectable chain. STRATUS adds a separate immutable evidence chain so tampering becomes mathematically detectable.
Hash-chained, signed, and locked at write time. Under S3 Object Lock in Compliance Mode with customer-controlled retention, the record is tamper-evident and retention-protected within the configured evidence boundary. When the auditor asks "prove it" — you do, with math.
Four weeks from kickoff to closed-loop revoke on a real production target. If we can't show a working closed-loop revoke in 30 days, you don't move forward. No questions. No salvage attempt.
Deploy Hybrid Connector Gateway inside your VPC (confirmed during scoping call). mTLS tunnel established. Identity sources connected (HR + AD).
Normalize identities across legacy + cloud. Run Ghost Account discovery — surface every terminated user with live access.
Validate decision paths. Workflow approvals. Dry-run revoke with full audit chain — without firing the kill switch yet.
Execute first live closed-loop revoke on a real target. Evidence Pack signed, hashed, and locked into S3 Compliance Mode.
Most security vendors decorate their homepages with placeholder dashboards. These are design mockups of actual STRATUS surfaces — the Kill Switch operator console, the Identity Graph for a terminated user, the live Connector Health board, the hash-chained Audit Trail. Every figure labeled with what it represents and what level of capability it shows. Real product screenshots replace these as we deploy with Founding Partners.
High-contrast destructive action. Two-person approval required. Reversible within 24 hours via cryptographic rollback receipt. No surprise irreversibility — operators can move fast without operating blind.
Figure 1 · MockupKill Switch console at the moment a Workday termination event has fanned out a revoke request across 14 connected systems. Pre-execution view — operator must type "REVOKE" to commit. Two-person approval already satisfied (timestamp shown).
Single identity, both worlds. PeopleSoft Admin and AWS IAM-Power on the same person — STRATUS finds the toxic combination and the orphaned ghost-access in one query. Legacy and cloud governed against one source of truth.
Figure 2 · MockupOne terminated identity (j.doe) graphed against its source of truth (Workday) and six target-system entitlements split across legacy and cloud. The toxic combinations are surfaced automatically — operator clicks any node to see provenance and trigger the revoke flow.
Live operator board. Heartbeat every 15 seconds, mTLS verified, discover/certify/revoke capability shown per connector. No vague green checks — partial support, workflow-only paths, and partner-dependent flows are labeled exactly.
Figure 3 · MockupOperator console view of seven representative connectors with last-sync timestamps and the precise Discover / Certify / Revoke capability vector per system. Partial, workflow-only, and partner-dependent flows are flagged inline rather than collapsed into a single green check.
Every event hash-chained. Modify any record and the entire downstream chain breaks — detectable in milliseconds, provable with math. Locked into S3 Object Lock at write time with 7-year retention.
Figure 4 · MockupFour events from a single terminate-revoke chain: HR signal in, revoke initiated, revoke approved, revoke executed. Each event's SHA-256 hash includes the previous record's hash — alter one record and every downstream record is mathematically broken.
Before you spend 18 months replacing your existing IGA, prove revoke across your real legacy + cloud stack in 30 days. Outbound-only, with immutable evidence your auditor can verify. Then expand into certifications, SoD, NHI governance, AI-agent controls, and the rest of the platform as your program matures.
Paid Founding Partner engagement. Connect HR + identity + one or two target systems. Closed-loop revoke on Day 30. Pricing credits toward year-one contract upon conversion.
Roll out remaining connectors per the Maturity Matrix — AD/Okta/AWS first, then Workday/Salesforce/GitHub, then PeopleSoft/Oracle/SAP under the Private Beta path.
Expand into quarterly certifications, SoD enforcement, non-human identity governance, AI agent controls, CIEM, and the full 10-pillar platform as your program matures.
The 30-Day Proof of Revoke is structured as a paid Founding Partner engagement — credited toward year-one contract upon conversion. See the Founding Partner Program for full structure.
Ready to validate in a design-partner POC. JML, Evidence Vault, HCG outbound mTLS, AD, Okta, AWS, Entra, GCP, Workday, Salesforce, GitHub, Snowflake.
Functional but limited to selected design partners. AI Agent Governance, Entitlement Translation (LLM), ITDR, ServiceNow, PeopleSoft, Oracle EBS, SAP.
Planned. Not sold as production-ready. Mainframe/RACF Bridge, DSPM, FedRAMP High Authorization.
Requires customer environment, vendor API tier, or custom connector. ServiceNow workflows, custom ERP integrations, uncommon legacy revoke paths.
Full per-module breakdown: see the Connector Maturity Matrix in the Trust Center.
Most IGA platforms ship four or five modules and call it a suite. AccessGov ships ten pillars — depth, not feature checkboxes.
JML · Risk Scoring · NHI · Digital Twin · Predictive Lifecycle AI · PII Encryption
8 modulesCatalog · Birthright · JIT · Emergency Access · Simulation · Delegations
8 modulesCertifications · SoD · Role Mining (AI) · Audit · Compliance · Evidence Packs
8 modulesUEBA · ITDR · Attack Path · Shadow Access · CIEM · Blast Radius · Kill Switch · DSPM
9 modulesRemediation Center · Access Debt · Pruning · Orphan Cleanup · Drift Reverse
9 modulesAI Guardrails Private Beta · AI Agent Governance Private Beta · Entitlement Translation (LLM) · Access Graph
9 modulesAD · Entra ID · Okta · AWS · GCP · Workday · Salesforce · GitHub · Snowflake · CyberArk available now. PeopleSoft · Oracle EBS · SAP · ServiceNow in private beta. RACF/mainframe on the roadmap.
connectorsSSO/SAML/OIDC · Adaptive Access · Gateway · SCIM Outbound · Session Mgmt
6 modulesWorkflow Designer · Orchestration · GitOps Policy as Code · ChatOps · SaaS Discovery
7 modulesCAEP · MCP Agent Gateway · BYO-KMS · Mainframe Bridge Roadmap · SOC Webhook · Legacy Bridge
12 modulesAfter fifteen years inside identity programs at IBM and Oracle, Sirisha ran a study across 47 enterprises. Here's what every single one of them was missing.
The average gap between an employee leaving and their access being revoked. Long enough to exfiltrate, commit, or pivot. Every single time, the security team had no idea it was happening.
MethodologyThe 4h 17m figure reflects the mean termination-to-revocation gap measured across 47 enterprise studies conducted FY2025 across mixed legacy + cloud environments. The 8-second closed-loop time is STRATUS lab-environment measurement from HR termination event in to evidence pack sealed across AD, Okta, and AWS. Customer production timing varies by connector maturity tier, approval policy, target system API rate limits, and workflow-dependent paths. Full methodology and raw measurements available on request as part of a Founding Partner engagement.
HR signal → revoke fans out across the systems scoped in the POC in seconds. Each target is labeled with Discover / Certify / Revoke maturity in the Evidence Pack — workflow-driven and partner-dependent paths are called out explicitly, not silently bundled. Closed loop, with cryptographic evidence of every revocation.
Bots, agents, service accounts, machine identities — discovered, owned, certified, rotated. AI-agent governance available in Private Beta for Founding Partners.
Risk-weighted reviewer routing, auto-revoke on no-response, full audit trail. The quarterly review that actually finishes on time.
Pre-built rule library for SOX, PCI, HIPAA. Catches conflicts at request time, not after the violation has been audited.
AWS · Azure · GCP. Right-size every IAM role. Detect shadow admin paths. Revoke unused permissions on schedule.
UEBA, ITDR, attack-path analysis. Anomalous access flagged in seconds. Auto-quarantine on high confidence.
Multi-AZ cloud control plane (recommended production architecture). Customer-managed data tier. Hybrid Connector Gateway dialing out over mTLS. Built for environments where the network team owns the firewall and the answer to "open a port" is always no.
Lightweight agent inside your VPC dials out over mTLS. No inbound firewall hole, ever. The network team's favorite vendor.
AWS KMS, Azure Key Vault, HashiCorp Vault, GCP KMS. You hold the keys. We never see plaintext PII.
Dual availability zones, private app pods, Postgres primary/replica, Redis HA. 99.95% uptime target.
Cryptographically signed audit log of every policy decision. Auditor-ready exports. NIST-aligned · HIPAA-mapped · FedRAMP-aligned.
Most vendor sites pretend they're a fit for every situation. We won't. Here's where STRATUS is the obvious choice — and where we genuinely think you'd be better served somewhere else.
Identity governance shouldn't require a 3-year transformation project to solve a 4-hour revocation gap.
After fifteen years inside identity programs at IBM and Oracle, I watched the same pattern repeat across forty-seven enterprises. A user leaves on Friday. The IGA platform is mid-deployment, mid-migration, mid-something. By the time the offboarding ticket fires, the access has been live for hours. The audit log shows what happened — but not in a way that survives a forensic challenge.
STRATUS is built around the part everybody else treats as an afterthought: the actual revoke, the actual evidence, the actual proof that the action was taken and can be verified by math. Hardened from day one. Outbound only. Designed to ship in weeks, not years.
If the four-hour gap sounds familiar — and you're tired of waiting on the long migration to close it — we should talk.
Paid 30-Day Proof of Revoke — credited toward year-one contract upon conversion. Closed-loop revoke working by Day 30 — or you walk.
Founding Partner Program · 2026 Selection Open · Sacramento, CA
Days 1–7 you connect. Days 8–14 we surface every ghost account. Days 15–21 we simulate. Day 30 we revoke. If we cannot show a working closed-loop revoke in 30 days, you do not move forward.