Every site on one box, rendered as a city viewed from a jet. Health, certificates and remaining capacity readable in a single glance — no tailing six log files to find out what broke.
Installs read-only. It cannot change anything on your server until you explicitly turn writes on.
Cheap hardware means everything lands on the same server, and the tools stop scaling long before the box does.
You find out when a customer screenshots the browser warning, not when the renewal failed three weeks earlier.
Is there room for one more site? The honest answer is usually a guess about RAM you have never measured.
Most control panels want root and full write access on day one, on a server already running things you cannot afford to lose.
Every site is a house. Rooftop strobes blink faster the more urgent the problem, so a failing site is visible from across the room.
Issuance and auto-renewal, with expiry surfaced on the grid long before anything lapses.
Each constraint is computed from real numbers off your server, and the tightest one is reported. Every estimate shows its working.
Sites already on the box are adopted read-only. JetGrid monitors them and refuses to modify them, permanently, until you unprotect one by hand.
Point it at your own machine and it finds your projects, tells you which are running, and starts or stops them — local only, never production.
It ships unable to change anything. Writes are a decision you make, not a default you discover.
Every limit below is the one the server actually enforces.
No plans configured yet — run php artisan db:seed.