About Gritiva
Most teams running between a handful and a few dozen machines are stuck between ad-hoc SSH and Kubernetes. One does not scale; the other costs more engineer-time than it saves at that size. Gritiva is built for the range in between.
Why does Gritiva exist?
Teams in the 2-to-50-machine range typically end up maintaining a pile of Ansible playbooks, a half-finished dashboard, a hand-rolled mesh, and shell scripts nobody wants to touch. Every piece works; the combination is nobody's job. Gritiva replaces that assembly with one control plane.
What does Gritiva believe about infrastructure?
- Most teams will never run Kubernetes, and that is a reasonable choice rather than a failure. They need a tool shaped for them, not a smaller copy of what hyperscalers run.
- Strong isolation should not require a container runtime. Linux namespaces and cgroups already provide it; a daemon holding root is a cost, not a feature.
- Connectivity is a primitive, not an add-on. Every fleet eventually needs cross-host networking. Bolting it on later compounds operational complexity for years.
- Being honest about limits is a feature. The comparison pages name the cases where another tool is the better answer, because a claim that survives scrutiny is worth more than one that does not.
What is Gritiva not?
It is not a cloud provider, not a Kubernetes replacement for fleets above roughly fifty machines, not a service mesh in the Istio sense, and not a platform-as-a-service that manages your application runtime. Those boundaries are deliberate.
The comparison pages go through each of these in detail.
What happens when something breaks?
Production incidents get written up and published, including the ones that were embarrassing. The postmortems are in the public documentation with root causes, timelines and the specific changes made so the same class of failure cannot recur.
Read them: Postmortems.
Frequently asked questions
- How does Gritiva make money?
- Subscriptions to the hosted control plane. Self-hosting the control plane is free. See the pricing page for the plans.
- Can I read the source?
- Gritiva is distributed under a source-available, non-commercial licence. Contact us for access arrangements.
- Who is Gritiva for?
- Teams operating roughly 2 to 50 machines — home labs, agencies, small product teams, and anyone maintaining infrastructure spread across more than one provider or network.
Last updated