You want customers, prospects, or your community to see your roadmap: what shipped, what's in progress, what's coming next. You already run that work in Linear, but Linear has no "publish my roadmap" button. Here are the four real paths to a Linear public roadmap, what each one costs you, and where each one breaks.
TL;DR
The right path depends on who "the public" actually is.
- Sharing with everyone on the internet (community, prospects, product transparency)? Linear's native shared views are free and good enough for a technical audience. For a polished, branded page, reach for a dedicated public-roadmap tool.
- Sharing with specific paying customers, each seeing only their project? That's a client portal problem, not a public roadmap problem. Different shape, different tools.
- Need full control of design, branding, or unusual filtering? Build on the Linear API. Budget weeks, not hours.
Who this post is for
This post assumes you already run your roadmap in Linear and want to show it to people outside the workspace. If you do not use Linear yet, the choice is upstream of this article. If your "public" is actually a set of named clients (each seeing only their project), that's a client portal problem, not a public roadmap problem; the tools are different and the tradeoffs invert.
Path 1: What Linear gives you natively (and what it does not)
This is the path most people expect to find and the path that disappoints first. Linear has shipped public-flavored features (Customer Requests, guest access, Slack integrations) but it does not have a native "publish my roadmap to a non-Linear audience" surface. The long-running linear/linear#653 request for public link sharing was filed externally and closed without action.
Native Linear also does not give you what a public roadmap actually needs:
- A truly read-only view. Guest seats are read-write by default. Clients can edit issues, leave comments in your workspace, and accidentally reassign or break things. There is no "view-only" mode for external visitors.
- A scoped view. Guest access is team-scoped, not project-scoped. Visitors see every issue in any team they have been added to. If two clients share a team, they see each other's work.
- Branding. Native shared views live on Linear's domain in Linear's developer-focused UI. No logo, no custom domain, no way to dress it up for a customer-facing audience.
If you only need internal-team visibility, or you are willing to onboard every viewer into Linear, native is enough. If "public" in your search query means anyone on the internet visiting a clean, scoped, branded page that only shows what you want shown, native does not cover the job. The rest of this post is for you.
Path 2: Dedicated Linear public roadmap tools
A small set of tools exist specifically to take Linear data and render it as a public-facing roadmap or status page.
SteelSync
SteelSync is the oldest entrant in this category and still ranks well on most Linear-niche SERPs. The product centers on public roadmaps, status updates, and release tracking sourced from Linear, with out-of-the-box layouts, voting on roadmap items, and customer subscriptions to release updates. Two things to know before committing: there has been no visible shipping activity for roughly a year, and the view layout is fixed (limited control over what each visitor sees). The SEO presence is residual; the product underneath has been static.
Lindie
Lindie was the second-mover in this category. It is still listed in Linear's integration directory and the product remains available, but it shows the same shape as SteelSync: no meaningful shipping activity for roughly a year, fixed display layout. Users who migrated from Lindie to other tools have also reported little to no support response when issues come up. Verify current status on lindie.app and ask about support SLA before committing.
Other entrants worth knowing about
IssueBee markets itself as "beautiful kanban boards for Linear" but is currently in early access with no visible user base; treat it as a name to be aware of rather than a viable option. FeedVote is a newer entrant publishing aggressively on the category but is still establishing itself as a product. For both, confirm there is real product behind the marketing before betting a customer-facing surface on them.
These purpose-built tools shine when you want a turnkey public roadmap and accept their framing. They are weaker when your real need is something bespoke or when access varies per visitor.
Path 3: Build a custom Linear public roadmap with the API
Linear's GraphQL API is solid, and a small Next.js or SvelteKit app can hit Linear, render a roadmap view, and deploy in a weekend.
What "in a weekend" actually means after the initial push:
- OAuth or API-key handling, with token rotation if you go OAuth
- A sync layer so you are not querying Linear on every visitor pageload at scale
- A filtering layer (which Linear projects, teams, and labels are public versus internal?)
- A frontend that is genuinely better than the native Linear public view; otherwise this is busywork that ships a worse experience
- Ongoing maintenance as Linear ships API and webhook changes
This is the right path if you have very specific design requirements, an in-house engineer with bandwidth, and a long-term commitment to maintaining the tool. For most product teams, the math is bad: you are building a roadmap publisher instead of building your product. For agencies, the same logic applies; spending two weeks building a portal is two weeks not spent on client work.
A middle path: build a custom client portal only if no off-the-shelf tool matches your filtering needs.
Path 4: Use a portal tool with public rooms
Most teams who search "Linear public roadmap" want one of two things: (a) total transparency for everyone, or (b) clear visibility for the customers they actually serve. The second is more common than people realize, and "public roadmap" is the wrong tool for it.
If you are an agency, B2B SaaS company, or product team selling to specific customers, what those customers usually want is not a single public list of all your work. They want to see their project, their requests, their progress, their releases. That is a client portal problem, and it has different requirements: authenticated access per customer, filtered views per project, branded look on your domain, a clean way to track requests. The hidden cost post covers the structural argument for portal-shape over guest-seat-shape.
Helium Rooms (full disclosure: this is our product) covers both modes. You can create a public room with no login, shareable URL, your logo, a custom domain, and filtering down to specific Linear projects, teams, or labels. You can also create private rooms per customer with their own login.
Same product, two access modes, same underlying Linear sync. Helium is an official Linear integration, with a free tier if you want to try it.
If you genuinely want one public roadmap and that is the right job: public-room mode covers it. If you want client-specific portals: same product, switch the access mode per room.
Comparison table
| Tool | Public roadmap | Branded / custom domain | Per-client gating | Free tier | Notes |
|---|---|---|---|---|---|
| Linear native | No (no non-account public view) | No | No | Included | Internal sharing only; guests need accounts |
| SteelSync | Yes (focus area) | Yes | Limited | Yes | Oldest entrant; ~1 year no shipping, layout fixed |
| Lindie | Yes | Yes | Yes | Verify on site | Second-mover; ~1 year no shipping, support reportedly slow or absent |
| Helium Rooms | Yes (open mode) | Yes | Yes (auth per room) | Yes | Both public and private rooms; client portal first |
IssueBee (early access) and FeedVote (newer entrant) are also in the space but not yet proven; covered above in the body. Pricing and feature sets change. Confirm on each tool's site before committing.
Decision framework
- Open-source project, side project, or one-person team broadcasting to a technical community: Linear native public view (with the read-only, scoping, and branding caveats above). Free, zero setup.
- SaaS company with a single branded public roadmap page: Helium Rooms in open-room mode is the path we ship and support. SteelSync is the older alternative if you want a more established (if quieter) product.
- Agency or B2B SaaS with named clients, each needing their own scoped view: Helium Rooms in authenticated-room mode, or build a custom client portal. The right surface is per-client, not a single page.
- Unique filtering, layout, or design requirements you cannot get off the shelf: Linear API. Budget weeks and ongoing maintenance.
The worst path is a manual Notion page or a monthly email recap. Both work for the first month. Then they drift, the public page goes stale, and you become a human status bot writing updates that are outdated by the time you send them.
FAQ
Is there a built-in Linear public roadmap feature?
No, not in the sense most people expect. Linear has shipped customer-facing features like Customer Requests and guest access. But it does not currently support handing a non-Linear visitor a polished, branded roadmap page on its own.
The long-running linear/linear#653 request for public link sharing was filed externally and closed without action. Linear has effectively delegated this surface to the ecosystem of third-party tools.
If you want a public Linear roadmap on your own domain with your branding, you need a dedicated tool: SteelSync, IssueBee, or Helium Rooms. The alternative is a custom build on the Linear API.
How is a Linear public roadmap different from a client portal?
A public roadmap shows the same content to every visitor, usually a single product's shipped and upcoming work. A client portal shows different content to different authenticated users; each customer logs in and sees only their project, their requests, and their releases. If you are an agency or B2B SaaS, the people you call "the public" are usually specific paying customers, and what they need is a per-client portal with filtered access. Picking a public-roadmap tool when the real job is per-client visibility leads to either over-exposure (every customer sees every other customer's work) or under-fit (the tool cannot scope per client).
Can I make a Linear public roadmap with my own domain and branding?
Not with Linear's native sharing. The public link uses Linear's interface on a linear.app subdomain.
To brand a public Linear roadmap with your own logo and custom domain, you need a dedicated tool (SteelSync, Lindie, Helium Rooms) or a custom build on the Linear API. Branding matters more for B2B products selling to enterprise buyers, and for agencies where the roadmap sits inside the service offering. For a community or open-source roadmap, native sharing is usually enough.
Which Linear public roadmap tool is best for an agency?
For an agency, the better question is whether you actually want a public roadmap or a per-client portal. If clients each need their own filtered view, a client portal tool like Helium Rooms fits the shape of the job. If your agency runs a single page covering your process, methodology, or shared visibility for everyone you work with, Helium Rooms covers that mode too via an open-access room; SteelSync is the older alternative for that specific use case.
Is Lindie still a good option for a Linear public roadmap?
Lindie's product is still listed in Linear's integration directory and remains available, but there has been no visible shipping activity for roughly a year. Users who migrated from Lindie to other tools have also reported slow or absent support response. SteelSync, the oldest entrant, has been similarly static and carries the same fixed-layout limitation. If you want an actively-developed option with responsive support, Helium Rooms is the alternative we ship.
Does Helium Rooms support a public Linear roadmap?
Yes. Helium supports an "open" access mode where a room is reachable without a login. You can brand it with your logo and a custom domain, and filter it down to specific Linear projects, teams, or labels.
The same product supports authenticated rooms for per-client portals. You can run one public page for everyone and additional gated rooms for specific customers from the same workspace.