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. 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 websites are sandboxed from each other, a major security benefit.
- Process Separation: PHP processes, cron jobs, and file permissions are completely separate. A compromised site cannot 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 or migrating services.
- Improved Security: If one website is compromised, it won’t affect the others, as they don’t share the same environment.
🧩 What Is an Addon Domain?
An addon domain is a secondary website 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 externally.
- 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
When to Use a Containerised Website:
- Hosting client sites needing strong tenant isolation.
- Running different PHP versions per site.
- Concerned about security, such as for ecommerce or WordPress sites.
When to Use an Addon Domain:
- Adding a microsite or landing page that shares resources.
- Running test/staging versions of the same app.
- Managing a personal portfolio with several small static sites.
The decision between a containerised website and an addon domain in Enhance comes down to a tradeoff between convenience and isolation.
For most 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, 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.
Ready to Get Started?
Let’s put our performance to the test! We’ll handle a FREE test migration for you, so you can experience the speed and optimisation firsthand. Get started today and see the results for yourself!
