- Add organization billing based on active private-repository pull-request authors, with separate hosted and BYOK prices. Keep hosted model-provider costs inside the plan price rather than exposing inference metering.
- Count the same GitHub identity separately for unrelated customer organizations and once across organizations consolidated under one enterprise account.
- Add billing-manager roles, invoices, and usage alerts.
- Connect customer-actionable service disruption and recovery, account security, installation suspension, and subscription recovery or cancellation events to the organization notification inbox without exposing operator incidents.
- Run the hosted service on a free-tier-compatible PostgreSQL profile: low per-process DB pools, single-job webhook queue drains, one low-frequency worker fallback, and explicit provider docs.
- Stand up PostHog dashboards for traffic sources, docs/blog paths, install funnel events, and bot/automation breakdowns.
- Activate scrubbed PostHog Error Tracking and sampled OTLP Logs only with zero-dollar billing caps, project and issue rate limits, alert destinations, and log drop rules configured.
- Keep Prometheus metrics focused on operational health: database reachability, queue depth, stuck jobs, bounded review incidents, token usage, and webhook volume.
- Rehearse worker termination during a sandbox review and assert that every owned GitHub check reaches a terminal state within a bounded window.
- Generalize GitHub identities into provider-linked identities, then add OIDC or SAML sign-in, verified domains, SCIM provisioning, enterprise account grouping, consolidated invoicing, and tenant audit logs. Product pages do not claim these capabilities until their end-to-end controls exist.
- Add a first-class queue wake mechanism if hosted traffic grows beyond the low-idle profile.
- Evaluate a non-Postgres queue only if the product needs an edge-native database/runtime migration.
- Add privacy-preserving conversion events for GitHub App install, OAuth login, org settings save, and first completed review.
- Export analytics and metrics into a long-retention warehouse only after the PostHog dashboards prove which views are worth preserving.
- Add team-scoped and mandatory configuration layers only with explicit conflict, provenance, and policy-lock semantics.