Free to self-host. Managed when you're ready.
Run GetPaidHQ on your own infrastructure for free, or let us host it for you. Cloud pricing is being finalized — get in touch for early access.
Self-hosted
Run GetPaidHQ on your own infrastructure.
Free
Forever, on your infra
What's included:
- Fixed, usage-based, and hybrid pricing
- Built-in dunning and invoicing
- Processor-agnostic — bring your own gateway
- Multi-processor support per region or customer
- Community support
Cloud
Fully managed GetPaidHQ, hosted by us.
TBC
Pricing to be announced
What's included:
- Everything in Self-hosted, fully managed
- Hosting, scaling, and updates handled for you
- Priority support and SLA
- Onboarding assistance
- Custom adapter development on request
Frequently asked questions
FAQ.
- What is GetPaidHQ?
- GetPaidHQ is a self-hosted subscription billing platform. It supports fixed, usage-based, and hybrid pricing models, with built-in dunning and professional invoicing. Built for businesses on regional gateways, custom processors, or a mix — the processor-agnostic adapter interface lets you wire up any payment provider. Run it on your own infrastructure and keep your customer data under your control.
- Can I self-host GetPaidHQ?
- Yes — self-hosting is the default. Deploy GetPaidHQ on your own servers or cloud, wire it up to your payment processor of choice, and keep all customer and billing data within your perimeter. See the deployment docs for reference architectures and step-by-step setup.
- Who is GetPaidHQ for?
- GetPaidHQ is built for SaaS companies needing flexible subscription billing, API-first businesses with usage-based pricing, marketplaces with revenue sharing, membership and community products, and any team that wants billing infrastructure they can host and customize themselves.
- How does GetPaidHQ differ from hosted billing platforms?
- GetPaidHQ is processor-agnostic and self-hosted. You own the deployment, control the data, and pick the payment processor — instead of being locked into one vendor’s stack. It still gives you the same flexibility around fixed, usage-based, hybrid, tiered, and graduated pricing as the hosted players.
- Should I use GetPaidHQ if I’m on Stripe?
- Probably not — Stripe Billing already covers fixed, usage-based, and hybrid pricing for Stripe-only stacks, and it’ll be the path of least resistance. GetPaidHQ is built for the rest: businesses on regional gateways, custom or in-house processors, multi-processor stacks across regions, or with compliance requirements that keep customer and billing data within their own perimeter.
- What billing models does GetPaidHQ support?
- Fixed subscriptions (e.g. $29/month), usage-based pricing (per API call, GB, or any unit you track), percentage-based fees (e.g. 2.9% + $0.30), hybrid models combining all of the above, tiered pricing by volume, and graduated pricing that adjusts as usage grows.
- Can I combine different billing models?
- Yes. Hybrid billing is a first-class concept. Combine a fixed monthly base with metered usage and transaction percentages inside a single subscription — for example, $99/month base + $0.01 per API call + 2.9% transaction fees.
- How does usage-based billing work?
- GetPaidHQ captures billable events in real time through the Event Ingestion API, aggregates usage by billing period, and generates detailed invoices showing exactly what was consumed. Use it for per-unit pricing (API calls, storage, bandwidth) or percentage-based pricing (transaction fees, revenue shares).
- What payment processors does GetPaidHQ support?
- GetPaidHQ is processor-agnostic. The integration layer is designed so you can wire up any payment processor — regional gateways, custom processors, or your own in-house payment stack. Once you have adapters configured for the processors you need, you can switch per region or per customer without changing your application code.
- How do I integrate GetPaidHQ into my application?
- GetPaidHQ exposes a RESTful API for customer and subscription management, billing and payments, usage recording, webhook events, and admin operations. The API is documented with OpenAPI, with official SDKs for Node.js, Python, PHP, and Go.
- How does dunning management work?
- Built-in dunning includes automated retry logic for failed payments, configurable campaigns with multiple retry attempts, customer notifications via email and SMS, payment-method update links for expired cards, and detailed reporting on recovery success rates.
- How does invoice generation work?
- GetPaidHQ generates detailed, transparent invoices with usage breakdowns showing exactly what was consumed, fixed charges and variable usage fees clearly separated, PDF generation with customizable templates, automatic tax calculations where configured, and multi-currency support.
- Can customers see their usage in real time?
- Yes. Customer-facing usage dashboards let your users track current usage against limits, view historical consumption patterns, receive alerts when approaching limits, make informed upgrade decisions, and download usage reports.
- What reporting and analytics are available?
- Real-time usage dashboards, revenue analytics and projections, customer cohort analysis, payment success and failure tracking, detailed invoice breakdowns, and export capabilities for external BI tooling.
- What support is available?
- Detailed API documentation with examples, developer guides and tutorials, community support, priority support for paid plans, and professional services for enterprise self-hosted deployments.