When managing websites through the Enhance web hosting control panel, users are offered flexible options for deploying and organising their websites. Two of the most common choices are creating a containerised website or adding an addon domain under an existing website. While both approaches may appear similar on the surface—after all, both allow hosting multiple domains—they operate very differently under the hood, especially in terms of isolation, security, resource management, and scalability.
In this post, we’ll break down the technical differences between a containerised website and an addon domain within Enhance, and help you determine when to use each.
✅ What Is a Containerised Website?
A containerised website in Enhance is a fully isolated environment, created within its own Linux user account and run in a separate container. This means that each containerised website operates as if it were on its own miniature server, even though it’s hosted on the same physical machine.
Key Features of Containerised Websites:
User Isolation: Each container runs under a different Linux user, ensuring that websites are sandboxed from each other. This is a major security benefit.
Process Separation: PHP processes, cron jobs, and file permissions are completely separate. A compromised site cannot be used to access or exploit other websites on the same hosting account.
Independent Configurations: Each website can have its own PHP version, web server settings, and resource limits.
Scalability: Containers can be independently moved across nodes in a clustered environment. Great for scaling up or migrating services.
Improved Security: If one website is compromised or attacked, it won’t spill over to the others, as they don’t share the same environment.
🧩 What Is an Addon Domain?
An addon domain is a secondary website that is added under an existing website’s hosting account. It shares the same container and Linux user as the main domain.
Characteristics of Addon Domains:
Shared Environment: All addon domains run under the same user account, using the same PHP version and resource pool.
File Structure: The addon domain typically lives in a subdirectory of the main domain, though it functions as a separate site to the outside world.
Security Risks: If one addon domain is compromised, an attacker may gain access to the other domains sharing the same environment.
Simpler Management: Useful for small, low-traffic sites or when isolation isn’t critical. Common for personal projects or staging sites.
🔐 Security Comparison
Feature | Containerised Website | Addon Domain |
|---|---|---|
Linux User Isolation | ✅ Yes | ❌ No |
Process Isolation | ✅ Full separation | ❌ Shared processes |
Cross-Site Risk | ❌ None | ⚠️ High |
Config Flexibility | ✅ Independent PHP versions | ❌ Shared settings |
Ideal Use Case | Production, high-risk apps, ecommerce | Hobby sites, low-traffic blogs |
💡 Use Case Examples
You should use a containerised website when…
You’re hosting client sites and need strong tenant isolation.
You need to run different PHP versions per site.
You’re concerned about security, such as for ecommerce or WordPress sites.
You might choose an addon domain when…
You’re adding a microsite or landing page that shares resources.
You’re running test/staging versions of the same app.
You’re managing a personal portfolio with several small static sites.
The decision between using a containerised website and an addon domain in Enhance comes down to a tradeoff between convenience and isolation.
For the majority of production use cases—especially when security, flexibility, or performance isolation is a concern—containerised websites are the clear winner. Addon domains, while simpler and lighter, are best reserved for low-risk, internal, or personal use.
With Enhance’s modular and container-first design, users gain the power of modern web hosting best practices, even on shared infrastructure. Understanding how these layers work behind the scenes helps you make smarter, safer decisions for your web projects.