Same row. Three pages. Nothing copied.

Most teams keep a feedback board, a roadmap and a changelog in sync by hand — and quietly let two of them go stale. In Roadly they are three views of one record. Switch between them below; watch the reference number never change.

284Votes

Dark mode for the mobile app

PHI-4241 commentsopened 14 Mar

Shipped

This is one database row. The board shows its votes, the roadmap shows its status, the changelog shows its release note. Change the status once and all three are correct — because there was never more than one of them.

The stale roadmap is not a discipline problem. It's a data problem.

When your board, roadmap and changelog are three separate documents, keeping them honest is a chore somebody has to remember. Make them one record and it stops being possible to forget.

Status is the single control

One change, three pages

Move an item to Released and it leaves the roadmap's in-progress column and becomes eligible for the changelog. No second step.

Duplicates fold in before they count

284 means 284 people

Near-identical requests are caught as they arrive, so support shows as one honest number rather than six competing ones.

Nobody is emailed by surprise

Confirmed, then contacted

Following an item takes a confirmed address. It's the only way an email ever enters the system.

Not everyone who arrives has a feature request.

Some have a question. Some have a problem with an order number in it. A public voting board is the wrong answer to both — so the board sits next to a help center and a private thread, and a request can graduate into an idea without anyone retyping it.

Answered before it's asked

Help center

Write articles in the same editor as your changelog and publish them behind full-text search. Collections keep it navigable instead of a wall of links.

Private when it needs to be

Support requests

A request thread is readable by exactly two parties: the person who opened it and your team. No public post, no anonymous access, and an email when you reply.

A question can become an idea

Convert, don’t retype

When a request turns out to be a feature ask, move it onto the board as a real record. You edit it first — what someone wrote in private wasn’t written for an audience.

Two audiences who want opposite things — and both get served.

You're signed in all day and want density and a keyboard. Your community arrives from a link, on a phone, once, for under a minute. Designing for one usually means punishing the other.

Your inbox

Dense, keyboard-first

J/K to move, / to search, C to create, ⌘K for anything. Built for the person who lives here.

Their board

No account required

Post and vote in seconds. Hold submissions for review before they go public, if you want that.

Not in the box

On purpose

No sprints, story points or burndown — and no SLA timers or agent leaderboards on the support side either. Somewhere people visit voluntarily stops being that the moment it becomes an operations console.

Free while it's quiet. Community activity is never capped.

Posts, votes, comments, help articles and support requests are unlimited on every plan. Metering the thing that makes a board worth visiting is how boards die.

Free

  • 1 project — board, roadmap, changelog, help center and support
  • 3 teammates
  • 10 AI summaries a month
  • Unlimited posts, votes, comments, articles and requests

Pro

  • Unlimited projects
  • Unlimited teammates
  • Unlimited AI summaries
  • Private boards and your own branding

Pricing isn't set yet — Roadly hasn't launched.

Sign inOpen a board