Roadmap and Development Status

What Kuayle implements now, what it does not implement, and where proposed work is tracked. There are no promised dates or invented release milestones.

No invented release dates

Kuayle does not publish committed release dates or promise features against version numbers. Open issues and merged pull requests are the reliable record of proposed and completed work. This page documents the current product boundary rather than a sales roadmap.

  • Open issues describe proposed work
  • Pull requests and releases describe shipped work
  • No feature on this page has a guaranteed delivery date
  • Last reviewed: July 11, 2026

Available in v0.1.0

The current MVP includes the issue workflow, workspace roles, teams, custom statuses, comments, sub-issues, relations, labels, cycles, projects, saved views, notifications, public sharing, webhooks and GitHub integration.

  • Cycle burndown and velocity charts
  • Project issue list and Gantt view
  • GitHub activity linking and configurable status transitions
  • WebSocket updates and issue presence

Known gaps

These capabilities are not available in the current user interface. Their absence is documented so teams can evaluate Kuayle against present requirements rather than future assumptions.

  • Analytics dashboard: backend overview endpoints exist, but no dedicated UI
  • Data import and export workflows
  • Enterprise identity: SSO, SAML, SCIM and LDAP
  • GitLab and chat integrations

Dev Machines is a design, not a feature

TECHNICAL.md contains a design for disposable development environments connected to issues. The runtime container manager, authentication gateway and product UI described there are not implemented in the application.

  • Specification only
  • Not included in v0.1.0
  • No delivery date assigned

Follow or propose work

Use the GitHub repository to review active work, report a reproducible bug or propose a feature with a concrete use case.

  • GitHub: github.com/carbogninalberto/kuayle
  • Bug reports: include version, environment and reproduction steps
  • Feature requests: describe the workflow and expected outcome
  • Implementation status: verify merged code and release notes

Review Kuayle before you deploy it

Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.