Web manager: one place for runtime, routing and protection

A hosting account may contain a main site, several subdomains, an application on a separate port, and a legacy domain that redirects to its current destination. Web Manager presents those domains as the working set instead of spreading their settings across unrelated pages.

Each row keeps the domain, document root, runtime, routing, certificate, and protection context together. That makes a simple question - "what serves this hostname?" - answerable without inspecting several generated virtual-host files.

Let each workload use its runtime

PHP sites can select an installed SHM PHP version and control settings such as OPcache through the domain configuration. Node.js applications can route through their configured local application port. Static sites can remain static. Web Manager does not force every workload through the same runtime just because they share an account.

Changes are written through the shared web configuration path and regenerated for the active server stack. That shared contract matters on servers using Nginx, Apache, or the combined proxy arrangement: the panel edits the domain intent, while SHM produces the appropriate runtime configuration.

Keep routing, TLS and cache in view

Certificate assignment, HTTPS redirect behavior, and server cache can be managed per domain. Redirect rules cover both path-level and full-domain moves, which keeps a permanent migration separate from a temporary application route. A domain can use a specific certificate, and supported wildcard certificates can cover matching subdomains without repetitive assignment work. Server cache remains an explicit per-domain setting. It connects to Cache Manager, where eligibility, exclusions, invalidation, and live checks are visible. This keeps cache behavior testable instead of reducing it to an unexplained toggle.

Apply protection at the narrowest layer

Web Manager connects domain settings to HTTP Guard and ModSecurity. HTTP Guard can apply a protection profile, monitor traffic, protect selected URI patterns, and use smart protection where configured. ModSecurity can run in the chosen mode, apply an application profile, and manage bounded rule ID or tag exclusions when a legitimate request needs a precise exception.

There are also domain restrictions and blocked-bot controls for cases that do not require a full security-rule exception. The goal is to limit an exception to the specific request, rule, or domain that requires it instead of disabling a broader protection layer.

Bulk changes should still be explicit

When several domains need the same setting, Web Manager supports selected-domain bulk operations. Selection stays explicit, and the resulting configuration still belongs to each domain. This is useful for certificate changes, runtime policy, or protection settings across a related group without making every domain on the account identical. Web Manager is ultimately a control surface for web intent. It keeps the everyday choices approachable while preserving the real distinctions between runtimes, hosts, certificates, redirects, cache, and security. That is what makes it useful after the first site becomes ten.