Small service.
Direct line.
PacketGrid is run by one person. That is not a slogan or a pretend founder story; it is the practical reason the service can be direct, experimental and honest about its limits.
No support maze.
There is no giant operations team behind PacketGrid. When you send a question, it goes to the person building the service. That is useful when something needs a real answer rather than a scripted one.
Infrastructure is real, and finite.
PacketGrid is built around owned hardware and a small virtualisation stack rather than pretending to be a hyperscale cloud. That keeps the service under direct control, but it also means capacity is finite and maintenance sometimes matters more than marketing copy.
Free has trade-offs.
The Free plan allows one server. Starting or restarting a server can require the ad-supported cooldown, and inactive accounts have to log back in to keep their allocation. Premium removes those restrictions and currently allows up to 2 servers while the hosting system is being tested.
The product is being built in public.
The panel, provisioning work and infrastructure integration are moving in stages. The changelog is the useful source of truth for what is live. The status page is where published infrastructure information belongs.
Have a question?
Use the contact page. It goes to the person running PacketGrid.