Intro

Metabase (the core product) has historically had a public roadmap, available on GitHub. It's been valuable for users and customers of different sizes. As we changed our processes and tools, it's gotten out of date, and we haven't replaced it.

But we still very much want to keep it: it reinforces our values of transparency towards our community, it gives prospective customers more confidence about whether to choose Metabase as their BI tool, it gives us additional surface area for input from our customers and community.

Goals

For us, a public roadmap should, in this order:

1. Articulate the high-level direction we're taking the product.
2. To help people understand the areas where we're investing.
3. Be a surface area for feedback.

Non-goals

• To give precise timing on granular pet features for different people.
• To share everything we're working on.
• To enable detailed conversations.

Ultimately, the public roadmap should be more like the Promised Land – exciting, worth waiting for – and not a land of promises – all talk, bound to lead to frustrations.

Website view

Metabase Public Roadmap