kstack
kstack is the control plane — the panel your customers sign into to manage sites, mail, DNS, databases and machines. Priced by the number of nodes you run, not by the number of customers you serve.
Hosting, under control.
A Rust control plane and declarative node agents. You describe what should exist; each node reconciles itself towards it, every cycle, and reports what it actually found — so the box is never quietly different from what you asked for.
See plansConfiguration drift stops being your problem.
Most panels write a config file and hope. Delete an nginx config by hand and the agent puts it back. Rebuild a node from bare metal and it converges to the same state without anyone restoring anything.
The manifest this node should be running.
What is actually on the box right now.
The difference between the two.
Refuse a plan that would break something.
Atomic writes, with generation rollback.
What changed, and what it found.
One resource model, not five subsystems.
Websites, DNS zones, mailboxes, databases and virtual machines are rows of one resource type, so listing, quota and permission behaviour is written once instead of five times.
Per node. Never per account.
cPanel charges for every account you create, so growing costs you more for the same servers. kstack charges for the machines, and the accounts on them are yours.
Put one node up and break it on purpose.
The fastest way to judge kstack is to enrol a box, delete something it manages, and watch the next cycle put it back.
Book a walkthrough