Open betaNow open source on GitHub

Open-source subscription billing for any payment processor.

Self-hostable subscription billing that plugs into any gateway — fixed, usage-based, and hybrid pricing, no vendor lock-in.

Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.

Fixed, usage-based, tiered, and hybrid pricing — in one subscription.

Model whatever your product charges for. Combine recurring plans, metered usage, and one-off charges on a single subscription — then collect through your own payment gateway.

API-first, and built to be read.

A REST API, typed SDKs for Node, Python, PHP, and Go, reliable webhooks, and idempotency keys. It's open-source, so the implementation is never a black box.

billing.tsts
import { GetPaidHQ } from "@getpaidhq/node"

const gphq = new GetPaidHQ({ apiKey: process.env.GPHQ_API_KEY })

// Create a subscription on any configured processor
const subscription = await gphq.subscriptions.create({
  customer: "cus_123",
  items: [{ price: "price_pro_monthly" }],
  processor: "checkout",            // or "paystack", or your own adapter
})

// Record metered usage as it happens
await gphq.usage.record({
  subscriptionItem: "si_456",
  quantity: 100,
})

Your billing stack, on your infrastructure.

GetPaidHQ is AGPLv3 open-source. Run it on your own servers, keep customer and payment data inside your perimeter, audit every line, and avoid vendor lock-in. Free to self-host, forever.

How self-hosting works

Data residency
Payment and customer data never leaves your perimeter.
No lock-in
Source-available billing you can fork, audit, and own.
Modern stack
Go, PostgreSQL, Temporal, and NATS — real infrastructure.
Free forever
Self-host at no cost; managed Cloud is coming.

Common questions

Can I really self-host it?
Yes. GetPaidHQ is AGPLv3 open-source — clone the repo, run it on your own infrastructure, and it's free forever. A managed Cloud option is coming for teams who'd rather not operate it.
Which payment processors are supported?
Checkout.com and Paystack are supported today, and any processor can be added through the adapter interface. You route charges per region, per customer, or for failover.
Is this a Stripe Billing alternative?
It's for teams Stripe Billing doesn't fit — regional gateways, in-house or multi-processor stacks, and data-residency or ownership requirements. You bring the processor; GetPaidHQ runs the billing.
What billing models does it support?
Fixed, usage-based, tiered, and hybrid pricing — combined in a single subscription — with metering, invoicing, and built-in dunning.

Start self-hosting today.

Free and open source. Clone the repo and run it, or talk to us about managed Cloud.

Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.