GetPaidHQ vs Recurly.
Recurly is a hosted recurring-billing platform known for its revenue-recovery and dunning tooling. GetPaidHQ covers the same recurring-billing and recovery ground, but as open-source software you self-host on any processor — so the data and the deployment stay yours.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.
At a glance.
Both do recurring billing, usage, and dunning across multiple gateways. The difference is who hosts it, who can read the code, and how you pay.
| Capability | GetPaidHQ | Recurly |
|---|---|---|
| Hosting | Self-host, or managed Cloud | Fully hosted SaaS |
| Source code | Open-source (AGPLv3) | Proprietary |
| Where billing data lives | Your own infrastructure | Recurly's cloud |
| Pricing model | Free to self-host — you pay for infra | Subscription that scales with billed revenue |
| Payment processors | Any processor, via an adapter interface | Multiple supported gateways |
| Multi-processor routing | Per region, customer, or failover | Gateway routing within the platform |
| Recurring, usage-based & hybrid pricing | ||
| Built-in dunning & recovery | ||
| Vendor lock-in | Fork and run it forever | Tied to the platform |
Which one is right for you?
Recurly is the better choice when…
- You want a managed platform with mature, out-of-the-box revenue-recovery analytics.
- You prefer vendor-run infrastructure, support, and SLAs.
- You do not want to operate billing services yourself.
- A revenue-scaled subscription fits your budget.
GetPaidHQ fits better when…
- You want to self-host and keep billing and customer data inside your perimeter.
- You would rather pay for infrastructure than a percentage of billed revenue.
- You want to read and extend the dunning and billing logic directly.
- You need to route charges across your own processors, per region or for failover.
Moving from Recurly.
GetPaidHQ maps to the same primitives — accounts, subscriptions, plans, usage, and invoices — so your existing model translates. Bring customers and subscriptions over through the API, connect your processors behind the adapter interface, and run both in parallel for a cycle to reconcile recovery and invoicing before cutting over.
GetPaidHQ vs Recurly — FAQ.
- Is GetPaidHQ a Recurly alternative?
- Yes — it handles recurring, usage-based, and hybrid billing with dunning and invoicing. The difference is that GetPaidHQ is open-source and self-hosted rather than a managed SaaS.
- Does GetPaidHQ do dunning as well as Recurly?
- Dunning is built in — adaptive retries, pre-dunning, cross-processor retries, and payment-update links. Recurly has a longer track record of recovery analytics, so compare against your specific recovery needs.
- How does the cost compare?
- Recurly is a subscription that scales with billed revenue. GetPaidHQ is free to self-host under AGPLv3; you pay only for the infrastructure you run it on, or for managed Cloud.
- Can I keep my current gateways?
- Yes. Add the processors you already use behind GetPaidHQ’s adapter interface and route between them without changing application code.
Recurring billing you control.
Self-host GetPaidHQ for free today, or talk to us about managed Cloud.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.