Back to insights

Multi-tenant platform: every partner under their own brand

Multi-tenant platform showing several brand identities depending on the tenant

For many software vendors, a multi-tenant platform simply means separating databases. That separation is essential, yet it falls short. When a franchisee, an accounting firm or a reseller uses your solution to serve their own customers, they want the experience to carry their name, not yours. Their landing page, their logo, their colours and, ideally, their domain. Here is how we built this customisation layer, along with the questions to ask before you launch a white-label offer.

When a multi-tenant platform becomes strategic

  • Franchises: each location wants its own storefront while sharing the network's tools.
  • Partner networks: accounting firms, agencies or consultants who resell your solution and use customisation as a sales argument.
  • API resellers: integrators who embed your backend in their product and refuse to show a “Powered by” notice everywhere.

A header and interface in the tenant's colours

On our multi-tenant platform, the header and shell components read the current tenant's configuration at render time. Logo, display name, navigation links, contact or customer-area buttons: you configure everything without touching the code. CSS variables follow the same logic. As a result, a colour or typography change in the admin panel applies immediately, with no new build and no redeployment.

A dedicated landing page for each partner

A landing engine assembles the home page from reusable blocks: hero, features, testimonials, pricing, FAQ and call to action. Rendering stays dynamic. In a multi-tenant platform, the same public URL therefore displays the landing page of the tenant detected through the subdomain or the path. Each partner also sets their own SEO metadata, such as page titles and descriptions.

Dedicated domain or sub-path

Our multi-tenant platform offers two modes:

  • Sub-path (for example example.be/my-partner): instant setup, with no technical configuration.
  • Dedicated domain (for example my-partner.be): a DNS change is all it takes, then our edge layer manages the SSL certificate automatically.

If the partner sends emails from their own domain, plan the SPF and DKIM records as well. Without them, their messages may end up in spam folders. Finally, think about SEO: each partner domain should declare its own canonical URL to avoid duplicate content across tenants.

A self-service branding API

A tenant should never have to call us to change a logo. A REST API lets them read and update their configuration: visual identity (logo, colours, SEO metadata) on one side, landing page blocks on the other. Our own admin interface uses this very API. Tenants therefore get the same level of control as the operators of the multi-tenant platform.

Security and data isolation

Visible customisation is worthless without solid separation. Our multi-tenant platform combines three complementary layers:

  • Logical isolation in the database: every sensitive entity (customers, invoices, contracts, users) carries a mandatory tenant identifier, checked in every query.
  • Scoped sessions: a user logged in to one tenant only sees that tenant's data.
  • Logging: every action records the tenant involved.

On the GDPR side, clarify roles in your contracts. The partner often acts as data controller for their customers, while the software vendor acts as processor.

Use cases already in production

  • An accounting firm in Wallonia: its own subdomain, its brand guidelines and invoices sent in its name, on our infrastructure.
  • A consultant network: one landing page per consultant, scoped roles and permissions, and a global dashboard for the network head office.
  • An API integrator: it resells the product with its own terms and support, while we stay invisible.

Multi-tenant platform: questions to ask yourself

  1. How many partners do you expect, and how much customisation do they need?
  2. Do your partners need their own domain, or will a sub-path do?
  3. Who provides first-line support: you or the partner?
  4. How will you charge: per partner, per end user or by volume?
  5. Which data can each partner export if they leave your programme?

Who is it for?

Do you run a network, a franchise or a reseller programme, and are you thinking of building your portal yourself? Then ask yourself: how much time, how many euros, how many people? Our multi-tenant platform delivers the same promise in a few hours of configuration. Explore our custom web platforms or tell us about your partner network.

Need help with your project?

Contact Espero-Soft to discuss your IT needs