Product roadmap software your customers can follow.

Product roadmap software shows what a product team plans to build next. Internal roadmap tools focus on strategy and timelines for your own team; a public roadmap shows customers which requests are planned, in progress and released, and lets them vote on what they need. Gleap's roadmap is the public kind and part of the feedback portal: customers vote in the widget or on the portal, your team moves requests through the lanes, and subscribers are told when the work ships.

Requests arrive from the widget, the portal, support tickets and your team. Each one carries votes, comments, tags, linked tickets and a score. New requests wait in Needs your review until your team accepts them, or, on Team and up, Kai Copilot decides under your rules. Your team moves them through the roadmap lanes and posts updates that go to the subscribers.

Requested, Planned, In progress and Released on the public board by default, with Ideas as the hidden intake list (shown as Needs your review in the dashboard) and a hidden Closed lane. You can rename lanes, add your own and hide the ones customers should not see; the roadmap shows the visible lanes in your order.

No. Votes are one input. Kai Copilot merges duplicate requests, links each to the customers who asked and drafts the changelog when it ships, next to the votes. Your team decides what moves to Planned.

You set who can upvote, submit, read and write comments, each separately. Guests enter an email address to vote. Voting subscribes the customer to updates on that request.

An update posted in the request is emailed to everyone who voted, the roadmap moves the request to Released, and a published changelog reaches changelog subscribers by email and as an in-app pop-up. See release notes and changelogs.

Yes. The feedback portal runs on a custom domain with your logo, favicon and navigation links, and can be embedded in your site. You decide whether search engines index it; turning indexing off does not make a public link private.

Yes. A teammate links a ticket to a request from the ticket sidebar, which adds the customer's vote. From Team, Kai Support does this for tickets it investigates: when it concludes a ticket is a feature request, it adds the customer's vote to the matching request.

Yes. A new request is compared by meaning against the existing ones. The widget shows similar requests before submitting, and the dashboard names the match in the create dialog with a button to open the existing request.

No. Requests, voting, comments, roadmap lanes and changelogs are platform tools. On Team and up, Kai Copilot merges duplicate requests, links each to the customers who asked and drafts the changelog when it ships.

Your team approves the work, then, on Team and up, Kai Code plans the change, writes the code, runs tests and opens a pull request linked to the request. Engineers review and merge. This is the build step of closing the loop from request to release; see AI customer support for SaaS.

Gleap keeps the roadmap next to customer support and the agents that act on the feedback: tickets link to requests, on Team and up Kai Code builds approved work, and your release update reaches the people who asked. Requests keep their customer context in Gleap's customer feedback software. Switching from one of them? Compare Gleap as a Canny alternative, as a Productboard alternative and as a Featurebase alternative.

The feature roadmap, a custom portal domain and every Kai agent come with Team ($149 per month, billed annually). Kai Copilot bills for the work it does. See pricing.