Run a white-label reseller practice
A firm that wants to offer practice software to other firms — or run several brands from one operation — normally faces building a platform or stitching together per-seat licences it cannot rebrand. Multi-tenant plumbing, tenant isolation, and support tooling are exactly the parts nobody wants to build.

Firms run a white-label reseller practice on SpidNums by provisioning a tenant per firm, each with its own branding, domain, and isolated data. A super-admin console manages tenants and plan limits, support uses audited impersonation, and every tenant's data is isolated fail-closed and hosted in Canada. Reselling under your own brand is an invited conversation, not a workaround.
How firms run it, step by step
Start the white-label conversation
Reselling is invited — talk to SpidNums about white-label to set up the reseller arrangement before provisioning tenants.
White-label
Provision a tenant per firm
Each firm gets its own tenant with its own branding — name, logo, colours, tagline — and its own client book, staff, and settings.
White-label
Give each firm its own front door
Each tenant runs on its own custom domain or an instant subdomain, so every firm's clients sign in under that firm's name.
White-label
Manage the estate from super-admin
Tenant management, plan limits, and audited impersonation live in the super-admin console — support can see what a user sees, and the access is logged.
White-label
Stand on the isolation guarantees
Per-tenant isolation is enforced by a signed tenant cookie that fails closed, storage is namespaced per tenant, and data is hosted in Canada (ca-central-1).
Security
White-label
Security
Related use cases
Features used
Go deeper
Frequently asked questions
Can we resell SpidNums under our own brand?
Yes — reselling under your own brand is invited. Each firm you bring on runs as its own tenant with its own branding, domain, and isolated data, managed from a super-admin console. Talk to SpidNums about white-label to set up the arrangement.
How is tenant data kept separate?
Each tenant's data is isolated per firm: a signed tenant cookie enforces the boundary and fails closed, storage is namespaced per tenant, and database access runs through row-level security with service-role mediation. Data is hosted in Canada, in Supabase's ca-central-1 region on Postgres 17.
How does support work across tenants?
Through audited impersonation from the super-admin console: an authorised operator can view a tenant as its users see it, and every impersonation is logged. Plan limits per tenant are managed from the same console.
See this workflow with your own client list in it.
A tailored demo walks the exact steps above with your services and deadlines.