Roadmap & Known Issues
Relevant source files
The following files were used as context for generating this wiki page:
This page outlines the current development status, planned features, and identified technical limitations of the Barekey vault manager. Barekey is currently in an early scaffold state where core organizational and project creation features are functional, but advanced vault operations and security controls are still under active development.
Sources: AGENTS.md:7-10, pkg/ui/src/pages/o/[org]/overview/page.tsx:94-118
Planned Features & Roadmap
The project roadmap is divided into core system improvements, infrastructure additions, and UI enhancements. Several high-level capabilities have been identified as upcoming priorities to transition the project from its current MVP state to a production-ready vault manager.
Key Infrastructure & Security Roadmap
The following table summarizes significant infrastructure milestones planned for the project:
| Feature | Description | Status |
|---|---|---|
| Client-side Encryption | Transitioning from server-side (Convex) encryption to full client-side encryption. | Planned |
| Key Rotation | Automated and manual Project DEK rotation and secret re-encryption logic. | Planned |
| Autumn Integration | Implementation of the Autumn payment processing layer. | Planned |
| SDK & CLI Support | HTTP endpoints in pkg/convex/http.ts to support external developer tools. | Planned |
| Audit Logs | Comprehensive trail for project creation, secret changes, and membership updates. | Scaffolded |
Sources: AGENTS.md:15-18, AGENTS.md:46-50, AGENTS.md:65-68, pkg/ui/src/pages/o/[org]/overview/page.tsx:94-118
Project-Level Roadmap
Individual projects within Barekey are slated for specific enhancements related to secret lifecycle management and visibility.
This diagram represents the progression of project-level features from current initialization to advanced lifecycle management.
Sources: pkg/ui/src/pages/o/[org]/project/[projectSlug]/overview/page.tsx:66-77
Identified Technical Issues & Limitations
Several known issues and limitations exist within the current architecture, ranging from routing collisions to scaffolded UI elements that lack backend implementation.
Routing & Slug Collisions
A critical known issue involves the potential for static routes to collide with dynamic organization slugs. Because system pages like /o/new and /o/select are static, any organization created with the slug "new" or "select" becomes unreachable at its canonical path.
- Impact: Users can inadvertently break navigation by choosing reserved slugs.
- Mitigation Plan: Implement slug reservation at creation/rename time and validate input against a list of system paths.
Sources: TODO.md:1-15
Scaffolded Features (Non-Functional)
Many UI components are currently "scaffolded," meaning they appear in the interface but are not yet backed by operational logic or live data.
- Usage Tracking: The Organization Overview displays cards for "Static Requests," "Dynamic Requests," and "Storage," but these currently show "0" and are marked with a hint "Usage limits tracking soon."
- Audit Feed: The audit log panel on the organization overview is a placeholder that describes future functionality rather than displaying real events.
- Encryption Controls: The project settings page includes an "Encryption controls" section that identifies envelope encryption but notes that rotation controls are "coming next."
Sources: pkg/ui/src/pages/o/[org]/overview/page.tsx:50-75, pkg/ui/src/pages/o/[org]/overview/page.tsx:106-118, pkg/ui/src/pages/o/[org]/project/[projectSlug]/settings/page.tsx:327-340
Billing & Usage Architecture
The billing system is currently defined in the UI but lacks a backend implementation for enforcement and payment processing.
Planned Billing Tiers
Barekey intends to offer three tiers: Free, Pro, and Max. Each tier defines specific limits for static requests, dynamic requests, and storage.
The diagram shows the tiered structure and the planned integration with Autumn for payment handling.
Sources: pkg/ui/src/pages/o/[org]/billing/page.tsx:16-75
Known Billing Constraints
- Single Org Limit: The Free plan is explicitly intended to be limited to one organization per user.
- Overage Logic: While the UI allows toggling "With overages," the logic for billing these monthly regardless of the base billing interval (annually vs monthly) is not yet implemented.
Sources: pkg/ui/src/pages/o/[org]/billing/page.tsx:216-225
Summary
Barekey is moving from a structural scaffold toward a feature-complete secret management platform. Current priorities include securing the vault with client-side encryption, resolving routing vulnerabilities regarding reserved slugs, and replacing scaffolded UI elements (Usage metrics, Audit logs, and Billing) with live backend integrations. Developers should be aware that many current visual indicators for usage and security rotation are placeholders for upcoming releases.