Any subscription plan,
any pricing, any payment.
Subscriptions, metered usage, feature flags, entitlements and credits — collected through mada, Apple Pay and cards.
- No code
- reprice from the dashboard
- 12 systems
- metering · dunning · tax
- Any event
- API calls · tokens · GB
- Bilingual
- Arabic and English
Your product is ready to charge. Your billing isn't.
Every SaaS, AI, and fintech company reaches the same fork — and both roads cost you a year.
Build it yourself
Billing looks like a feature until you start. Then it turns into a system, and the system is never finished.
- 1–3metering and events
- 3–6pricing models
- 6–9proration, dunning, tax
- and it never ends — every price change is another sprint
Force-fit a global tool
It will bill. But usage arrives late, entitlements stay your problem, and nothing about it was built for this market.
- Usage isn't live
- you pre-aggregate and send batches — minutes behind, so no live balance and no way to stop a runaway account
- Entitlements aren't included
- it bills the plan, but your product still has to decide what each customer may do
- Local integrations
- the accounting and point-of-sale tools you already run aren't on their integration list
- Support
- email tickets in another timezone — not Arabic, not your business hours
Build it from parts, not from scratch.
Subscriptions, metering, feature flags, entitlements and credits already exist. You compose them — and everything both roads above cost you comes with it.
Multiple plans. Same parts.
Start with a blank canvas.
Every Tirdad plan is assembled from primitives — no billing code, no migrations. Scroll to watch one take shape, line by line.
A base subscription.
Begin with a recurring price — the predictable floor of the plan. Bill it monthly or annually, always in SAR, with trials when you need them.
A metered feature.
Attach a meter to bill real usage. Every event — an API call, a token, a gigabyte — is counted and aggregated in real time. You decide what to measure and how to add it up.
An entitlement.
Set what's included, and what happens past it. A hard cap blocks overuse; a soft limit lets it through and bills the overage. Limits reset on the period you choose.
A feature flag.
Gate access with a boolean flag — SSO, priority support, an advanced module. It lives in the same entitlement system, checked in real time. Feature flags and billing, one source of truth.
Prepaid credits.
Add a wallet for pay-as-you-go balances — top-ups, promotional grants, and expiry rules. Usage draws the balance down before it ever reaches an invoice.
One plan. Then many.
That's a complete plan — pricing, entitlements, and billing in a single object. Clone it, change a limit, flip a flag, and you've shaped the next tier.
From event to invoice — automatically.
Your product sends usage.
Every action — an API call, a token, a delivery — streams to Tirdad in real time, over an SDK or a single API call.
Tirdad meters it, live.
Events are counted and aggregated against the plan's meter the instant they land — no nightly batch, no lag.
Warned before the cap.
As usage nears the entitlement, threshold alerts fire — to you and to your customer — so a surprise bill never happens.
Past the limit, it keeps working.
The soft limit lets usage through and prices the overage automatically. A hard cap would block instead — your call, per plan.
Prepaid balance covers it first.
Usage draws the customer's wallet down before anything reaches an invoice — top-ups and grants included.
Discounts apply on their own.
Attach a coupon or promo and it comes off the invoice automatically — percentage or fixed, stacking or exclusive, with usage limits and an expiry.
The invoice writes itself.
Subscription, overage, discounts, credits, and VAT settle into one invoice — in SAR, collected through mada and Moyasar. Zero manual work.
Every part you just watched, explained.
Usage events, explained
What a usage event is, what a well-designed one contains, and how one tiny record powers metering, credits, limits, and invoices — a plain-language guide.
Credits, explained
What prepaid credits are, why AI products bill this way, how wallets, top-ups, and expiry work, and what it changes for cash flow — a plain-language guide.
Grace periods, explained
What a grace period is, how long it should be, what access customers keep during it, and why the policy matters more than the length — a plain-language guide.
The cost of building it yourself.
Metered billing looks like a feature you can add. It's a system that keeps a team busy long after launch — here's the real cost, side by side.
Time to first invoice
Build in-house6–12 months of engineering before you can charge a customer
With TirdadLive in days — integrate and start billing
What it costs to get there
Build in-house2–4 senior engineers for months — SAR 1M+ in salary before the first invoice
With TirdadFree to start, then pay as you grow
Who builds it
Build in-houseYour best backend engineers — pulled off the product only you can build
With TirdadA configuration your PM or finance lead owns
The systems underneath
Build in-houseKafka, ClickHouse, Postgres, Redis, Temporal — and 24/7 on-call
With TirdadFully managed, or the same Helm charts on your own infra
The part nobody scopes
Build in-houseProration, dunning, tax, refunds, disputes, edge cases — maintained forever
With TirdadBuilt in and kept current for you
When billing gets it wrong
Build in-houseA metering bug under-bills; a proration bug over-refunds — revenue lost silently
With TirdadExactly-once counting, reconciled and audited
Illustrative — costs vary by team; salary figures assume senior backend engineers in the Kingdom.
Everything billing needs. None of it your problem.
The unglamorous half of billing — the part that quietly eats a year of engineering. Tirdad ships all of it.
Metering & aggregation
Count any event in real time — exactly once.
Proration
Fair math on every upgrade, downgrade, and mid-cycle change.
Dunning & retries
Failed payments chased and recovered automatically.
Tax & VAT
SAR invoices with 15% VAT, calculated for you.
Invoicing & PDFs
Itemized invoices generated every cycle.
Entitlement checks
Gate features in real time — access and usage in one call.
Credits & wallets
Prepaid balances, top-ups, and grants, with a full ledger.
Coupons & discounts
Stackable discounts with redemption tracking.
Webhooks
Every billing event, synced to your systems.
Idempotency
Retries and duplicate sends never double-charge.
Trials & grace periods
Onboarding and lapses handled by policy.
Reconciliation
An auditable trail from raw event to invoice line.
Reprice on Friday. Live by lunch.
The pricing changes your competitors ship in a sprint, you make from the dashboard — raise a price, add a tier, launch a promo, flip a feature. Live in seconds, no deploy, no engineering ticket.
- Raise or cut a price
- Add a tier or an annual plan
- Launch a limited-time promo
- Adjust a usage cap or allowance
- Grandfather your existing customers
Yours to run, yours to leave.
No revenue share, no proprietary lock-in. Every dependency is open source and swappable, and a dedicated deployment is the same architecture as our cloud — not a fork.
Cloud or on-prem
only on TirdadRun on Tirdad's cloud, or deploy the same Helm charts inside your own infrastructure. Billing data can stay entirely within your walls.
Swap any provider
Your payment gateway, accounting system, and CRM are integrations, not dependencies — swap mada for another gateway, or change your books, without touching billing.
Your data, portable
Open webhooks stream every billing event to your systems, and a full export means you're never held hostage by the platform.
What the region needs, covered.
Our customers steer what we build. They asked, we shipped — and the next line in this ledger is yours.
01“Let our customers pay with mada and Apple Pay.”
mada · Apple Pay — collected through Moyasar
02“Invoices in riyals, with our VAT.”
SAR-native pricing · 15% VAT on every invoice
03“Our finance team works in Arabic.”
Arabic invoices, dashboard and support
04“Sync to the books we already use.”
Zoho Books · QuickBooks, synced automatically
05“Our data can’t leave our infrastructure.”
On-prem — the same platform, inside your walls
06Your ask goes here — regional requests move to the front of the roadmap.
Built for event-scale workloads.
A streaming pipeline, not a request queue — engineered for the high write volumes of AI and usage data.
Exactly-once counting on a durable event log — nothing billable is ever lost.
Enterprise-grade, and certified.
The controls a finance or security team will ask about — in place from day one.
SOC 2 Type II
Independently audited security controls.
PDPL
Aligned with Saudi Arabia's Personal Data Protection Law.
Data residency
Region-isolated — data is processed and stored only in its region.
Tenant isolation
Strict per-tenant separation with full, immutable audit trails.
Built for what the others weren't.
Global tools meter usage but weren't built for Saudi Arabia. Regional tools are built for Saudi but not for usage. Here's the honest breakdown — where each is strong, and where Tirdad is the only one that covers both.
Stripe Billing
Global · usage + subscriptionsStrongDeep metering and a huge developer ecosystem — the global default.
GapTakes a % of everything you bill, ties you to Stripe's own payments, and offers no SAR, mada, or Arabic.
Chargebee
Global · subscriptionsStrongMature subscription and revenue-ops tooling for global SaaS.
GapUsage metering is bolted on, pricing scales with your revenue, and it wasn't built for Saudi rails or VAT.
Stream
GCC · billing + paymentsStrongSaudi-built, with local payment rails and invoicing.
GapSubscriptions- and payments-first — no real usage or AI metering, cloud-only, and a payments take-rate.
Subsbase
MENA · subscriptionsStrongSubscription-lifecycle management across MENA with local support.
GapBuilt for recurring plans, not usage — no API or AI-token metering, and no on-prem option.
Comparison reflects publicly available information, July 2026.
The things buyers ask.
Draw your plans in minutes, not quarters.
Model any pricing on a free account — no sales call required.