Pricing

We don't publish
a price list.
Here's why
that's better.

A fixed plan would force your product into our structure. We do the opposite — we align our billing to yours.

The reasoning

Your billing model shouldn't have to bend around ours.

We have seven partners. Not seven thousand. That ratio is deliberate — it means we can afford to do something most API vendors cannot: adapt our pricing architecture to yours, rather than issuing a standard plan and calling it flexibility.

Our partners range from focused vertical products to platforms that are a hundred times our size. Each has its own customer pricing strategy, its own commercial architecture, its own growth model. A single published price plan would serve none of them well.

"The model we agree on is a direct consequence of how you've built your product — not a compromise you make to fit ours."

When you integrate AzoraOne, the billing conversation starts from your architecture: how you charge your customers, how you've structured your tiers, what your growth projections look like. We work backwards from there.

Three billing architectures

Proven models. You pick the one that maps to yours.

Pay per document
Usage-based

You pay per uploaded file. Costs move in direct proportion to your customers activity — making it easy to pass through or mark up transparently in your own pricing.

Fits well with: usage-based SaaS products, consumption billing, pay-as-you-go platforms, or any product where your customers bill by transaction volume.

Pay per customer
Seat-based

A flat rate per end-customer per month, regardless of how many documents that customer processes. Predictable, linear, and trivially mappable to your own seat or licence revenue.

Fits well with: per-seat SaaS pricing, module-based licencing, accountancy platforms billing by company or client, or any product where you charge a monthly fee per entity.

Volume tiers
Threshold-based

Agreed monthly or annual thresholds with declining effective rates as you scale. The more your customers use AzoraOne, the lower your cost per file — structurally rewarding growth without requiring renegotiation at every milestone.

Fits well with: high-volume pipelines, enterprise integrations, platforms with predictable annual growth, or any product where scale should translate directly into margin improvement.

What you should expect

0.50 0.10

Whatever billing model we agree on, most partners converge toward an effective rate between €0.05 and €0.10 per processed file. That's the number worth doing your back-of-envelope on.

The model varies. The value doesn't.

The conversation

Tell us how you
bill your customers.
We'll work backwards
from there.

No deck. No demo unless you want one. Just a conversation about your architecture and whether our model fits inside it.

We'll typically want to understand your customer pricing strategy, your expected API throughput and your end-customer volume — so the more context you can bring, the faster we can give you a meaningful number.
Start the conversation