OSS / About
Roadmap
What Aurora has shipped recently, what is in progress, and what is next. OSS work is prioritized by user impact.
Browse docs
Recently shipped
v1.0 — Core gateway
OpenAI /v1/chat/completions and /v1/embeddings, model routing and translation across providers, master-key auth, and the admin dashboard.
v1.5 — Providers + access control
Provider passthrough routes at /p/{provider}/* for native upstream APIs. Managed API keys with per-key provider/model policies and rate limits. Pricing overrides.
v2.0 — Policies + caching
OSS guardrails (system prompt, regex block, PII redact, length limit). Exact and semantic response cache. Workflow-based policy selection. Prometheus metrics.
v2.5 — Responses API + control plane
OpenAI /v1/responses and lifecycle endpoints. Editable per-model pricing with backups and restore. Native /v1/messages ingress for the Anthropic SDK. CLI Tools admin feature.
In progress
Q3 2026
- Intelligent routing — latency-aware, error-aware provider selection, with circuit-breaker fallback integrated.
- Broader provider support — Cohere, additional OpenAI-compatible providers, and a unified way to register any custom base URL.
- Prompt cache visibility — surface cached vs uncached token counts in the dashboard
Usagepage per request. - Guardrails hardening — response-side rules, custom rule types via the admin API, a more capable UI for rule editing.
- Full
/v1/conversationslifecycle — create, list, retrieve, and delete on par with the OpenAI Responses API.
Future
Q4 2026 and beyond
- Native MCP gateway integration in OSS — first-class Model Context Protocol routes with policy and audit integration.
- Embedded dashboard improvements — customizable views, exportable reports, saved filters, shareable links.
- Performance benchmarks and CI regression gates — published numbers per release, automated regression detection on PRs.
- Edge runtime — a smaller
aurora-edgebuild for Workers / Vercel / Cloudflare with a constrained feature set.
How to influence the roadmap
Open an issue
File a feature request with a use case. The most upvoted issues get prioritized.
Open link →
Join Discord
Real-time discussion in #feature-requests and #aurora-oss. Maintainers read every channel.
Open link →
Send a PR
The fastest way to ship a feature is to write it. See the Development guide for the workflow.
Open link →
Enterprise request
Enterprise-only features go through a separate queue. See the Enterprise Overview for details.
Open link →
Release cadence
- OSS minor versions ship roughly every 4-6 weeks.
- Patch versions ship as needed for bug fixes.
- Release notes are published in the Changelog and on the GitHub releases page.
- Enterprise follows its own release train and is versioned independently of OSS.
What does not belong here
- Bug fixes. They ship in the next patch and are tracked in the Changelog.
- Security patches. They ship immediately and get a CVE if applicable.
- Internal refactors. They ship in whichever release they happen to land in.
Related
- Changelog — every release, with diffs
- Contributing — how to send a PR
- Anonymous Heartbeat Telemetry — what we learn from deployments to inform prioritization