Roadmap

Last updated 2 min read
Report issue

Roadmap#

What we're working on, what's next, and what's deliberately not on the list. Last updated 2026-05-14.

Caveat: this is a bootstrapped indie roadmap. Estimates are aspirations, not commitments. If a date matters to you contractually, talk to us.

Now (Q2 2026 — through end of June)#

  • Docs system live — docs.gritiva.com with AI drafter (PR #56)
  • Modern docs visual — Stripe/Vercel-style redesign (PR #59)
  • Agent crash-loop root-fix — PR #55
  • DRM live in production — Cloudflare + cloudflared + nginx-in-scope reconciler
  • Wave A VNet stable — overlay network primitive
  • Wave B vRouter/vSwitch/vLB shipped — behind feature flag, smoke tests in progress
  • Pricing live + first 10 paid customers (target end-Q2)
  • /auth/refresh endpoint — JWT renewal without re-login
  • Admin panel visual upgrade — match the docs site polish
  • Real /api/docs/tree proxy ✅ done in PR #62

Next (Q3 2026 — July through September)#

  • API reference auto-generation — keep /docs/api-reference in sync with OpenAPI spec
  • SDK in Python + TypeScript — wrap the REST API
  • Webhook delivery & retry guarantees — currently best-effort; need at-least-once
  • Multi-region failover for the hosted control plane
  • gmesh route reflector — break the >50-peers-per-VM ceiling (BGP-style topology)
  • SOC2 Type I observation period starts

Later (Q4 2026 — October through December)#

  • SAML / OIDC SSO for Enterprise plan
  • Self-hosted control plane GA — a customer can run their own panel.gritiva.com clone
  • Audit log export — push to S3 / Splunk / Datadog
  • Marketplace skeleton — community-contributed scope templates (think: Helm charts but lighter)

Deliberately not on the roadmap#

  • ❌ Kubernetes compatibility layer — different mental model; we're not building a K8s clone
  • ❌ Native autoscaling — runtimes that need HPA should use K8s
  • ❌ Multi-tenant orchestration of customer-of-customer apps — out of scope; we're infra, not PaaS
  • ❌ GUI workflow builder — this is infra, not Zapier
  • ❌ Built-in GitOps engine — use Argo / Flux; we don't want to compete there
  • ❌ Windows agent — possible eventually but no current demand justifies it

How we prioritize#

We rank by:

  1. Is it blocking a paying customer right now? — top of the list
  2. Does it remove a known footgun? — second
  3. Does it expand the addressable market? — third
  4. Is it cool to build? — last

Feedback#

We genuinely want to know what you'd add to this list. Email [email protected] or open a GitHub discussion.

If you're considering GritivaCore for production and a missing item would block your decision: please tell us. We've reordered the roadmap multiple times based on customer feedback. We'd rather build the right thing than the impressive thing.