⚠ Alert: Unauthorized SaaS Spending Detected

TERMINATE
ROGUE IDENTITIES

Scan. Isolate. Purge. The automated protocol for neutralizing zombie SaaS accounts before they drain your budget.

> initializing_scan...

> connecting_to_provider: Okta... ESTABLISHED

> connecting_to_app: Salesforce... ESTABLISHED

> analyzing_usage_logs...

> WARNING: 42 inactive accounts detected.

> estimated_waste: $6,300/mo

> awaiting_command_

🔎

Target Acquisition

We cross-reference your Source of Truth against actual SaaS user lists. Discrepancies are flagged immediately.

☣️

Threat Analysis

Our "Zombie Query" engine identifies suspended identities that are still active billing entities in downstream apps.

🛡️

Perimeter Defense

AES-GCM encryption for credentials. Strict tenant isolation. Self-hosted authentication infrastructure.

Operational Directives

The average organization wastes 30% of their SaaS budget on "Zombie" licenses—accounts assigned to users who no longer exist or haven't logged in for months.

We provide the visibility to stop the bleeding. Connect your apps, monitor usage, and reclaim your budget.

  • >> Establish Connection: Link Directory & Apps (Okta, Google, Salesforce)
  • >> Scan for Anomalies: Correlate identity data with activity logs
  • >> Isolate Zombies: Flag terminated users holding expensive seats
  • >> Reclaim Resources: Deprovision and reduce burn rate

Read the integration setup guides →

Detection_Log
// waste_analysis_report.json

{

"target": "user_492_x",

"status": "TERMINATED",

"app": "Salesforce_CRM",

"last_login": "180_days_ago",

"cost_leak": "$1,800/yr",

"recommendation": "IMMEDIATE_PURGE"

}

Production updates

Release notes

Version history and changes shipped to production.

v0.1.44

  • Added a Jira setup guide and fixed the Jira connection, which previously requested a permission Atlassian does not offer and could not complete authorization.
  • Usage reporting can now show vendor-reported spend per person where the provider offers it; the credentials list shows whether a key's owner still has access.
  • Added OpenAI as a usage integration: connect an OpenAI organization with an Admin API key to see token usage and cost per person, and which API keys are spending.
  • The usage page now shows the person who owns each API key, instead of just "User".
  • A key that was created recently is no longer reported as dormant before anyone has had a chance to use it.
  • The usage page no longer lists an empty "Unattributed" entry that looked like an inactive user.
  • Service accounts and keys without a linked member are no longer described as having "no usage in the last 90 days".

v0.1.43

  • Added versioned production release notes to the home page, including expandable release history.