Your agency just won a contract for three new WordPress sites, each for a different client. The clients want separate email accounts, individual SSL certificates and a clear invoice that reflects only the resources they use. You start to wonder whether a single-site host can cope, or if you need a platform that was built with multi-site work in mind.
TrueCore's plans are priced for small teams that run several sites under one roof. The Ember plan (£20 / mo) lets you host up to three sites, gives 40 GB of storage and includes PostgreSQL 16 databases. The Blaze plan (£40 / mo) expands the site limit to ten, adds 60 GB storage and upgrades backup frequency to every six hours. For agencies that need to run more sites, Inferno (£80 / mo) raises the limit to up to 20 sites and 100 GB storage. All plans ship with automatic SSL, DNS management, SSH access and the same PHP 8.3 + FPM stack.
Multi-site workflow and billing
When you host several client sites on a single account, you end up sharing the same resource pool unless the platform isolates each site. TrueCore uses flame-bubble containers and per-customer cgroup limits. The cgroup limits are hard, enforced by the Linux kernel. If a client's site tries to exceed its allocated RAM, the kernel kills the offending process immediately. The rest of your agency's sites stay up.
Because the limits are visible with a simple command, you can show clients exactly what they are paying for:
site info --client example-client
The output lists the current cgroup CPU share, memory ceiling and disk quota. You can copy that into an invoice, set a transparent price and avoid the guesswork that many resellers hide behind "soft limits".
The Ember and Blaze plans also include frequent backups via restic to encrypted Backblaze B2 buckets — 12-hourly on Ember and 6-hourly on Blaze. You can restore a single client's site without touching the others, which keeps billing disputes low and recovery times fast.
Why isolation matters for agencies
A bad client can break a whole server if the host only uses soft limits. Imagine one site runs a poorly coded plugin that spawns hundreds of PHP workers. On an oversold server the extra workers consume CPU and memory that belong to every other site. The result is a slow response for all your clients and a flood of support tickets.
TrueCore's kernel-enforced limits, described in our post about resource constraints, prevent that cascade. The kernel stops the runaway process before it can starve other cgroups. Because each site runs in its own flame-bubble container, network namespaces keep traffic separate, and flame-guardian bans abusive IPs at the firewall level without affecting legitimate visitors.
The watchdog service, flame-watchman, checks each service every five minutes. If a site's HTTP response stops returning a 200 status, the check is logged and an alert lands in our Discord channel. That early warning lets you step in before a client's issue spreads to the rest of your portfolio.
Practical steps to set up an agency workflow
- Choose the right plan - Start with Ember if you have up to three clients. Upgrade to Blaze when you cross ten sites or need tighter backup windows.
- Create a container per client - Use the control panel to add a new site. The system automatically provisions a new cgroup and a
pod-nginxprocess that only serves that domain. - Assign resources - The default limits match the plan. If a client needs more storage, you can increase their quota in the panel; the kernel will enforce the new ceiling instantly.
- Set up billing - Export the
site infooutput to CSV, add your markup and send an invoice. Because the limits are hard, you can justify any extra charge with concrete numbers. - Monitor health - Subscribe to the #alerts Discord channel. When flame-watchman records a failed check, you receive a message with the site name, so you can investigate before the client notices.
Trade-offs to be aware of
TrueCore does not offer cPanel or other heavyweight control panels. All management happens through our custom panel or the command line. If you rely on a GUI for every task, there is a learning curve. However, the lack of a third-party panel means fewer moving parts, lower overhead and a smaller attack surface.
Backups are stored off-site in encrypted B2 buckets. The restore process is manual - you run restic restore with the snapshot ID. This gives you full control but requires a bit of command-line familiarity. For most agencies the trade-off of transparency beats the convenience of a one-click restore button.
We do not provide 24/7 phone support. Our ticket system operates during business hours, with out-of-hours coverage for true incidents. Agencies that need round-the-clock phone help might need to supplement with their own monitoring.
Bottom line for small UK agencies
If you need to host several client sites, keep billing clear and protect each client from the missteps of another, a hosting provider must combine strict isolation with transparent tooling. TrueCore delivers that with kernel-enforced cgroup limits, per-site containers, frequent encrypted backups and a monitoring stack built in-house. The Ember, Blaze and Inferno plans scale cleanly from three sites up to 20 on Inferno while keeping costs predictable.
Pick the plan that matches your client count, use the site info command to prove resource allocation, and let flame-watchman alert you before a single bad site drags the whole agency down. That's the practical, no-fluff approach that lets small UK agencies focus on building websites, not fighting hosting outages.