What Is the Roadmap for Kaneo? A Developer's Guide to the Live Feature Timeline

Kaneo's roadmap is a live, public page hosted at https://kaneo.app/roadmap that tracks upcoming features and enhancements, directly linked from the project's Hero component and documented in the repository's changelog.

The usekaneo/kaneo repository maintains this roadmap externally while integrating it into the web interface and tracking progress through internal documentation. Understanding how this roadmap connects to the codebase helps contributors and users anticipate architectural changes across the pnpm monorepo.

Where to Find the Official Roadmap for Kaneo

The canonical roadmap for Kaneo lives outside the repository at https://kaneo.app/roadmap. This external page serves as the single source of truth for product direction and upcoming capabilities.

According to the source code analysis, the roadmap link was formally integrated into the UI in commit c62925f, which added a "live roadmap" reference to the Hero component. The main README.md also points to this URL within its documentation section, ensuring users can easily navigate from the repository to the public timeline.

How the Roadmap Integrates with the Kaneo Codebase

While the roadmap content itself is not stored in the repository, the usekaneo/kaneo codebase contains the infrastructure that references and supports it.

Frontend Integration in the Hero Component

The web application displays a direct link to the roadmap through its Hero component. Based on the repository structure, this UI element is located in the frontend application package:

• File: apps/web/src/components/Hero.tsx (or equivalent Hero component)
• Function: Renders a button or link pointing to https://kaneo.app/roadmap
• Commit: Added in c62925f to provide immediate access from the landing page

This integration ensures that every deployment of the Kaneo web app surfaces the current roadmap to end users without requiring manual updates to the codebase.

Tracking Progress via the Changelog

The repository's CHANGELOG.md provides the technical counterpart to the public roadmap. Recent releases such as v2.15.0 document specific implementations that later appear on the roadmap, including:

• Billing system improvements
• Internationalization (i18n) expansions
• MCP (Model Context Protocol) server enhancements

By cross-referencing the changelog with the live roadmap, developers can trace when specific features transitioned from planned status to shipped code.

Technical Architecture Supporting the Roadmap

Kaneo is built as a pnpm monorepo managed by TurboRepo, structured to accommodate the large-scale changes typically listed on the roadmap. The architecture divides functionality across distinct packages that correspond to roadmap categories:

• apps/api: Hono-based backend API handling billing, authentication, and MCP server logic
• apps/web: React frontend containing the Hero component and roadmap links
• packages/*: Shared libraries and utilities supporting cross-cutting concerns

When the roadmap indicates infrastructure changes—such as implementing Redis-based WebSocket Pub/Sub or database schema migrations—these modifications target specific directories within this monorepo structure.

Programmatically Accessing Roadmap Data

Developers can fetch the live roadmap content for custom integrations or CLI tools:

// Fetch the live roadmap page (Node.js with undici)
import { fetch } from "undici";

async function fetchRoadmap() {
  const response = await fetch("https://kaneo.app/roadmap");
  if (!response.ok) {
    throw new Error(`Failed to fetch: ${response.status}`);
  }
  const html = await response.text();
  return html;
}

// Usage
fetchRoadmap()
  .then(content => console.log("Roadmap loaded:", content.length, "bytes"))
  .catch(console.error);

For React applications linking to the roadmap, implement a secure external link component:

// React component for roadmap navigation
import { Link } from "react-router-dom";

export function RoadmapLink() {
  return (
    <Link
      to="https://kaneo.app/roadmap"
      target="_blank"
      rel="noopener noreferrer"
      className="btn btn-primary"
    >
      View Roadmap
    </Link>
  );
}

Summary

• The official roadmap for Kaneo is hosted externally at https://kaneo.app/roadmap and referenced throughout the repository.
• The Hero component in apps/web/src/components/Hero.tsx provides UI integration, added in commit c62925f.
• Technical progress is tracked in CHANGELOG.md, which documents shipped features corresponding to roadmap items.
• The pnpm monorepo architecture (using TurboRepo) organizes code into apps/api, apps/web, and packages/* to support roadmap initiatives.
• Developers can programmatically access the roadmap via standard HTTP requests for custom tooling.

Frequently Asked Questions

Where is the Kaneo roadmap officially published?

The Kaneo roadmap is published as a live page at https://kaneo.app/roadmap. This external site is maintained by the Kaneo team and is linked directly from the repository's README and the web application's Hero component.

How can I track which roadmap features have been implemented?

Check the CHANGELOG.md file in the root of the usekaneo/kaneo repository. This file maintains a chronological record of all releases, with recent versions like v2.15.0 documenting specific features such as billing improvements and MCP enhancements that correspond to roadmap items.

Is the roadmap content stored in the GitHub repository?

No, the roadmap content itself is not stored in the repository. Instead, the codebase contains links and references to the external roadmap URL, along with the architectural infrastructure in apps/api, apps/web, and packages/* that implements the features described on the live roadmap.

What technology stack supports the roadmap features?

The roadmap features are implemented across a pnpm monorepo using TurboRepo. The stack includes a Hono API backend (apps/api), a React web frontend (apps/web), and shared packages (packages/*), allowing the team to develop complex features like Redis-based WebSocket support and database migrations as indicated on the roadmap.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}