Public roadmap and feature requests.

Public roadmap software shows customers which requests are planned, in progress and released, and lets them vote on what they need. Gleap's roadmap is 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. Your team reviews them in the Ideas pipeline, 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 intake list 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 PM scores each request on demand, revenue, strategic alignment and effort with your weights, next to the votes. Your team decides what moves to Planned.

You set who can upvote, submit, read and write comments, each separately. Guests confirm a vote with their email address. 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, and Kai Resolve does it for tickets it investigates: a feature-request verdict links the matching request and subscribes the customer.

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. Kai PM is an AI agent that scores requests, finds duplicates and helps prioritize your backlog.

Your team approves the work, then 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.

Gleap keeps the roadmap next to customer support and the agents that act on the feedback: tickets link to requests, Kai Code builds approved work, and the release reaches the people who asked. See Gleap as a Canny alternative and as a Productboard alternative.

The feature roadmap and a custom portal domain are included from the Team plan. Kai Resolve, Kai Code and Kai PM are in Pro. See pricing.