Offboarding that survives the audit.
AccessExit turns every departure into a tracked offboarding checklist with owners, SLAs, and evidence, then closes it with an audit-ready receipt.
Free / $29 Starter / $49 Team. MVP in beta — paid plans activated manually, no credit card.
The problem
When someone leaves a small team, their access rarely leaves with them, and the offboarding is a Slack message and a stale checklist. Months later an auditor, client, or insurer asks you to prove it, and nothing is on file.
The approach
AccessExit turns each departure into a tracked case with owners, due dates, and captured evidence across the SaaS long tail SSO doesn't reach, then produces a timestamped receipt that never claims access was removed unless it was verified or a named person accepted the risk.
What's inside
Deterministic offboarding checklists
People directory & app inventory
Access map with coverage gaps
Criticality-aware deprovisioning SLAs
Evidence log per task
Immutable, shareable receipts
Quarterly access reviews & attestations
Google Workspace directory sync
02From the lab
The decisions, trade-offs, and engineering notes behind AccessExit — written as we build.
SSO and SCIM deprovisioning are gated to enterprise tiers, so small teams pay the "SSO tax" in manual labor and unprovable offboarding instead. Here's the honest arithmetic — and the pragmatic way out.
AccessExit generates offboarding checklists with rules, not a model — not because AI is bad, but because the output is an audit artifact, and three places in the code exist purely to stop the product claiming more than it can prove.
More from Eastbase
