15 Best Public Roadmap Examples for SaaS in 2026

Implementing a public roadmap is slowly becoming the norm for many SaaS companies in 2026.

It's an effortless way to communicate your product vision, manage customer expectations, and keep users in the loop about the progress of ongoing developments.

In this blog post, we will give you an easily digestible overview of 15 real-world public roadmap examples, from smaller startups to large enterprises like Microsoft, GitHub, and others.

We will also give you a simple guide about the best way to set up your very own public product roadmap in just a few minutes.

But first, let's quickly cover what public roadmaps even are. 👇

What is a public roadmap?

🗺️ A public roadmap shows the future plans and direction of a company's product transparently to everyone. It's usually in a Kanban layout, outlining what's coming next, what's currently being worked on, and what's recently been launched.

Rather than keeping the roadmap private as usual, a public product roadmap is made fully publicly visible to all users, potential customers, and other key stakeholders.

The main purpose of a public roadmap is to:

• Provide transparency and communicate the company's product vision
• Engage users by gathering feedback
• Align development efforts with customer needs
• Build trust by being open about upcoming features and timelines

So, it's not just a list of upcoming features. It shows that you're constantly improving your product and listening to the customers. The most important part is that users can see what you've planned and provide valuable feedback, making them feel part of the journey.

It's how modern companies show they care about their users' needs and manage their expectations.

✨ Looking to create a public roadmap for your product? Check out Featurebase →

15 best public roadmap examples for SaaS companies

Now that we have a great overview of what a public roadmap is and why they're used in the first place, let's dive into real-world examples to give you a good understanding of different approaches. 🌍

Here's a quick look at all 15, the tool behind each one, and what makes it worth copying:

1. Featurebase✨

Created with: Featurebase (that's us 👋)

We run our feedback forum, public roadmap, and changelog from a single platform, so a request can travel from idea to vote to "in progress" to shipped without ever leaving one place. When a feature's status changes, everyone who upvoted it is notified automatically by email.

Takeaway: We use our own product to collect feedback, publish product updates, and show a public roadmap to our users. We are shipping new features literally every week, so it's very important to keep our customers in the loop about what's new and what's next. Keeping feedback, roadmap, and changelog connected is what lets us close the loop on every request instead of letting ideas disappear into a backlog.

Pricing: Free plan with unlimited suggestions, and paid plans start at $29/seat/month.

Featurebase public roadmap: Featurebase roadmap

2. Rolla

Created with: Featurebase

Rolla runs its entire feedback and roadmap process in one public view, so the whole lifecycle of a feature - from first request to shipped - is visible to users in a single place. Ideas are open for voting, and each one carries a timeline so customers always know roughly when something is coming.

Takeaway: Rolla is an amazing example of how to build a transparent company culture with a public product roadmap. Users see that ideas from other people get implemented and that the company deeply cares about their experience.

The entire lifecycle of features being developed can be followed in a single place. Customers constantly leave feedback and vote on the most valuable ideas. Each idea also has a timeline to avoid questions like "When is X feature finally coming?". The lesson here is that pairing visible timelines with open voting kills the most common roadmap question before it's ever asked.

Pricing: Featurebase has a free plan, with paid plans from $29/seat/month.

Rolla public roadmap: Rolla roadmap

3. GitHub

Created with: GitHub Projects

GitHub, the code-hosting platform used by millions of developers, builds its roadmap natively inside GitHub Projects. Instead of a status-based Kanban board, it's organized by quarter, and every item is tagged by release stage (GA, Public Preview) and plan tier (Free, Team, Enterprise) so developers can see exactly what's coming, when, and whether it applies to them.

Takeaway: GitHub's public roadmap is an interactive view that reflects their commitment to open-source and community-driven development. It allows users to see upcoming changes, contribute ideas, and track the development status of different features, creating a strong sense of community involvement.

Status setup: Rather than a simple Kanban board, GitHub organizes everything by quarter and tags each item by release stage, which suits their technical audience that needs precision over simplicity. The takeaway isn't to copy this level of detail - it's to match your roadmap's granularity to what your users actually need to plan around.

Pricing: Free - GitHub Projects is built into GitHub at no extra cost.

GitHub public roadmap: GitHub roadmap

4. Atlassian Cloud

Created with: In-house (Atlassian)

Atlassian, the company behind Jira, Confluence, and Trello, built its own roadmap and split it into separate Cloud and Data Center views. With so many products under one roof, it leans on filters - product, category, status, and timeframe - plus lots of white space so the page never feels overwhelming.

Takeaway: The Atlassian Cloud Roadmap showcases how a large enterprise can implement a public roadmap effectively. It's a simple, easy-to-understand list that provides an overview of upcoming features, their expected release dates, and the products they will impact. For a large catalog, strong filtering is what keeps a roadmap usable rather than turning it into an unreadable wall of cards.

Pricing: Built in-house, so it isn't a roadmap product you can buy separately.

Atlassian public roadmap: Atlassian roadmap

5. Ahrefs

Created with: Canny

Ahrefs, the well-known SEO toolset, runs its roadmap on Canny and organizes it around its many product modules so users can jump straight to the area they care about - Site Explorer, Keywords Explorer, and so on - rather than scrolling through everything at once.

Takeaway: Since Ahrefs has a lot of different product modules, their product roadmap is focused on helping users sort & find the part they are most interested in. It's quite easy to use and lets people vote on what features they want to see next. This way, Ahrefs ensures they're building what their users really want. When your product spans several distinct areas, grouping the roadmap by module is what stops power users from bouncing.

Pricing: Canny has a free plan, with paid plans from $19/month.

Ahrefs public roadmap: Ahrefs roadmap (ahrefs.canny.io)

6. Unity

Created with: Productboard

Unity, the real-time 3D and game-engine company, embeds its roadmap directly on its own site and uses top-level categories so users can move between its different products and platforms. It's a read-only view - there's no voting or feedback collection - but it does the job of keeping a large user base informed.

Takeaway: Unity offers a clear roadmap that's embedded on their website. Although they're not collecting customer feedback or upvotes with it, it's a simple way to keep users updated with their plans. Notice how it has categories on top to let users navigate between different products. Even a one-way roadmap earns trust - though adding voting would turn that visibility into a feedback loop.

Pricing: Productboard starts at $15/maker/month (billed annually), with Enterprise pricing on request.

Unity public roadmap: Unity roadmap

7. Airtable

Created with: Airtable

Airtable, the no-code database and app builder, runs its public roadmap inside Airtable itself - turning its own product into the demo. It isn't purpose-built for roadmapping, but a well-structured base with clear views does the job and doubles as proof of what the tool can do.

Takeaway: Airtable uses its platform to showcase its roadmap as well, demonstrating the versatility and power of Airtable. Although it's not entirely optimized for building public roadmaps, it's still a great example of a simple roadmap that is executed well. If you already live in a flexible tool, you can stand up a serviceable roadmap there - just know you'll trade voting and notifications for that convenience.

Pricing: Airtable has a free plan, with paid plans from $20/user/month.

Airtable public roadmap: Airtable roadmap

8. Rust

Created with: Nolt

The Rust programming language project runs its roadmap on Nolt and frames it around upcoming releases rather than a Kanban board. It's styled to match Rust's brand, which makes a community-driven open-source project feel polished and intentional.

Takeaway: Rust's roadmap is a good example of a straightforward, easy-to-follow plan that's nicely customized to fit their brand. Although it's not in the conventional Kanban format, it gives a great overview of the upcoming releases. A release-oriented layout works well when your audience cares more about "what's in the next version" than about which exact stage each item sits in.

Pricing: Nolt starts at $29/month per board.

Rust product roadmap: Rust roadmap (rust.nolt.io)

9. CoffeeCup

Created with: Featurebase

CoffeeCup keeps its roadmap deliberately minimal, and its most interesting choice is hiding vote counts until after you've cast your own. That small tweak changes the psychology of voting on the whole board.

Takeaway: CoffeeCup has a neat, minimalistic product roadmap. It is worth highlighting because it also features upvoting, but the count is hidden before voting the ideas. This is an effective way to reduce herd behavior, where users tend to upvote ideas that already have many votes. Hiding the count means each vote reflects what a user actually wants, not what's already popular - which gives you cleaner prioritization signal.

Pricing: Featurebase has a free plan, with paid plans from $29/seat/month.

CoffeeCup public roadmap: CoffeeCup roadmap

10. Trello

Created with: Trello

Trello, the Kanban board tool, runs its public roadmap on its own boards using simple lists like ideas, doing, and shipped. Cards support comments and voting, and each one has a shareable link - a natural fit for a product whose whole job is organizing work into columns.

Takeaway: Trello uses its own tool to show the roadmap. This approach is like Airtable's - using their product to showcase future plans. It's a smart way to show the capabilities of Trello while keeping users informed. Dogfooding your own product as the roadmap is a quiet but effective demo - users see the tool working before they ever sign up.

Pricing: Trello has a free plan, with paid plans from $5/user/month.

Trello public roadmap: Trello roadmap

11. Microsoft 365

Created with: In-house (Microsoft)

Microsoft's 365 roadmap covers an enormous product catalog, so it leans heavily on filters (product, platform, release date, cloud instance) and gives every feature a unique ID for easy reference. There's no voting, but a "Using this roadmap" guide helps users navigate the sheer volume.

Takeaway: Microsoft's public roadmap highlights everything the company is working on and displays when these features can be expected. It could be a good solution for larger enterprises that have fully adopted Microsoft's ecosystem, but it's quite cluttered and hard to navigate compared to modern solutions.

Status setup: Microsoft keeps it to three plain stages - in development, rolling out, and launched - which makes a huge product catalog easier to parse at a glance. The flip side is a cautionary one: at this scale a roadmap can tip into overwhelming, which is exactly why most SaaS teams are better off keeping theirs focused.

Pricing: Built in-house as part of Microsoft 365, not a standalone roadmap tool.

Microsoft public roadmap: Microsoft roadmap

12. Buffer

Created with: FeatureOS

Buffer, the social media management platform, is famous for its transparency culture, and its roadmap reflects that - users are involved across the whole planning process through open suggestions and voting. It fits a company that publishes everything from salaries to revenue.

Takeaway: Buffer has a clear and interactive public roadmap that involves users in the entire planning process. Similarly to other examples in this list, it also has feature suggestions and voting functionalities. When transparency is already part of your brand, an open roadmap isn't a risk - it's the natural extension of how you already operate.

Pricing: FeatureOS has a free plan, with paid plans from $60/month.

Buffer public roadmap: Buffer roadmap

13. Loom

Created with: Productboard

Loom, the async video messaging tool now part of Atlassian, keeps a clean roadmap on Productboard that's organized by product area. Feature ideas come with proper descriptions rather than one-line titles, which gives users enough context to vote meaningfully.

Takeaway: Loom (now part of Atlassian) has a simple product roadmap showing their plans for different features. It's a straightforward solution, but it could benefit from a little more of their own branding. Writing a real description for each item, instead of a bare title, is a small effort that noticeably improves the quality of the votes you get back.

Pricing: Productboard starts at $15/maker/month (billed annually).

Loom public roadmap: Loom roadmap (hosted on Productboard)

14. SE Ranking

Created with: In-house ('Share Your Wish' portal)

SE Ranking, an all-in-one SEO platform, frames its roadmap around a "Share Your Wish" portal where users submit and vote on ideas. Those wishes feed directly into the features that show up in its monthly product updates, creating a tight loop between request and release.

Takeaway: SE Ranking has a comprehensive suite of SEO tools, so their roadmap strategy focuses on direct user feedback through a 'Share Your Wish' portal. It allows users to submit and vote on ideas, which then directly influence the features listed in their monthly updates. This way, SE Ranking ensures their development cycle is perfectly aligned with the needs of their agency and business clients. Naming the portal something inviting - "Share Your Wish" rather than "Feature Requests" - is a small branding move that lowers the barrier to contributing.

Pricing: Built in-house through SE Ranking's own portal, not a separate product.

SE Ranking public roadmap: SE Ranking roadmap

15. Friends & Fables

Created with: Featurebase

Friends & Fables, an AI-powered tabletop role-playing platform, runs a fully branded roadmap that feels like part of the product rather than a bolted-on portal. Idea voting is front and center, so the features players care about most rise to the top.

Takeaway: Gaming companies know the value of keeping users engaged and updated with their plans. Friends & Fables' public roadmap is customized to be fully in their own brand. It also supports idea voting, so everything players want rises to the top. For community-driven products, matching the roadmap to your brand keeps the experience immersive and signals that feedback is a first-class part of the journey.

Pricing: Featurebase has a free plan, with paid plans from $29/seat/month.

Friends & Fables public roadmap: F&F roadmap

Why should you have a public roadmap?

Still unsure if a public roadmap is right for you? Here are 7 ways public roadmaps benefit your company:

• Builds customer trust and loyalty
  When customers see your future plans, they feel more connected and invested in your product. This transparency builds trust, and a trusting customer is a loyal customer.
• Captures customer feedback
  No one wants to send feedback into a black hole. Public roadmaps invite suggestions, turning passive users into active community members. This engagement not only improves your product but also creates a sense of belonging among your users.
• Drives product development
  By showcasing what's coming next, you align your team's efforts with customer expectations. It helps in prioritizing features that matter most to your users, ensuring your development is on the right track.
• Manages expectations
  A clear roadmap sets realistic expectations about your product's growth and updates. It helps in managing customer expectations and reduces uncertainty about the product's future.
• Differentiates your brand
  In crowded markets, a public roadmap can be a huge differentiator. It shows that you value openness and customer feedback - qualities that can set you apart from competitors.
• Increases accountability
  Public roadmaps hold you accountable to your plans, ensuring that you're constantly making progress and updating your product.
• Attracts potential customers and investors
  A well-structured roadmap can be a powerful tool for attracting new customers and investors. It showcases your vision, the direction of your product, and your commitment to growth.

For more, read our blog: Should Your Company Have a Public Roadmap →

In short, a public roadmap is much more than your list of features with timelines. It's a strategic asset that can help you build a loyal community, enhance product success, and elevate your brand's reputation. We've experienced it firsthand.

How to create a public roadmap?

Good news! It's easier than you think. As you've seen from the 15 examples above, there are many ways to approach this.

Let's break it down into simple steps:

1. Pick your style: Reflect on the examples you've seen. Do you like a simple list or something more visual? Your roadmap's style should match your company's personality and be easy for your audience to understand.
2. Choose your statuses: The examples above lean on a few simple columns to show progress. Three to four statuses is the sweet spot for most products, with schemes like Under Consideration, Planned, In Progress, and Shipped mapping cleanly to how users think about development. Keep the language plain unless your audience is technical.
3. Define your goals: What do you want to achieve with your public roadmap? Is it for gathering feedback, setting clear expectations, or showcasing your future plans? Your goals will guide the content and design of your roadmap.
4. Collect insights: Your roadmap should be based on what your users need and want. Use surveys, feedback tools, or direct communication to gather their insights. Remember, this roadmap is as much for them as it is for you.
5. Set priorities: You can't tackle everything at once. Prioritize features and updates based on user demand and strategic value. This helps in creating a focused and realistic roadmap. For a more in-depth guide about prioritization, check out our guide about planning your product roadmap effectively.
6. Keep it dynamic: Update your roadmap regularly. New challenges constantly arise, and feedback can shift priorities. A dynamic roadmap shows that you're responsive and adaptable.
7. Be open about changes: If you need to shift priorities or delay a feature, communicate it openly. Honesty in your roadmap strengthens trust with your users.
8. Encourage interaction: Allow users to comment, give feedback, or even vote on features. This engagement makes them feel valued and involved in your product's journey.
9. Choose the right tool: There are a variety of public roadmap tools available for creating roadmaps. Pick one that suits your needs. Consider the tool's ease of use, customization options, and integration with your other tools.

Conclusion

The bottom line is that public roadmaps are a lot more than just planning tools for SaaS companies. They're a dynamic way to engage with users and build trust.

While the worry of idea theft exists, remember that the most sensitive plans can be kept internal. The positives of transparency, user engagement, and the valuable feedback you gain often outweigh any risks.

Featurebase allows you to create your own public roadmap in seconds. It's fully customizable to align with your brand and lets users provide feedback and vote on ideas. When you update the status of an idea, all upvoters are automatically notified via email, ensuring that relevant users stay informed about their requests. 💫

We have a Free plan with unlimited suggestions and access to all modules, so there's no downside to trying it. 👇

✨ Create internal & public roadmaps with Featurebase for free →

More reading:

• Top 7 Public Roadmap Tools for SaaS Companies →
• Should Your Company Have a Public Roadmap? →
• A Simple 6-Step Guide to Plan & Prioritize Your Product Roadmap Effectively →
• The Best Product Roadmap Examples for SaaS Startups →

FAQs

What is a public product roadmap?

A public roadmap is a strategic tool that shows the future plans and direction of a company's product transparently to everyone. It's usually in a Kanban layout, outlining what's coming next, what's currently being worked on, and what's recently been launched. Rather than keeping the roadmap private, it's made fully publicly visible to all users, potential customers, and other key stakeholders.

How does a public roadmap benefit SaaS companies and their users?

For SaaS companies, a public roadmap is key to building trust and maintaining open communication with their user base. It allows customers to see what new features or improvements are coming, fostering a sense of involvement and anticipation. For the company, it's a way to gather valuable feedback, prioritize development based on user needs, and demonstrate commitment to continuous improvement.

What statuses should you use on a public roadmap?

Keep it simple. Three to four statuses is the sweet spot for most products, enough to show meaningful progress without creating ambiguity. A common scheme that works well is Under Consideration, Planned, In Progress, and Shipped. Avoid overly technical labels unless your audience is developers, since terms like "In Progress" and "Shipped" are universally understood.

What's the difference between a public roadmap and a changelog?

A public roadmap is forward-looking and shows what's coming next, while a changelog is backward-looking and shows what has already shipped. You really need both: a roadmap without a changelog leaves users wondering if anything gets built, and a changelog without a roadmap gives no sense of direction. Featurebase combines a roadmap and a changelog in one place so users can move naturally between what's next and what's new.

What are the best practices for creating an effective public roadmap?

Creating an effective public roadmap comes down to a few habits: prioritize transparency by being clear about your goals and timelines, gather user feedback regularly so the roadmap reflects real customer needs, update it often to keep it current, and encourage interaction through votes and comments. Above all, manage expectations honestly - it's better to under-promise on timelines than to lose trust by missing them.