Skip to main content
A Plan defines what a tenant gets access to and how much they pay. Plans belong to a Product, which is a logical grouping (e.g., “Email Platform” or “Analytics Suite”).

Plan Fields

Features vs Limits

Features are boolean gates — a tenant either has access or doesn’t:
Limits are numeric caps on usage:

Seat-Based Plans

For B2B products where pricing scales with team size, plans can be seat-based: Pricing formula:
Example: Base 50/monthfor10seats,50/month for 10 seats, 5/seat after that.
  • 8 seats → $50
  • 15 seats → 50+(5×50 + (5 × 5) = $75

Test Mode

Plans have a test_mode flag. When true, Crovver routes checkout through test payment credentials (e.g., Stripe test keys). This lets you test the full checkout flow without real charges. Use test cards like 4242 4242 4242 4242 for Stripe test mode.
Never use a production plan for testing. Always create a separate test plan with test_mode: true.