Yours
Your domain
TLS, palette, copy, emails, PDFs
Paprel
Our hosting
White-label accounting platform
Ship a full accounting product embedded into your own platform — under your brand, your domain, your customer relationship. The ledger, signed events, OAuth, and audit log are ours to run.

Your surface
Domain · palette · copy · email · PDF · onboarding
Paprel underneath
Double-entry ledger · signed events · OAuth · audit log
The split, in one line
Yours
Your domain
TLS, palette, copy, emails, PDFs
Paprel
Our hosting
Yours
Your customer relationship
Onboarding, support, plan tiers
Paprel
Our ledger
Yours
Your product experience
Navigation, workflow, where books live
Paprel
Our audit log
Everything the customer sees is your brand. Everything keeping the ledger honest is Paprel. Below is what falls in each column.
Brand surface
Custom domain (app.yourbrand.com), color palette, typography, copy, transactional emails, branded PDFs, support persona. Tokenized — change one variable, propagates everywhere.
Delivery mode
Ship our hosted UI under your brand, or call the OpenAPI / OAuth surface from your own frontend. Same primitives behind both — pick per route, not per product.
Tenant isolation
Every customer is a logically isolated tenant with its own ledger, audit log, OAuth scopes, and webhook config. Cross-tenant reads require explicit grants — never accidental.
Your customers, your brand domain, isolated tenants underneath. Each tenant is its own audited ledger — and you choose how isolated the underlying infrastructure is.
Customer A tenant
Customer B tenant
Customer C tenant
Same isolation model running newledger.io today.
Two ways to ship. Same APIs, same audit guarantees, same OAuth surface — different infrastructure boundaries underneath.
Multi-tenant cloud
Each customer is a logically isolated tenant — separate ledger, separate audit log, separate OAuth scopes. Runs on the same managed Paprel cluster as everyone else. Region-pinned (US, EU, or APAC), no cross-tenant access without an explicit grant.
Dedicated instance
Your own Paprel cluster — separate compute, separate database, separate observability. Same APIs and dashboards, no shared infrastructure with other customers. Available as managed cloud (we run it) or private cloud (we deploy into your VPC / cloud account).
Switching modes later is supported — your data and OAuth clients stay valid.
Customer-facing differentiation is yours. Ledger integrity, signed events, and audit trails are ours. Clean handoff per concern.
Brand & domain
Your platform owns
Custom domain, palette, typography, copy, emails, PDFs, support voice.
Paprel powers
Hosting, TLS, CDN, asset pipeline — invisible to your customers.
Workflow surface
Your platform owns
Page layouts, navigation, onboarding flow, what fields users see when.
Paprel powers
Journal posting engine, balance math, FX, multi-entity, multi-currency.
Access control
Your platform owns
User onboarding, plan tiers, customer support workflows.
Paprel powers
OAuth 2.0 / 2.1, RBAC, tenant boundaries, signed audit log of every mutation.
Reporting & exports
Your platform owns
Which reports surface in the UI and how data is visualized.
Paprel powers
P&L, balance sheet, trial balance, GL export, signed replayable webhooks.
Teams pick the white-label path when finance workflows need to live inside their own product, not next to it.
Accounting firms
Ship a firm-branded client portal — every client gets a tenant, your firm gets a fleet view. Reviewer / approver workflows, multi-entity by default, full audit history per client.
Vertical SaaS
Bring invoicing, expenses, journals, and reporting inside the workflow product your customers already use daily. No more 'export to QuickBooks' — books live where the work happens.
Fintech & marketplaces
Add a branded accounting layer above money movement. Customers get books, statements, and tax-ready reports inside your product. Settlement, fees, and platform-level rec stay on the same ledger.
Live reference
NewLedger is the accounting SaaS we run on top of Paprel. Same APIs you'd integrate, same isolation model, same audit guarantees. It's also the white-label reference deployment — what you can ship looks like that.

Every customer is a logically isolated tenant — separate ledger, separate audit log, separate OAuth scopes. Cross-tenant access requires an explicit grant. Tenants are pinned to a single region (US, EU, or APAC) — no cross-region replication.
Yes. Your custom domain (app.yourbrand.com or similar) serves the UI; transactional emails come from your domain; PDFs render with your brand. Paprel infrastructure is invisible to your end users.
Yes. Two modes: (1) use the hosted white-label UI and skin it via tokens — fastest path; (2) build your own frontend against the OpenAPI + OAuth surface — full control. Mix and match per route.
Same as embedded — your data is yours. Full CSV/JSON export, signed replayable webhooks for 30 days, audit log queryable end-to-end. The wire format matches the OpenAPI spec, so you can rebuild books anywhere.
Talk to us. White-label deployments typically combine a platform fee with per-active-tenant pricing. Design-partner pricing is available for teams shipping on Paprel in the first wave.
Next step
Architecture review in 48 hours. Tenant model, brand surface, OAuth flows, exit path — all on the table.
For CTOs, CPOs, and platform engineers shipping accounting under their own brand.