{"id":6370,"date":"2026-10-05T09:30:12","date_gmt":"2026-10-05T06:30:12","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6370"},"modified":"2026-10-05T09:30:13","modified_gmt":"2026-10-05T06:30:13","slug":"multi-brand-hosting-one-server","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/multi-brand-hosting-one-server\/","title":{"rendered":"One Server, One Brand: How to Plan Multi-Brand Hosting the Right Way"},"content":{"rendered":"\n

Running a branded business online is easy with the right hosting partner.<\/p>\n\n\n\n

SPanel, ScalaHosting’s free control panel, applies white-label branding server-wide: one company name, one logo, one neutral login path per server. To run two hosting brands, run two servers – one for each business. <\/p>\n\n\n\n

That split isn’t a limit to engineer around. <\/p>\n\n\n\n

It keeps billing, support, DNS, and client data cleanly divided. The entire process comes at no added cost for resellers, as SPanel is already included in your hosting plan.<\/p>\n\n\n\n

The question that follows every white-label setup<\/strong><\/h2>\n\n\n\n

Here is a scenario many resellers are way too familiar with:<\/p>\n\n\n\n

James runs two small hosting brands out of Manchester – WordPress care plans on one, agency clients on the other. He has just branded his first SPanel server with his name, his logo, and a clean login page. Now he wants the second brand on the same box, because a second server feels like overkill. <\/p>\n\n\n\n

It’s a reasonable instinct and a common case. The honest answer is rather simple: branding is server-wide, so one server carries one brand. That is not done so that your hosting provider can squeeze more money out of you. It\u2019s a logical setup for business owners with multiple brands, clients, and business models.<\/p>\n\n\n\n

In one sentence:<\/strong> SPanel branding is global to the server, so each server presents exactly one brand, and the clean way to run several brands is one server per brand.<\/p>\n\n\n\n

Here is the answer to \u201cwhy.\u201d<\/p>\n\n\n\n

Why one server holds one brand<\/strong><\/h2>\n\n\n\n

Enabling branding in the Admin Interface<\/strong> does more than swap a logo. SPanel rewrites the web server configuration for every hosted domain so the panel answers at the neutral \/hostpanel path, updates the proxy that routes panel traffic, rewrites the webmail entry links, and records the brand for new accounts to inherit. <\/p>\n\n\n\n

That work is deliberately server-wide; it’s what makes branding stick without you re-applying it.<\/p>\n\n\n\n

The same scope is why one server can’t show brand A to some clients and brand B to others: there is one name, one logo, one login path recorded for the server, and every domain reads from it. The full per-brand setup is the short five-minute branding walkthrough<\/a>, run once per server.<\/p>\n\n\n\n

\"One<\/figure>\n\n\n\n

Why two servers is the cleaner architecture anyway<\/strong><\/h2>\n\n\n\n

Treat “one brand per server” as planning guidance, and the two-server pattern is the design you’d choose on purpose.<\/p>\n\n\n\n

Billing and identity stay separate.<\/strong> Two brands mean two storefronts and two inboxes; one server each keeps the books and client lists from bleeding together.<\/p>\n\n\n\n

A problem on one brand doesn’t touch the other.<\/strong> A reboot, rollback, or migration on brand A never reaches brand B’s clients, and brand B’s busy launch day can’t starve brand A of CPU or memory. Separate servers contain both trouble and resource demand for the brand that caused or needed it.<\/p>\n\n\n\n

Planning question<\/strong><\/td>One server, two brands<\/strong><\/td>Two servers, one brand each<\/strong><\/td><\/tr>
Branding<\/td>Not supported<\/td>One clean brand per server<\/td><\/tr>
Billing \/ support split<\/td>Tangled together<\/td>Naturally separate<\/td><\/tr>
Failure blast radius<\/td>Both brands affected<\/td>Contained to one brand<\/td><\/tr>
DNS & mail reputation<\/td>Shared, cross-contaminating<\/td>Independent per brand<\/td><\/tr>
Resource isolation<\/td>Brands compete for CPU\/RAM<\/td>Each brand sized on its own<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Planning two brands?<\/strong> ScalaHosting offers several managed cloud VPS solutions<\/a> designed for cost-effectiveness. If you prefer flexibility – you can always customize your server resources and add more in the future should the need arise. Along with many free features, you also receive SPanel at no added cost to each managed plan.\u00a0<\/p>\n\n\n\n

Planning your multi-brand setup, server by server<\/strong><\/h2>\n\n\n\n

The work per brand is the same short checklist, run once per server.<\/p>\n\n\n\n

    \n
  1. In the Admin Interface<\/strong>, open Server Management<\/strong> \u2192 Branding<\/strong> and type the company name into the Enter Your Brand<\/strong> field.<\/li>\n\n\n\n
  2. Turn on Custom logo<\/strong> and upload that brand’s logo so it shows on the login page and inside the panel.<\/li>\n\n\n\n
  3. Set the Login URL<\/strong> to the neutral \/hostpanel path. SPanel moves the panel to that path across every domain and reloads the web services.<\/li>\n\n\n\n
  4. In Server Settings<\/strong> \u2192 Basic Settings<\/strong>, set the Hostname<\/strong> to that brand’s domain (for example, server1.brand-a.com) so that mail and FTP settings reflect the brand.<\/li>\n\n\n\n
  5. In the same screen, point the brand’s Name Servers<\/strong> (ns1\/ns2) at that server so client DNS delegation shows the brand.<\/li>\n<\/ol>\n\n\n\n

    Steps four and five finish the white-label job and live in the branded hostname and nameservers<\/a> settings.<\/p>\n\n\n\n

    Before you publish either brand, the complete white-label checklist<\/a> lists every place a vendor name can still leak.<\/p>\n\n\n\n

    \"One<\/figure>\n\n\n\n

    To summarize:<\/strong> “One brand per server isn’t a wall you hit. It’s the line that keeps two businesses from sharing one bad day.”<\/p>\n\n\n\n

    When you actually need the second server<\/strong><\/h2>\n\n\n\n

    Split when the second brand becomes real – you want to diversify different clients, pricing, and identity to a separate business name. Until then, one branded server is plenty. <\/p>\n\n\n\n

    It\u2019s great that SPanel is engineered to use a fraction of the server resources that cPanel requires, so a single managed VPS can comfortably support a growing first brand. When brand two arrives, spin up another virtual server, run the five-step checklist, and you have two clean businesses instead of one crowded box.<\/p>\n\n\n\n

    If you’re still planning the first brand, the guide to starting a hosting business on a managed VPS<\/a> is where to begin.<\/p>\n\n\n\n

    Plan it once, run it clean<\/strong><\/h2>\n\n\n\n

    Two brands on two servers sound like more configuration, but the VPS scalability fixes that. Each brand owns its identity, DNS, support queue, and uptime. SPanel makes the per-server part a short, repeatable checklist. <\/p>\n\n\n\n

    If you’d like multi-brand controls to evolve, the Cloud Democracy<\/a> project is where ScalaHosting takes feature requests, and the SPanel API docs<\/a> show how the branded endpoint behaves when you automate across branded servers.<\/p>\n\n\n\n

    FAQ<\/strong><\/h2>\n\n\n\n

    Q:<\/strong> Can I run two hosting brands on one SPanel server?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> No. Branding is server-wide: one name, one logo, one login path per server. Two brands require two hosting servers, where each brand utilizes one.<\/p>\n\n\n\n

    Q:<\/strong> Is that a limitation I should worry about?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> Not really. Separate servers keep billing, support, DNS, and resources cleanly divided, which is how you’d want two businesses structured regardless.<\/p>\n\n\n\n

    Q:<\/strong> Does a second server cost a lot more?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> It’s a second managed VPS, sized for that brand. SPanel and all its features, branding included, are free, so there’s no per-brand white-label surcharge on top. The only cost is the server fee, but you can easily scale that by starting small and expanding as your business grows.\u00a0<\/p>\n\n\n\n

    Q:<\/strong> Can I use a different login path per brand on one server?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> No. The branded path is the neutral \/hostpanel for the whole server, recorded once and inherited by every domain.<\/p>\n\n\n\n

    Q:<\/strong> Will updating SPanel reset the branding on either server?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> No. SPanel’s updater reasserts the branded URL after each update, including the webmail entry links.<\/p>\n\n\n\n

    Q:<\/strong> Where do my clients log in once each brand is on its own server?<\/strong> <\/p>\n\n\n\n

    A:<\/strong> At their own domain plus the branded path, client-site.com\/hostpanel\/login, with the brand of whichever server hosts them.<\/p>\n\n\n\n