Your product is ready. Billing is holding it back.
The closer you get to launch, the same problems show up: subscriptions, usage, entitlements, invoicing, payments. Build it all yourself — or adapt a billing stack that wasn't built for your market?
Build it yourself
Months of engineering spent on billing instead of your product. Then come the maintenance, pricing changes, edge cases, and infrastructure you now own.
Use a platform built for another market
You skip part of the build, then build what's missing: mada, Arabic, local requirements, and the entitlement logic inside your product.
Start billing in minutes. Evolve it with your product.
Subscriptions, usage metering, entitlements, feature flags, and credits are already there. Configure your billing model from the dashboard and connect Tirdad to your product — instead of building the billing lifecycle yourself.
Your product's tiers — assembled from the same parts.
These are example plans, built with Tirdad. Looking for our pricing? See Tirdad pricing
Start with a blank canvas.
Every Tirdad plan is assembled from primitives — no billing code, no migrations. Step through to watch an example customer's plan 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.
That's your pricing — live in minutes.
A complete plan — pricing, entitlements, and billing in a single object. Clone it, change a limit, flip a flag, and you've shaped your next tier.
These are example plans, built with Tirdad. Looking for our pricing? See Tirdad pricing
From first event to final invoice. Automatically.
From first event to final invoice. Automatically.
Your customer uses your product. Tirdad takes it from there — metering usage, watching limits, pricing overages, applying credits and discounts, and building the invoice.
They use it. Tirdad knows.
An API call, a token, a message, a gigabyte — send the event through the SDK or API and Tirdad receives it in real time.
Every unit is counted as it happens.
Each event hits the meter attached to the customer's plan immediately. No pre-aggregation. No nightly batch. No waiting.
Near the limit? Know before they cross it.
As usage approaches a threshold, Tirdad triggers the alert automatically — for your team, your customer, or both.
Over the limit? You decide what happens.
Let usage continue and price the overage automatically, or enforce a hard cap and stop it. Set the behavior per plan.
Have a balance? Use it first.
Prepaid credits, top-ups, and grants are consumed automatically before anything reaches the invoice.
Have a discount? Already applied.
Percentage or fixed, temporary promo or coupon — Tirdad applies it automatically according to the rules you set.
And at the end? The invoice is ready.
Subscription, overage, discounts, credits, and VAT come together in one SAR invoice, ready to collect.
Built for the Saudi market from day one.
Tirdad was built from day one for companies selling software in Saudi Arabia — from SAR and Arabic to local payments and e-invoicing.
No workarounds. No local layer left for your team to build.
SAR isn't just another currency in a dropdown.
Pricing, subscriptions, usage, credits, and invoices treat SAR as a first-class part of the billing lifecycle.
Arabic is part of the product. Not a translated interface.
Arabic and English invoices and customer experiences without building an Arabic layer over a product designed around English.
The ways your customers actually pay here.
Connect the payment methods and gateways that matter in Saudi Arabia without changing the billing system behind them.
Built around Saudi invoicing requirements.
Tax, invoicing, and local integration requirements are part of the billing lifecycle — not another project you bolt on later.
And when your data needs to stay in the Kingdom, you have the choice.
Run Tirdad in a model that fits your residency and governance requirements — managed or inside your own infrastructure.
Local doesn't mean limited.
Subscriptions, usage, credits, entitlements, and hybrid pricing — the billing models modern SaaS and AI products need, built for the market you're selling in.
Build for Saudi Arabia without adapting your billing to it. Tirdad started here.
You can build it. The question is: why would you?
Billing isn't an invoice and a payment. Behind it are metering, entitlements, pricing, tax, retries, reconciliation, and all the infrastructure that keeps them working as your product grows. You can build all of that. Or you can build your product.
Your engineering time
Build in-houseYour best engineers build billing infrastructure instead of the features that make your product different.
With TirdadIntegrate once. Then manage your billing model through Tirdad.
Time to launch
Build in-houseBefore the first invoice: events, metering, pricing, entitlements, payments, and invoicing.
With TirdadConnect your product. Build your plan. Start billing.
What's underneath
Build in-houseEvent infrastructure, metering, storage, processing, retries, observability — and an operational burden that doesn't go away.
With TirdadThe infrastructure is already there and fully managed — or deploy it inside your own infrastructure.
What shows up after launch
Build in-houseA mid-cycle upgrade. Failed payment. Overage. Discount. Credit. Refund. Rounding edge case. Every new case becomes more code you own.
With TirdadThey're not edge cases. They're billing primitives — and they're already built.
When pricing changes
Build in-houseTicket. Build. Test. Deploy.
With TirdadEdit. Review. Publish.
When something goes wrong
Build in-houseA small metering or pricing bug can mean revenue you never collect — or a customer you charge too much.
With TirdadEverything from usage event to invoice line is traceable and auditable.
Build what makes your product different. Let Tirdad handle the billing.
Start freeChange pricing without rebuilding billing.
A new price, a new plan, a usage limit, or an entirely different pricing model shouldn't mean another ticket, another build, and another release. With Tirdad, change the model from the dashboard. Your product follows.
$99 becomes $149? Change it.
No code change. No deployment. Update the price and decide when it takes effect.
You don't have to monetize the same way forever.
Fixed today. Usage-based tomorrow. Or both. Change how you charge without rebuilding billing.
A plan is more than a price.
Add a feature, move a limit, grant more credits, or change an entitlement — and your product gets the new plan definition.
New pricing idea? Try it.
Configure the plan, set its price and entitlements, review it, and publish — without turning the idea into an engineering project.
Change the future without breaking the past.
Launch new pricing for new customers while keeping existing customers on their current terms when you need to.
Security starts inside the billing lifecycle.
Tirdad sits in a sensitive part of your stack: customers, usage, entitlements, and invoices.
That's why security isn't a layer added afterward. It's part of how Tirdad is built and operated from the start.
Card data doesn't need to pass through Tirdad.
Keep sensitive payment details with your payment provider. Tirdad works with payment state and the billing lifecycle without becoming another place that stores card data.
Every tenant stays within its boundary.
Tirdad is built for multi-tenancy with customer data and accounts isolated between organizations.
Need more control? Run it yourself.
Deploy Tirdad inside your environment and behind your own network and access controls when your policies require it.
Security shouldn't be a promise. It should be visible in how the system is built.
Start with the decision in front of you.
Work through pricing as a sequence: define what customers buy, understand what it costs, then connect usage to the invoice.
Price a product feature
Turn a customer outcome into a feature, entitlement, allowance, and price.
02Calculate what it costs
Build a cost model before margin disappears inside a popular feature.
03Connect usage to billing
Decide what your product owns, what Tirdad owns, and how one event becomes an invoice line.
You're probably wondering a few things.
If you've made it this far, you probably have a few questions before deciding whether Tirdad fits your product. These are the important ones.
Build your first plan in minutes.
Model any pricing on a free account — no sales call required.