2025 has been a huge year.

Released moved beyond publishing roadmaps and updates.

It became a Product Hub. A system for connecting product work directly to customer experience.

Passive roadmaps turned into active conversations. Feedback stopped disappearing and became a clear, fast loop that teams can act on every day.

The Product Hub

Product teams are spending far too much time maintaining zombie roadmaps in third-party tools that are always out of sync with Jira. Meanwhile, stakeholders are digging through outdated PowerPoint decks just to figure out what had shipped and what hadn’t.

In February, we responded by launching the Product Hub. A single place for live product updates that actually stay current.

We introduced Portals as dedicated spaces for individual products or initiatives. To make them feel like a natural extension of a company’s own setup, we focused on a few fundamentals:

Portal themes like “Sydney” for a clean horizontal roadmap and “San Francisco” for a continuous timeline layout.
Custom domains, host your hub on your own domain like http://hub.yourcompany.com.
Access management, using email domains to automatically grant access to internal stakeholders without manual user setup.

The goal was simple: give product work a home that felt intentional, trustworthy, and easy to access.

Tailored Roadmaps

In the spring we focused our energy again on roadmaps. Doubling down on a view that would lay the foundation for the rest of the year.

Different stakeholders look at the same roadmap for very different reasons. Leadership cares about strategic progress. Sales cares about what is landing when. Customer-facing teams care about specifics they can reference in conversations.

So we stopped forcing everyone to look at the same view.

With Multiple Roadmap Views, PMs could create different versions of a roadmap, all powered by the same live Jira data, but tailored to specific audiences.

We built on that with a few key additions:

One source of truth. Multiple, tailored narratives.

Feedback

By August, we were ready for the biggest shift of the year: Feedback.

Most tools treat feedback as a passive repository. Something to collect, tag, and maybe look at later.

We took a different approach.

We built the Feedback Inbox as a customer engagement tool for product teams.

It’s really quite simple. If a customer takes the time to share feedback, the product team should respond and follow up as reliably as a support or success team would.

A product team that engages with customers not only builds trust with those customers, but also empathy within the team.

Our focus was to make it as easy as possible for product teams to triage and act on feedback.

Feedback stopped being something you collect. It became something you work with.

Wishlists

In the fall, we tackled another long-standing problem: public voting boards.

Public boards tend to turn into popularity contests. Users vote based on what they see others voting for, not necessarily on what matters most to them.

In October, we introduced Wishlists.

Instead of voting publicly, users maintain a private list of things they want most.

This changed the signal completely:

Private intent, so users are not influenced by the crowd.
Wish limits, forcing people to actually prioritise instead of voting for everything.
Direct visibility in Jira, with a Wishers panel showing exactly who wants a feature and when they added it.
Jira Product Discovery integration, syncing wish counts into number fields so real customer demand can be used directly in prioritisation.

Less noise. Clearer signals.

And hundreds of improvements

And if this wasn’t enough, we shipped hundreds of improvements to make Released, faster, easier to use, and more flexible. To just name a few…

Image resizing, in release notes for cleaner, more professional updates.
Customizable portals, allowing you to rename the default “Changelog” and “Roadmap” navigation items.
Easier roadmap setup, that automatically generates roadmap columns based on the available options for the selected fields.
Reordering groups, allowing you to customize the order of swimlanes on the roadmap
New card design, to make roadmap cards look even better and accommodate large amounts of fields and comments.

… and the list goes on.

Building the customer communication platform for product teams

By the end of 2025, Released had moved into a different category.

Released has evolved into a customer communication platform for product teams. A single place where roadmaps, updates, and feedback come together in real time, powered directly by live Jira data.

While other tools focus on collecting ideas or planning in isolation, we focused on closing the loop. Making customer communication fast, contextual, and part of everyday product work.

That shift defined Released in 2025. And it sets the direction for what comes next in 2026.

Thank you for your trust, and for the feedback that continues to shape Released.

Happy holidays. We will see you in 2026.

Jens
Co-founder/CEO