Feature requests
Tell us what to build next — and see what others are asking for.
Tell us what to build next, see what others are asking for, and follow a request from idea to release.
Most requested right now
Query plan advisor
Automatic index suggestions with measured impact from your own workload.
Scheduled branch refresh
Nightly reseeding of long-lived branches from an anonymised production snapshot.
Per-endpoint rate limit rules
Declarative limits with burst allowances configured alongside the route.
Terraform provider parity
Full coverage of branches, policies and spend caps in the official provider.
How a request becomes a feature
Submit the problem
Describe the situation and impact rather than the solution — it gives us room to find a better one.
Weekly triage
Product and engineering review new requests every Monday and set a status with a public comment.
Build and release
Requests move through Planned, In progress and Shipped, and everyone who voted gets notified at each change.
Statuses explained
| Status | Meaning | Typical time |
|---|---|---|
| Under review | Triaged, gathering demand and context | 1–4 weeks |
| Planned | Committed to a quarter on the roadmap | 1–2 quarters |
| In progress | Actively being built, beta flag likely available | 4–12 weeks |
| Shipped | Generally available, linked to the changelog entry | — |
| Not planned | Declined with a written explanation | — |
Post a request
Two minutes to write, and every submission gets a human response within a week.