About Gritiva

Last updated 2 min read
Report issue

About Gritiva#

A short company page. The why, the who, the how we work.

Why this exists#

Most companies running between 2 and 50 VMs are stuck. They've outgrown "I'll just ssh into the box" but Kubernetes is overkill — too much cognitive load, too many moving parts, too expensive in engineer-time. They end up patching together Ansible scripts, half-finished dashboards, hand-rolled mesh setups, and 5-year-old shell scripts that "just need to be touched once a quarter."

We've been those teams. We built Gritiva for them.

What we believe#

  • Most teams will never run Kubernetes — and that's fine. They need a tool that fits them, not a smaller copy of what hyperscalers run.
  • Strong isolation should not require containers — Linux primitives (netns + cgroup) give you most of what containers do, with a tighter security model and lower overhead.
  • Mesh should be a primitive, not an add-on — every fleet needs cross-host networking; bolting it on later (sidecars, service meshes) adds operational complexity that compounds for years.
  • Source-available beats both proprietary and pure OSS — you can read everything we ship, fork it, audit it. Commercial use needs a paid plan; everything else is free.
  • Honesty about limits is a feature — see Why GritivaCore for the topics where we say "use Kubernetes instead."

How we work#

  • Bootstrapped — no outside funding, no investor pressure to grow at unsustainable rates
  • Small team — currently founder + (planned) first hire late 2026
  • Distributed — the founder is in [TBD]; the company is wherever the work happens
  • Public postmortems — when things break in production, we publish what happened: see /docs/postmortems-index
  • Source-available — the agent, docs system, and mesh daemon source live at github.com/mohammad2000/GritivaCore

How we make money#

Hosted control plane subscriptions (Pro and Enterprise plans). Self-hosted use is free. Consulting and migration help on the side. See Pricing.

We're cash-flow positive on a small base. We're not optimizing for valuation; we're optimizing for the next decade of running a sustainable company.

What we're not#

  • We are not a "next-gen" cloud
  • We are not a Kubernetes alternative for >100-node fleets
  • We are not a service mesh in the Istio / Linkerd sense
  • We are not a PaaS like Heroku — we don't manage your runtime, you do
  • We are not trying to disrupt anyone

Where to start#

Press & investor inquiries#