🔍⌘K

Start typing to search docs.

Operations Overview

1.0.0

How we observe, operate, and keep the platform healthy.

On this page
  1. Platform operations
  2. Observability
  3. Weekly checklist
  4. Escalations

Platform operations

  • Runbooks cover deployments, troubleshooting, and cost management. They match the docs/runbooks markdown files imported into this hub.
  • Infrastructure uses Pulumi programs (infra/pulumi-*) to spin up dedicated stacks when customers graduate from the shared Supabase project.
  • Security requirements live in Security & Compliance and include gitleaks, SBOMs, and vulnerability scans.

Observability

  • Leverage @vercel/analytics events (docs, paywall, pricing) for customer insights.
  • Use Supabase monitoring dashboards for database performance.
  • Track semantic-release output via the changelog page.

Weekly checklist

Info

Treat this as the baseline SRE ritual. Automate where possible, but keep human eyes on the system weekly.

  1. Review last release in the changelog.
  2. Check Pulumi stack drift (run pnpm infra:drift scripts if present).
  3. Validate Stripe webhooks using stripe listen locally or observability in production.
  4. Run pnpm run security:* to refresh SBOM + vulnerability scans.
  5. Update docs if you touched architecture or provisioning flows.

Escalations

  • For production incidents, start with the Troubleshooting runbook.
  • Use #ops-alerts (internal) for paging on-call.
  • File updates back into the docs hub once the incident is resolved.