Starter
Evaluate the API, examples, and fit before buying a commercial license.
$0 evaluation
- Local package evaluation
- Core calendar views
- Docs and examples
- Email access request
Pricing
Pay when the scheduler is becoming product infrastructure.
Start with evaluation. Upgrade when a customer-facing or internal product needs production scheduling UI, customization, support, and commercial use.
Current access status
Bravo Calendar is in private early access. Stripe Checkout is implemented for Pro and Team when environment keys are present; without keys, the buttons explain the early-access path instead of taking payment.
- Clerk sign-in is wired as optional locally and required before real checkout once keys are configured.
- Paid fulfillment uses server-side entitlement records when DATABASE_URL is configured; package invitations remain founder-led for early customers.
- Customer-facing install examples use @bravocalendar/react; live demos keep the local package dependency until registry distribution is finalized.
Pro
For one production app that needs polished scheduling UI without bespoke calendar engineering.
$495 early-access license
- One production project
- Resource and timeline views
- Event editor workflows
- 1 year updates
- 30 days implementation help
Team
For teams building multiple scheduling-heavy products or internal tools.
$1,995 early-access license
- Multiple internal products
- Private implementation review
- 1 year updates
- Roadmap influence
- Migration planning support
License clarity before checkout.
Pricing is early, but the buying rules should still be legible before money changes hands.
| Scope | Starter | Pro | Team |
|---|---|---|---|
| Commercial SaaS use | Evaluation only | 1 named project | Multiple internal products |
| Updates | Current preview | 1 year | 1 year |
| Support | Best effort | 30 days implementation help | Private implementation review |
| Source package access | Local evaluation | Private package access | Private package access |
| Refund posture | Not applicable | Case-by-case during early access | Case-by-case during early access |
| Resale / white label | No | Custom approval | Custom license |
Can I evaluate before paying?
Yes. Early buyers should validate the API, customization model, and fit against their scheduling workflow first.
What happens if checkout is not open?
Email hello@bravocalendar.com or use the request-access form below. The Stripe route requires Clerk, Stripe prices, and DATABASE_URL before it will accept money.
Is account access automated after payment?
The code path is ready: Clerk identity, Stripe metadata, webhook persistence, and entitlement checks. Package access can still remain manually fulfilled for the first pilots.
What counts as a project?
A named product or internal app. SaaS resale and white-label terms should move into a custom license once demand is proven.
Not ready to buy yet?
Send the scheduling workflow you are building. Early access can be handled manually while Stripe, Clerk, and package distribution are finalized.