A White-Label Ecommerce Platform Your Clients Think You Built.
Your domain, your name, your icon. Twenty-two modules to switch on per client, record types you define yourself, and none of your clients ever meeting us. You are the software company; we are the part underneath that you never have to maintain.
Twenty-Two Modules, Switched On Per Client
An agency running websites and a distributor running inventory should not be looking at the same sidebar. They are not.
Projects, Tickets, Planner, Calendar, Team
Client Work
The operational half of an agency: what is being done, who is doing it, and when it is due.
Invoices, Expenses, Reports
Money
Billing your clients and knowing what the work actually earned.
Inventory, Customers, Contacts, Forms
Their Store
The commerce side, if the clients you serve are selling something.
Websites, Pages, Media
Their Site
Sites and the content in them, with images handled on upload.
Email, Klaviyo, Giveaways, Insights
Reach
Mail, the marketing tool most clients already run, and first-party traffic on their own sites.
Records, Integrations, Logs
The Rest
Custom record types, third-party connections, and an audit trail of every change.
A Platform Is A Row, Not A Fork.
Your instance has its own slug, name, description, icon and custom domain, and a list of the modules it runs. That is configuration, which has two consequences worth caring about.
Setting one up takes an afternoon rather than a deployment. And every improvement to the underlying platform reaches your clients without you merging anything, because there is nothing to merge.
Invent The Records You Need.
When none of the twenty-two fit, define a record type. Its name, its fields and its views are stored as data, so a kind of record specific to your industry can exist today and change again next week without a migration.
That is usually the difference between a vertical SaaS you could sell and a generic dashboard your clients tolerate.
Read The Whole Thing First
Reselling somebody else's platform is a serious commitment, so the reference is public and detailed rather than gated behind a call.
Overview
What the white-label layer is, in the introduction.
Modules
What each of the twenty-two does, in the modules reference.
Records
Defining your own record types, in the records guide.
Sites
Client sites and the keys behind them, in the sites guide.
Security
How tenants are kept apart, in the security guide. Read this one before signing anything.
Operations And Use Cases
Running it day to day, in operations and use cases.
Questions People Ask
What does white-label actually mean here?
Your clients sign in to your domain and see your name and your icon. A platform is a row with its own slug, domain and branding rather than a forked copy of the software, which is why setting one up is configuration rather than a deployment, and why improvements to the underlying platform reach your clients without you merging anything.
Can I choose what each client sees?
Modules are switched on per platform, from a set of twenty-two covering client work, billing, commerce, sites, marketing and the audit log. An agency running websites and a distributor running inventory should not be looking at the same sidebar, and they do not have to.
What if my clients need something none of the modules cover?
Define a record type. It gets its own name, its own fields and its own views, stored as data rather than as a schema change, so a kind of record specific to your industry can exist by the end of the afternoon and change again next week. Past that, custom development is a separate conversation.
Who holds the customer relationship?
You do. Your clients are your clients: they sign in to your domain, they see your brand, and they never encounter ours. What we are is the thing underneath, which is the correct place for us to be if you are the one selling.
Is the data isolated between clients?
Every record belongs to an organization and queries are scoped to it, which is the same boundary the rest of the platform runs on rather than something added for resellers. The security documentation covers the specifics, and reading it before signing anything is the right instinct.
What does it cost to run?
That is a conversation rather than a page, because a reseller arrangement has more moving parts than a plan does: how many clients, which modules, whose infrastructure. There is no published number here, and one invented for a marketing page is the one a partner would hold us to later.
Tell Us Who Your Clients Are.
Which modules they need, what you would call it, and where it should live. That conversation is the whole setup.