{"id":6229,"date":"2026-09-03T10:32:37","date_gmt":"2026-09-03T07:32:37","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6229"},"modified":"2026-09-03T10:32:38","modified_gmt":"2026-09-03T07:32:38","slug":"branding-toggle-three-web-servers","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/branding-toggle-three-web-servers\/","title":{"rendered":"One Toggle, Three Web Servers: How SPanel Propagates Your Brand Across Apache, Nginx, and OpenLiteSpeed"},"content":{"rendered":"\n

SPanel’s white-label branding is one switch in the Admin Interface, but it rewrites configuration across every web server the panel supports: Apache behind Nginx, and OpenLiteSpeed. <\/p>\n\n\n\n

Enabling it moves the panel to the neutral \/hostpanel path on every hosted domain, updates the webmail entry links, and reloads the web services. New domains inherit the branding, and SPanel updates reassert it. White-label branding is included for free on every ScalaHosting managed VPS.<\/p>\n\n\n\n

A reseller who never re-applies anything<\/strong><\/h2>\n\n\n\n

Here is a hypothetical scenario. <\/p>\n\n\n\n

Tomas runs a 40-client reseller business out of Tallinn. Most of his clients never think about who supplies the hardware, exactly how he wants it. The panel they log into shows his company name, carries his logo, and answers at their own domain. <\/p>\n\n\n\n

What Tomas never sees is the part that holds it together: every time he adds a client and every time SPanel updates, the branded login has to be re-stamped into the web server configuration – and he has never re-applied it by hand. <\/p>\n\n\n\n

That reliability is the unglamorous engineering work behind a single toggle.<\/p>\n\n\n\n

What the branding toggle actually does<\/strong><\/h2>\n\n\n\n

When you enable branding from the SPanel Admin Interface, you set three things: your company name<\/strong> in the “Enter Your Brand<\/em>” field, your logo<\/strong> under “Custom logo<\/em>“, and the branded state<\/strong> itself – chosen under “Login URL<\/em>” as either the default \/spanel or the neutral \/hostpanel. From there, SPanel does the mechanical work.<\/p>\n\n\n\n

To put it simply, the branding toggle rewrites the web server configuration that routes panel traffic on every hosted domain, so the panel answers at the neutral \/hostpanel path instead of the default \/spanel path.<\/p>\n\n\n\n

That rewrite is the whole story. <\/p>\n\n\n\n

The panel does not move to a different server or port; the same backend answers. What changes is the public path<\/strong> the web server hands those requests to, plus the name and logo shown once you see the page. The login page, the webmail entry links, and the API endpoint all follow the branded \/hostpanel path, which says nothing about which panel runs underneath. <\/p>\n\n\n\n

Three web servers, one switch<\/strong><\/h2>\n\n\n\n

Here is where the word “toggle” undersells the work. <\/p>\n\n\n\n

SPanel servers do not all run the same web stack. Some run Apache with Nginx in front of it as a reverse proxy – a front-line web server that receives each request and forwards it to the right backend; others run OpenLiteSpeed<\/a>, a separate high-performance web server that handles the request directly.\u00a0<\/p>\n\n\n\n

That is three distinct web server programs, each with its own configuration format, and branding has to speak all three dialects so a reseller never has to know which one their server runs.<\/p>\n\n\n\n

What the toggle rewrites<\/td>Apache + Nginx stack<\/td>OpenLiteSpeed stack<\/td><\/tr>
Panel routing path<\/td>Virtual host and proxy rules updated to \/hostpanel<\/td>Virtual host config updated to \/hostpanel<\/td><\/tr>
Per-domain coverage<\/td>Every hosted domain’s vhost rewritten<\/td>Every hosted domain’s vhost rewritten<\/td><\/tr>
Webmail entry links<\/td>Login and logout links repointed<\/td>Login and logout links repointed<\/td><\/tr>
Going live<\/td>Web services reloaded automatically<\/td>Web services reloaded automatically<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

From the Admin Interface you see one confirmation. <\/p>\n\n\n\n

Underneath, SPanel has rewritten every domain’s configuration<\/strong>, recorded the branded state<\/strong>, and reloaded the web services<\/strong> – without you opening a config file or restarting a service.<\/p>\n\n\n\n

Planning your own white-label setup?<\/strong> The mechanics matter more than the logo upload. Enable branding on a managed VPS<\/a>, add a second hosted domain, and watch the panel serve both at your brand’s \/hostpanel login, nothing left to re-apply.<\/p>\n\n\n\n

Why new domains inherit branding<\/strong><\/h2>\n\n\n\n

A branding setting that only applies to the domains present when you flip it is a trap. You would enable branding on Monday, add three client domains on Tuesday, and quietly ship them the default \/spanel login. SPanel avoids that by treating branding as a property the server checks, not a one-time action it performs.<\/p>\n\n\n\n

Every code path that writes a fresh web server configuration consults the branded state first. New account creation, adding an addon domain, adding a subdomain, changing an account’s main domain – each one generates its virtual host with the branded path already in place. You enable branding once, and the server keeps every future domain consistent with it. <\/p>\n\n\n\n

That is the difference between a branding setting and a branding system, and it is why your clients always log in at their own domain without you lifting a finger.<\/p>\n\n\n\n

Because the branded state is server-wide, one server carries one brand. If you want to manage two brands, that means two servers, which is cleaner anyway.<\/p>\n\n\n\n

Why an update doesn’t strip your brand<\/strong><\/h2>\n\n\n\n

Anyone who has customized software has been burned by an update that quietly resets it. SPanel’s updater is branding-aware. When it regenerates configuration, it reasserts the branded path in everything it touches, including the webmail login and logout links. There is no post-update checklist, and no clients staring at \/spanel while you notice and fix it. <\/p>\n\n\n\n

One more surface follows the brand: the API endpoint.<\/strong> <\/p>\n\n\n\n

With branding enabled, SPanel’s API answers at the branded path too, so integrations address the same neutral URL the panel uses. That behavior is in the official SPanel API documentation<\/a>, which matters for resellers wiring the panel into a billing system.<\/p>\n\n\n\n

A branding feature you have to babysit isn’t a feature. Its real job is staying true after every new domain and every update.<\/p>\n\n\n\n

This is where SPanel diverges from the wider category. <\/p>\n\n\n\n

Per cPanel’s own documentation, that panel’s login page cannot be rebranded at all. SPanel makes the login page the centerpiece of the brand and moves it with one switch. For the full set of places a provider’s name can leak, the complete white-label checklist is the reference to keep open.<\/p>\n\n\n\n

Demo flow<\/strong><\/h2>\n\n\n\n

Steps to reproduce this on a demo SPanel server:<\/p>\n\n\n\n

    \n
  1. Log into the Admin Interface<\/strong> and open the branding screen (Server Management \u2192 Branding<\/strong>). Set “Enter Your Brand<\/em>” to your business name and upload your logo under “Custom logo<\/em>“.<\/li>\n<\/ol>\n\n\n\n
    \"One<\/figure>\n\n\n\n
      \n
    1. Under “Login URL<\/em>“, select the neutral \/hostpanel path and click Save Changes<\/strong>. SPanel rewrites the configuration for every hosted domain and reloads the web services.<\/li>\n\n\n\n
    2. Open a hosted client domain at the branded login path to confirm the panel answers there under the new brand.<\/li>\n<\/ol>\n\n\n\n
      \"One<\/figure>\n\n\n\n
        \n
      1. Open a second hosted domain and visit its branded login. The new domain serves the branded page with no extra step, demonstrating inheritance.<\/li>\n<\/ol>\n\n\n\n
        \"One<\/figure>\n\n\n\n

        See it on a real server<\/strong><\/h2>\n\n\n\n

        Branding is included free on every ScalaHosting managed VPS, with no per-account fee. SPanel runs the infrastructure behind over 700,000 websites across 120+ countries (ScalaHosting<\/a>), for a company in business since 2007. <\/p>\n\n\n\n

        If there is a branding behavior you wish SPanel handled differently, the Cloud Democracy board at features.spanel.io<\/a> is where resellers vote on it.<\/p>\n\n\n\n

        Frequently asked questions<\/strong><\/h2>\n\n\n\n

        Q:<\/strong> What exactly does the branding toggle change on the server?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> It rewrites the configuration that routes panel traffic on every hosted domain, switching the panel from \/spanel to the neutral \/hostpanel path, and repoints the webmail entry links and the API endpoint to match.<\/p>\n\n\n\n

        Q:<\/strong> Does it work the same on Apache and OpenLiteSpeed servers?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> Yes. The toggle writes the correct configuration for whichever stack the server runs, so the result is identical from the reseller’s side.<\/p>\n\n\n\n

        Q:<\/strong> Do I have to re-apply branding when I add a new client domain?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> No. New accounts, addon domains, and subdomains generate their configuration with the branded path already applied. You only need to enable it once.<\/p>\n\n\n\n

        Q:<\/strong> Will an SPanel update reset my branding?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> No. The updater reasserts the branded path in the configuration it regenerates, including the webmail login and logout links.<\/p>\n\n\n\n

        Q:<\/strong> Can I set a completely custom login path like<\/strong> \/mybrand?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> No. The “Login URL” setting on the branding screen offers two choices – the default \/spanel or the neutral \/hostpanel – not an arbitrary custom path. The neutral \/hostpanel reveals nothing about the panel software and is inherited by every new domain.<\/p>\n\n\n\n

        Q:<\/strong> Does hiding the<\/strong> \/spanel<\/strong> path make my server more secure?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> Treat it as reduced casual fingerprinting, not security. It removes the most obvious signal of which panel runs the server, but a determined party can still identify it. SPanel’s real protection is SShield<\/a>.<\/p>\n\n\n\n

        Q:<\/strong> Does the API use the branded path too?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> Yes. With branding enabled, the SPanel API endpoint follows the branded URL, so your integrations address the same neutral path as the panel.<\/p>\n\n\n\n

        Q:<\/strong> Can one server show two different brands?<\/strong>\u00a0<\/p>\n\n\n\n

        A:<\/strong> No. Branding is server-wide: one company name, one logo, one path per server. To run two brands, run them on two servers.<\/p>\n\n\n\n