ScalaHosting has started rolling out seven new features for its SPanel hosting control panel, adding Git deployment, server clustering, DNS replication, passkey login, expanded white-label controls, domain-wide email forwarding and pre-optimised WordPress installations.

The company says the features are being added at no extra cost and require no additional software installation, with the rollout expected to reach all eligible accounts over roughly two weeks.

Only the new login options have been publicly documented in detail so far, meaning several of the other features remain based on ScalaHosting’s description of what users should expect as they begin appearing inside SPanel.

Git deployment moves into the control panel

One of the more useful additions is built-in Git version control, allowing users to clone public or private repositories from services including GitHub, GitLab and Bitbucket, as well as self-hosted repositories accessible over SSH.

Repositories can be kept in sync on a schedule or updated automatically through push webhooks. Users can also switch branches, check repository status, review commits and run deployment scripts after a pull directly from SPanel.

For developers, the practical change is fairly simple. A site update can move from manually uploading files over FTP to pushing code through Git.

The larger difference is that ScalaHosting has put much of that workflow inside the hosting panel, opening it up to people who may be comfortable working with Git but do not necessarily want to manage deployments entirely through SSH.

There’s some risk attached to that convenience. Automatically running a deployment script after every webhook pull can cause problems very quickly if production is tied to the wrong branch or an untested change slips through.

For production sites, using a dedicated release branch and maintaining a working restore point before enabling automated deployment would be the safer setup.

sPanel Gets Multi-Server Cluster Management

ScalaHosting is also introducing cluster management that allows several servers to operate as part of the same SPanel environment.

The system can assign different roles to nodes handling web traffic, databases and email, while shared storage and health monitoring are used across the cluster. A built-in load balancer can distribute traffic between web nodes, with additional capacity added as demand grows.

This is unlikely to matter much to someone running one small WordPress site.

It becomes far more useful once a business is pushing against the limits of a single server, particularly where an outage has a direct financial cost. With multiple nodes available, the failure of one server can reduce capacity without necessarily taking the entire service offline.

ScalaHosting has already offered managed cluster hosting as a separate product. Bringing cluster controls into SPanel gives customers more direct control over an infrastructure setup that previously required more involvement from the hosting provider.

The cluster feature itself may be included for free, but running a cluster still means paying for several servers. You will need to pay for an additional VPS.

DNS Clustering Removes Another Single Point of Failure

A new DNS clustering feature allows standalone DNS servers to be attached to an SPanel server, with DNS zones automatically replicated between them.

Changes made to a zone are synchronised across the connected DNS servers without administrators having to manually copy zone files or build their own replication system.

That is particularly relevant for resellers, agencies and hosting providers using branded nameservers such as ns1.example.com and ns2.example.com.

Running DNS from one physical machine creates an obvious weakness. If that server fails, visitors may be unable to resolve a domain even if the website itself is sitting on a perfectly healthy server elsewhere.

For customers already using a hosting provider’s distributed shared nameservers, however, the feature is unlikely to change much.

Passkeys Arrive Alongside Google & GitHub login

The new authentication system is the most clearly documented part of the SPanel update.

Users can now sign in using a Google account, GitHub account or a passkey based on the WebAuthn standard used by systems including Windows Hello, Face ID, Touch ID and physical security keys.

Unlike a traditional password, the private key used by a passkey remains on the user’s device. SPanel stores the corresponding public key and verifies a cryptographic challenge during login.

That makes passkeys considerably harder to steal through a conventional phishing page because there is no reusable password being sent to the server.

Traditional password authentication and TOTP two-factor authentication remain available.

Keeping a fallback method is still sensible. Anyone who loses every device containing an enrolled passkey without another authentication method available could end up locking themselves out of the control panel.

ScalaHosting published details of the passkey system on August 11, 2026, and says it is included with managed cloud VPS accounts at no additional cost.

WordPress Installs Now Arrive Pre-Tuned

New WordPress installations on ScalaHosting cloud plans are also getting a more aggressive performance configuration from the beginning.

The setup includes LiteSpeed Cache configured with a high-performance profile, Redis object caching, a current PHP version and a server-level cron job replacing the default WordPress wp-cron system.

SPanel also warms the cache and checks that pages are actually being served from cache before the installation process is considered complete.

That last part matters more than it sounds.

Installing a caching plugin is easy. Confirming that the cache is actually being hit is where some hosting setups fall apart, particularly once other plugins, cookies or dynamic pages become involved.

Replacing wp-cron with a real server cron is also a sensible change because WordPress normally triggers scheduled jobs through visitor requests. Busy or badly configured sites can end up doing unnecessary work at exactly the wrong time.

The default configuration will still need checking on more complicated websites. WooCommerce stores, membership platforms and sites with large numbers of logged-in users can behave badly when aggressive caching rules are applied without exclusions.

A configuration that produces excellent benchmark results on a normal blog can cause a shopping cart to become a very different problem.

More white-label control for agencies and resellers

ScalaHosting has also expanded SPanel’s white-label features.

Resellers and agencies can now customise more of the control panel experience with their own logo, colours, company name and a custom login URL instead of directing customers through the standard /spanel address.

It is a relatively small feature technically, but one that matters to hosting businesses trying to keep the customer experience under their own brand.

Domain-wide email forwarding is also being added.

Instead of creating individual forwarding rules for every mailbox, administrators can forward mail for an entire domain to one or more destination domains.

For example, mail sent to sales@old-domain.com can automatically arrive at sales@new-domain.com, while the same happens for info@, support@ and other matching addresses.

It should make domain migrations, company rebrands and mergers considerably less tedious.

Rollout expected to take about two weeks

ScalaHosting says all seven features are included without an additional software licence or separate installation process and will appear inside SPanel as the staged rollout reaches each account, with the company expecting the process to take around two weeks.

The larger question is how much these additions increase dependence on SPanel itself.

Git deployment, DNS replication and clustered hosting are hardly new ideas, but the workflows ScalaHosting is building around them are specific to its own control panel.

That is the familiar trade-off with a proprietary hosting platform. The more useful the panel becomes, the more infrastructure and routine ends up built around it.

For existing SPanel users, however, this is a fairly substantial update. Some of the additions are small quality-of-life improvements, while others move features normally associated with more complicated server administration directly into the control panel.

The real test will come once all seven are live across customer accounts and users can see whether the implementation is as useful in production as it looks on paper.