The road ahead: payments, policy, and the shape of Ranbval v1
Roadmap · 5 min read · Published 2026-04-18 by Ahsan Tariq
What Ranbval looks like in the next two quarters — and the deliberate things we are refusing to build.
Product roadmaps tend to be wishlists. The Ranbval roadmap is not. Shipping next: subscription billing and seat management at twenty dollars a month per workspace; policy-as-code where a ranbval.policy.yaml committed next to your service syncs allowlists automatically; a first-class Node SDK mirror of the Python flows; incident mode with a one-click global revoke and scoped re-issue for the nights nobody wants. On the edge of the roadmap: mobile dashboard for approvals, partner integrations with observability platforms, hardware-backed key storage for enterprise tiers. What Ranbval will not build: a public plaintext export of secrets, even "for convenience"; a backend master recovery key held on your behalf; a marketing feature that hides a weakened trust model. Every unshipped feature is a feature we do not have to defend. For a security product that is not a lack of ambition — it is the ambition.
