Free
$0/month
20 credits each month
- 10 saved schemas
- 3 workspace members
- 2 API keys
- 5 concurrent jobs
Pricing
One resolved page. One credit.
Every plan below is self-serve with a published monthly price and page-credit allowance, loaded from the same catalogue that powers checkout. Volume, residency, support, or procurement requirements beyond these plans are handled as a custom annual agreement.
Basic
$20/month
5,000 credits each month
- 50 saved schemas
- 10 workspace members
- 10 API keys
- 50 concurrent jobs
Pro
$50/month
15,000 credits each month
- 200 saved schemas
- 50 workspace members
- 25 API keys
- 200 concurrent jobs
Enterprise
$100/month
40,000 credits each month
- 1,000 saved schemas
- 200 workspace members
- 100 API keys
- 1,000 concurrent jobs
Metering
Count the work you can explain.
A native image resolves as one page and consumes one page credit; a PDF is metered as one credit per rendered page. Your billing workspace shows the current balance, cycle, plan allowance, and available purchase options.
Published prices above are USD base prices loaded from the tracked Paddle catalogue. Paddle Checkout remains the source for tax treatment, localized totals, and payment methods.
Custom agreements
Past the published plans, it becomes a contract.
The Enterprise plan above is self-serve at its published price and allowance. Beyond it — higher volume than 40,000 credits a month, specific residency, a contractual service level, or a procurement process — the terms are negotiated in an annual agreement.
Commercial terms
Custom volume and negotiated limits under an annual direct contract, with invoicing and payment terms documented in the agreement. Invoice payment terms: TBD, to be agreed in the executed contract.
Security and data terms
Account-specific security review, data processing terms, residency requirements, and access-control requirements are handled during contracting.
Support and SLA
A support commitment with response targets and a contractual service level agreement. Support response targets: TBD, to be agreed in the executed contract. Contractual SLA target: TBD, to be agreed in the executed contract.
Guided onboarding
A guided onboarding commitment aligned to the agreed deployment plan. Guided onboarding commitment: TBD, to be agreed in the executed contract.
Procurement
How a larger buyer transacts.
Routeser transacts custom agreements by direct contract today. The process covers the order, annual commitment, invoicing, security review, data processing terms, support commitments, and negotiated operating limits. The published plans, including Enterprise, are bought directly through checkout and need none of this.
Routeser does not currently claim an active cloud marketplace listing. The intended marketplace path, if introduced, follows negotiated private offers, standardized marketplace contract terms, and custom payment schedules; availability will be stated only after a listing exists.
FAQ
Frequently asked questions
What is a page credit?
One credit represents one resolved page. A native image counts as one page; a multi-page PDF counts each rendered page.
Where can I confirm the final total?
Sign in to the billing workspace. Paddle Checkout shows the final amount, tax, and currency before you confirm a purchase.
How is the Enterprise plan purchased?
Like the other published plans: self-serve through checkout at the price and allowance shown above.
When do I need a custom agreement instead?
When you need more volume than the published plans provide, a specific data-residency arrangement, a contractual service level, or a procurement and security review. That is an annual direct contract. Routeser does not currently claim an active cloud marketplace listing.
Next step
Discuss a custom agreement
Tell us about expected volume, workflow, regions, security and procurement requirements, and your target timeline.