A white label website platform that runs your clients' whole businesses
Sites, stores, bookings and back office for every client — under your brand, on their domains, with their data kept apart. You stay the agency; Olmira stays out of sight.
Most white-label offers rebrand a page builder and stop there. Olmira white-labels the entire operation: the control panel your clients log into carries your name, logo and colours; its emails send under your identity; and the "Powered by Olmira" mark comes off their sites. Underneath, each client gets the full platform — online store, bookings, CRM and management — so you are reselling a real product, not a facade.
A white label website platform — the control panel becomes your product
The White-label pack rebrands Olmira Control end to end: your product name in the header and browser tab, your logo and favicon, your colours applied as design tokens across every screen, and your own support and legal URLs behind the help links. Email goes out under your sender identity — and because Olmira supports per-tenant SMTP, from your own mail server too. The branding is entitlement-gated, so it is applied consistently or not at all, never half-on.
See how email sending works → /integrations
Separation you can explain to a client in one sentence
"Your data is in its own database." That is the architecture, not a metaphor: every Olmira account gets a database of its own, with its own generated credentials, so one client's orders, customers and content are held apart from the next client's. On Pro+ the separation goes further — the account is provisioned on Olmira's isolated tier, with its own database and its own connection endpoint rather than the one lower tiers share, which is the difference that matters when a client's procurement team starts asking questions. It is a better answer than most agencies can give, and it costs you nothing extra to say it truthfully.
none
Team roles that match how an agency actually works
Seats come with the plan — 10 on Pro, 25 on Pro+, unlimited on Business — and roles are yours to define: build "Client editor" once, set its permissions in a matrix, and reuse it across clients. Delegated access confines a client's login to their own workspace. Revokes always win over grants, and every gate is enforced server-side, so a mis-clicked checkbox fails closed rather than open.
AI on your own terms → /ai-assistant
Bring your own AI
What it costs, in real numbers
The control panel (name, logo, favicon, brand colours, support and legal links), the emails it sends (your sender name, and your own SMTP if you want), and client sites lose the "Powered by Olmira" mark. The white-label surface is the product your clients touch.
Not on their sites, not in the rebranded control panel, and not in the emails it sends. Your subscription and its billing remain between you and Olmira — your clients are your customers, not ours, and we do not contact them.
They do — each client account connects its own Stripe, PayPal or Klarna, the money settles there directly, and Olmira takes €0 platform fee on sales. You bill your clients for your services however you already do; Olmira bills you for the subscription.
Yes — one database per account is how Olmira is built, on every plan. Pro+ goes a step further: the account is provisioned on the isolated tier, with a separate database and its own connection endpoint rather than the one lower tiers share.