Deployment
Pricing
How Saifuro is priced and what drives the number.
Two components: a platform subscription and a usage based fee on metered transaction volume. Exact numbers depend on volume, the number of policy classes, and deployment shape, and come out of the first technical call.
What drives the number
| Driver | Effect |
|---|---|
| Metered volume | The usage component scales with evaluated requests, not with money moved |
| Policy classes | More distinct rule sets means more configuration and more support |
| Providers | Each additional payment provider adds an adapter |
| Deployment shape | Isolation requirements affect the subscription |
What we do not charge for
We take no float, earn nothing on custody, and hold no stake in interchange. Revenue grows when customers scale agent spending safely, not when transaction volume goes up for its own sake.
Observe mode is part of the evaluation, not a separate product.
Getting a quote
[email protected]. Useful to include: rough monthly agent spend, number of agents, and which payment providers you already use.