Deployment modesTwo ways to ship. Same accounting core underneath.
Pick the isolation level your books need. Both modes use the same double-entry engine, the same OAuth flows, the same signed audit log, and the same MCP surface.
Multi-tenant cloud
Shared cluster · logical tenant isolation.
Each customer's books live in a logically isolated tenant — separate ledger, separate audit log, separate OAuth scopes. Runs on Paprel's managed cloud, region-pinned (US, EU, or APAC). Sandbox to first posted journal in days.
Region-pinned booksOAuth 2.0 / 2.1MCP surfaceSigned webhooks
Best fit
Best for teams shipping embedded or white-label accounting fast — fintechs, vertical SaaS, design partners.
- Isolated books per customer
- Per-tenant OAuth scopes
- Region-pinned ledger data
- Signed audit log · 7-year retention
- Hosted or headless UI
- MCP tool surface included
- First posted journal in days
Dedicated instance
Fully isolated cluster · managed or BYOC.
Your own Paprel cluster — separate compute, separate database, separate observability. Managed cloud (Paprel runs it) or private cloud / BYOC (we deploy into your VPC). Same accounting APIs and dashboards, no shared infrastructure with other customers.
Dedicated clusterManaged or BYOCCustom SLACustom residency
Best fit
Best for regulated platforms, custom data residency, and teams that need their own SLA, region, and upgrade window.
- Fully isolated ledger + storage
- Choose region + instance class
- Custom SLA + upgrade window
- Managed cloud or BYOC
- Private VPC support
- Security-review aligned
- Same OpenAPI + OAuth surface
01Customers with active books
A customer counts as active in a billing period if it has posted journals or read reports. Dormant tenants are free.
02Posted journals per month
Volume tier based on monthly posted journal entries across all your tenants. Drafts, reversed entries, and read-only ledger queries don't count.
Standard multi-tenant SLA is included. Dedicated cluster, custom SLA, and private cloud / BYOC add a platform fee on top of the per-customer rate.
Concrete numbers during the architecture review — design-partner pricing applies for first-wave teams.
Programmable double-entry engine. Balanced postings only, idempotent on retries, multi-entity, multi-currency with FX revaluation.
POST balanced journals with debits and credits. Drafts, approvals, posting, and reversals are first-class API states — not UI conventions.
Bank, sub-ledger, and inter-entity reconciliation primitives. Match programmatically or expose to a reviewer; both share the same engine.
P&L, balance sheet, trial balance, and GL export served from the same ledger — no separate analytics DB to keep in sync.
Standard authorization flows with PKCE. Tenant-scoped tokens with per-route grants. Same scopes power REST, MCP, and machine-to-machine.
Role-based controls per tenant. Reviewer, approver, and operator roles map to ledger states. Cross-tenant reads need explicit grants.
Scoped MCP tool surface for AI agents. Signed webhooks with 30-day replay. Drafts only — every agent edit lands as a pending journal.
Content-hashed envelope per mutation: actor, action, before/after, signature. Queryable by entity, actor, or time window. 7-year retention.
Architecture review
Map the fit in 48 hours.
Deployment mode, OAuth consent, RBAC, MCP scope, audit, residency, rollout — all on the table.
Design-partner pricing available for teams shipping on Paprel in the first wave.