A public roadmap that tells people when it moves
Group work into Planned, In progress, and Shipped. Each item stays linked to the feedback posts that asked for it, so the people who requested it hear about it without you keeping a list.
The problem
Nobody reads a roadmap they have to ask for
The internal roadmap lives in a planning tool your customers cannot see, so 'are you working on this?' becomes a support ticket. The public roadmap, if it exists, is a slide that was accurate in February.
A roadmap that is generated from the work itself has neither problem: it is current because it is the same object your team is moving, and it is public because there is nothing to copy across.
What you get
Everything in roadmaps
Linked to the request
A roadmap item carries the feedback posts that fed it. When it ships, SignlOS already knows every customer to tell — you never build that list.
Statuses, not dates
'In progress' ages gracefully. 'March' becomes a broken promise on 1 April, and customers remember the miss longer than the feature.
Follow an item
Customers can subscribe to a specific item without voting on a post, and get the same notification when it moves.
Public or internal
Publish the whole roadmap, or keep columns internal until you are ready. What you have not published is not readable, including through the API.
Embed it
The roadmap widget answers 'are you working on this?' inside your own product, where the question is actually being asked.
One click to announce
Moving an item to Shipped is the natural moment to write the release note. The two are the same workflow, not two tools.
Questions
Frequently asked
Keep reading
Works with
Feedback boards
Customers post ideas and bugs, vote on the ones they care about, and get told when their request moves. You get a ranked list instead of a shared inbox.
Learn more →Release notes
A changelog with an editor, categories, and a public feed. Publishing notifies everyone who voted for the linked posts — the loop from request to announcement closes itself.
Learn more →Status pages
Per-component health, incident timelines, and operator notices — on your own domain. Every minute your status page stays silent during an outage is a support ticket you chose to receive.
Learn more →Full documentation lives at docs.signlos.com.
Your customers already told you what to build
It is in a support inbox, three Slack threads, and a spreadsheet nobody has opened since March. Put it somewhere it can be counted.
No credit card required to start. $0 forever.