Roadmap

This page describes Kessel’s Now / Next / Later roadmap — the current state of the platform, what’s actively in development, and what we’re working toward.

Links

• Internal Red Hat view — Jira roadmap plan (Red Hat SSO required)
• Contribute or track issues — project-kessel on GitHub

---

Now What’s available today

Features that are stable and available in the current release.

Inventory API Report, query, and track resources and their relationships via gRPC and HTTP APIs.

RBAC v2 Workspace-based tenancy with role bindings — map users or groups to roles scoped to a workspace or resource.

KSL Schema Language Define resource types and permissions in KSL. Compile to SpiceDB schema with the ksl compiler.

Multi-reporter resources Multiple services (reporters) can share ownership of a resource, each contributing their own representation.

SDKs Client libraries for Python, Go, TypeScript, Ruby, and Java.

CloudEvents via Kafka Resource changes are published as CloudEvents to Kafka, enabling event-driven integrations.

---

Next Actively in development

These are in progress and targeted for upcoming releases. Some may be available in preview.

Unified schema language

Today, resource attributes (JSON config) and permissions (KSL) use separate files. A single, unified schema language will combine both into one file with a single workflow.

RBAC Management API v2

Roles and workspaces are currently managed with temporary gRPCurl scripts. An RBAC management API (v2) will provide a proper interface for access grants and workspace management.

Runtime schema configuration

Schema is currently configured by editing files and restarting services. A configuration API will allow updating schema at runtime without downtime.

---

Later On the horizon

Longer-term investments. Scope and timing are subject to change.

Note

This section is updated periodically. For the most current view of planned work, see the Jira roadmap (Red Hat internal) or watch the project-kessel GitHub organization for new issues and milestones.

• History API — query the full change history of any resource over time
• Enhanced multi-tenancy primitives for complex B2B and sub-tenant hierarchies
• Additional SDK languages and improved SDK ergonomics

---

Suggest something

Have a use case or gap you’d like to see addressed? Open an RFE. Found a bug? Report it to the team.

Request a feature (RFE)

Report a bug