Driptab
Usage-based billing on a single Cloudflare stack. Record events, generate invoices,
collect payments — without running a database.
What Driptab does
Driptab is a developer-first billing platform. Your backend reports usage events
(emails sent, API calls made, GB stored). At the end of each billing period, Driptab
aggregates those events into line items, generates an invoice, and fires a webhook.
You decide how to collect payment.
Driptab also handles flat-fee billing: domain registration, VPS instances, and any
other fixed-price product. The same platform handles both models.
Concepts
|
|
| Billing model |
Plans, charges, metrics, catalog, add-ons |
| Subscriptions |
Subscription lifecycle, statuses, billing periods |
| Invoices |
Invoice lifecycle, timing models, payment status |
| Events and metering |
Usage event ingestion, aggregation, Durable Object architecture |
| Audit trail |
billing_events, audit_logs, actor tracking |
| Webhooks |
Event notifications, HMAC signing, dunning pattern |
| driptab.yaml |
GitOps sync, driptab.yaml format, dtab sync |
Guides
|
|
| Getting started |
Install CLI, create first plan, subscribe a customer, ingest usage |
| Domain hosting (HostCo) |
TLD catalog, domain register/renew plans, transfer add-ons |
| SaaS metering (EmailFS) |
Billable metrics, usage-based plans, event ingestion, period close |
| MCP integration |
HTTP MCP server, Claude Desktop setup, available tools |
| AI agents |
Crux driptab-operator agent, CLI/API/ops skills |
Reference
Pricing
|
|
| Pricing |
Hosted and self-hosted package limits |
Key facts
- Single deployment: Cloudflare Workers + D1 + Durable Objects + KV + R2. No
separate database.
- Multi-tenant: org → workspace → project hierarchy. All billing data is
project-scoped.
- Idempotent by design: every event ingestion, every mutation is safe to retry.
- Agent-first: the API is designed to be driven by AI agents over MCP.
- Open-source ready: the platform is self-deployable via Wrangler.