DirhamGuard
DirhamHost add-on

Every customer uses exactly what they pay for.

DirhamGuard fences each hosting account inside real kernel limits for RAM, CPU and processes. One runaway site can never take down the whole server again.

Get DirhamGuard See how it works
Native to DirhamHost· No CloudLinux licence· Kernel-enforced, not guessed
dirhamguard · live
account: chargean Business plan
Memory0 / 1024 MB
CPU0 / 150 %
memory.max = 1073741824
memory.current = 171M
cpu.max = 150000 100000
The oversell problem

Shared servers fail the same way every time.

Without hard limits, the busiest account on the box quietly eats the memory and CPU that everyone else paid for. The fix isn't a bigger server, it's a fence around every account.

Without DirhamGuard

One bad neighbour, everyone suffers

A single WordPress import, a plugin loop, or a traffic spike consumes all free RAM. PHP starts killing workers, unrelated sites throw 502s, and you are firefighting at 2am with no way to see who caused it.

With DirhamGuard

Each account stays in its lane

Every account runs in its own kernel slice. When it hits the RAM or CPU ceiling of its plan, only that account slows, the rest of the server never notices. And you get a clean upsell: "upgrade for more."

What you get

Real limits, live usage, one flat price.

Hard RAM ceilings

Kernel MemoryMax per account. Over-limit memory is reclaimed from that account alone, never the whole box.

CPU quotas

A plan gets a fixed share of cores via CPUQuota. Spikes are throttled, not passed on to neighbours.

Process caps

TasksMax stops fork-bombs and stuck cron jobs from exhausting the server's process table.

Live usage in the panel

Real-time RAM and process usage per account, read straight from the kernel cgroup, no estimates.

Per-account overrides

Give one customer more RAM without changing their plan. Sell upgrades in one click, reversible any time.

Zero migration

Turn it on per account from the Host Panel. No downtime, no reinstall, no separate OS. Off is one click too.

Under the hood

Enforced by the Linux kernel, not a background script.

01

Its own slice

Each guarded account gets a dedicated systemd slice carrying the plan's memory, CPU and task limits.

02

Its own PHP

The account's PHP-FPM runs as its own service inside that slice, so its workers can only draw on its budget.

03

The kernel decides

cgroup v2 enforces every ceiling in real time. Hit the limit and only that account is throttled.

# the fence DirhamGuard writes for one account
[Slice] MemoryMax=1024M CPUQuota=150% TasksMax=200
# its php-fpm, pinned inside the slice
[Service] Slice=dh-<account>.slice
# live, straight from the kernel
$ cat memory.current → 171M / memory.max → 1024M
Pricing

One licence per server. Unlimited accounts.

Guard as many hosting accounts as your server holds, the price never changes with customer count.

Yearly saves 2 months

DirhamGuard

Per server · unlimited hosting accounts

AED 39 / server / month
Billed monthly. Cancel anytime.
  • Kernel RAM, CPU & process limits on every account
  • Live per-account usage in the Host Panel
  • Per-account overrides & one-click upgrades
  • Activates on your existing DirhamHost licence key
Add to my DirhamHost

Fleet

Running DirhamGuard on many servers?

Volume
Discounted licences for 5+ servers.
  • One dashboard, every server
  • Priority support & onboarding
Talk to us
Questions

Good to know

Is this a CloudLinux replacement? +

It solves the same core problem, stopping one account from starving the others, but it is native to DirhamHost. There is no separate operating system to install and no CloudLinux licence to buy. You enable it per account from the panel you already use.

Will turning it on cause downtime? +

No. Enabling DirhamGuard for an account moves its PHP into a limited slice in place. Existing sites keep serving; there is no reinstall and no data migration. Disabling is a single click and equally seamless.

How is it billed and activated? +

DirhamGuard is one licence per server, monthly or yearly, for unlimited hosting accounts on that server. After purchase it activates as a feature on your existing DirhamHost licence key, the Host Panel unlocks the DirhamGuard controls automatically on the next check-in.

What exactly is enforced? +

Memory (MemoryMax), CPU share (CPUQuota) and process count (TasksMax) per account, enforced by the Linux kernel through cgroup v2. Disk is capped separately by XFS quotas, which DirhamHost applies as standard.

Can I give one customer more without upgrading their plan? +

Yes. Set a per-account override for RAM, CPU or processes from the Host Panel. It applies instantly and is fully reversible, ideal for one-off upgrades or temporary headroom during a launch.

Ready when you are

Stop overselling by accident.

Activate DirhamGuard on your server and put a real fence around every account you host.

Add to my DirhamHost See the panel demo