Skip to content

Chargebee

The second revenue source Tidemill ingests — and the reason the canonical vocabulary exists.

What it is

A proprietary subscription billing and revenue management platform, widely supported as a data source across the analytics category — ChartMogul, Baremetrics, ProfitWell and SaaSGrid all connect to it. Its data model differs from Stripe's in vocabulary more than in shape: item prices, period units, and its own subscription and invoice state machines.

Key facts
Category Billing layer (managed)
Licence Proprietary SaaS
Deployment Cloud only
Data access API + webhooks
Tidemill integration WebhookConnector, registered as chargebee
Status Implemented and enabled in production

Relevance to Tidemill

Chargebee is implemented today (tidemill/connectors/chargebee/) as a WebhookConnector, making it Tidemill's second live revenue source alongside Stripe.

Its real significance is architectural. Supporting a second billing vocabulary is what forced Tidemill's canonical vocabulary to become explicit — the provider-agnostic enums that every connector maps onto:

Canonical concept Stripe Chargebee
Plan interval recurring.interval item_price.period_unit
Pricing model billing_scheme / recurring.usage_type item_price.pricing_model
Subscription status status Subscription.status
Invoice status status Invoice.status

Edge cases like Chargebee's non_renewing — active for the current period but not renewing — are exactly what the canonical pending cancellation flag was introduced to represent without losing information.

Running two sources concurrently is also why source exists as a dimension on every subscription cube, so metrics can be grouped or filtered by connector. See cubes and reports.

Documentation gap

connectors.md documents Stripe, Lago, Kill Bill and QuickBooks, but has no Chargebee section despite the connector being implemented and enabled in production. Recorded in the wiki log on 2026-07-23.

Sources