Public Status

ShakerScan service status.

Public summary for the hosted app, AI Gate control plane, worker callback path, billing, and CI verification workflows. Billing is currently deployed with Stripe test keys, and GitHub required-check enforcement should be validated per repository during beta onboarding.

Overall Status

Beta services operational

3 of 5 listed services are fully operational; 2 are beta operational.Public incident history is maintained here; detailed internal worker, scheduler, and webhook health remains admin-only.

Web app and dashboard

operational
Customer Impact

Signup, billing, onboarding, target setup, evidence review, and approvals.

Verification

Public app availability plus internal admin health checks.

AI Gate control plane

operational
Customer Impact

AI target management, scan dispatch, policy decisions, evidence, and attestations.

Verification

API readiness, callback persistence, and evidence creation checks.

Worker callbacks and artifacts

operational
Customer Impact

Scan execution, transcript upload, callback persistence, and reconciled status.

Verification

Worker health, callback logs, artifact availability, and scan lifecycle state.

Billing and checkout

beta operational
Customer Impact

Checkout surfaces, plan changes, customer portal, quotas, and subscription webhooks are deployed for beta validation.

Verification

The deployment currently uses Stripe test keys. Code readiness and non-mutating checks are present, but live Stripe products, real-card checkout, portal changes, and webhook delivery require authorized production validation before paid launch.

GitHub and CI verification

beta operational
Customer Impact

GitHub App gates, fallback GitHub Action setup, attestation verification, and approval-token workflows.

Verification

GitHub App and Branch Rules flows are available for beta use and have live-path coverage, but customer-org branch protection, permissions, and required-check enforcement should be validated per repository before relying on merge blocking.

Incident Handling

Customer-impacting incidents should be posted here.

Incident notes should include affected services, customer impact, current state, mitigation, and follow-up. For urgent security reports, use the responsible disclosure path instead of this status page.

Last updated: May 1, 2026