beta active

Billing & usage

Paid beta access is wired through one Stripe subscription plan. No coupons, taxes, or invoice labyrinth yet. Civilization survives.

Server readiness

Provider readiness

All provider env is present. Real provider work can be wired next.

Ready

Supabase auth + database

Ready for auth and database wiring.

Public auth keys and backend database/Supabase secret credentials are present.

Next: Wire the real auth and persistence flows when provider work starts.

Stripe billing

Ready for checkout and webhook wiring.

Publishable key, secret key, webhook secret, and paid beta price id are present.

Next: Run a test-mode checkout and webhook smoke before exposing the paid beta gate.

AI generation

OpenAI generation is configured with fallback safety.

Provider failures can fall back to deterministic demo output.

Next: Run targeted generation checks before exposing real generation to beta users.

StatusPayment required
PlanPaid beta
CheckoutReady
VariantsIncluded

Paid beta access

Klarava is paid from the beginning. Start the beta subscription to unlock the workspace, strategy calendar, canonical drafts, and platform-specific copy export.

Log in to start checkout

V1 billing rules

  • One paid beta subscription plan gates app access.
  • Access is granted when any synced Stripe subscription is active or trialing.
  • Past-due, unpaid, incomplete, and canceled states stay out of the app until Stripe confirms recovery.
  • Meter canonical content pieces, not tokens.
  • Platform variants are included after canonical approval within plan limits.
  • No unlimited AI content. That way lies margin pain and weird user behavior.