Roadmap
Themes, not dates. Veirox is pre-1.0 and iterating fast — these are the directions we're actively designing and building toward, not a committed timeline or a contractual promise. See the changelog for what's already shipped.
Enterprise readiness
SAML 2.0 and OIDC login against your identity provider (Okta, Azure AD, Google Workspace, OneLogin), an org-level "require SSO" enforcement toggle, and SCIM 2.0 provisioning so removing someone from your IdP revokes their Veirox access automatically — no manual offboarding step.
Enterprise readiness
Veirox already meters usage and cost per org. What's missing is the connective layer — correlating what you spent with what it achieved (incidents auto-resolved, tasks completed without a human, hours saved) — plus cross-org rollups for platform teams and MSPs managing many orgs at once.
Agent runtime
Today a project runs exactly one agent configuration for everything. Named Agent Profiles would let a project define several — a security-triage agent scoped to read-only log access, a deploy-gatekeeper with kubectl/helm and nothing else, a cost-optimization agent with billing tools — each with its own model, prompt, and permission bundle, selectable per task or chat.
Console UX
Extending the comments + session-resume work already shipped into its natural next surfaces: a direct "Resume" action from the session detail page, approval decisions that resume the session they gated, and "retry with a fix" on a failed task run — so acting on feedback doesn't mean starting over.
Console UX
Rounding out the command palette with the remaining searchable sources and slash-mode actions, plus a proper Kanban board for Stories (Jira-style units of work) — status columns, bulk actions, and list conventions consistent with the rest of the console.
Tell us which of these matters most for your team, or what's missing entirely.