Released Hub vs 
Frill Released Hub is the best choice for teams already using Jira or Jira Product Discovery to collect feedback, share roadmaps, and publish release notes. Frill suits teams that want a focused portal for customer ideas, voting, public roadmaps, announcements, and embedded surveys.
Released Hub Best for teams already using Jira or Jira Product Discovery
Frill Best for focused feedback and announcements
✓ Supported · — Partially supported · × Not available.
| Feature | Released Hub | Frill |
|---|---|---|
| Pricing | ||
| Free plan and limits Compare the limits and scope of the free offering. | Supported Up to 10 Jira users | Not available |
| Starting paid price Compare the entry paid plan, billing unit, and payment commitment. Free-plan limits are listed separately. | Standard: $1.10/Jira user/month; volume discounts apply | Startup starts at $25 per month and includes up to 50 active ideas and one survey. |
| Pricing model Understand what drives the bill, such as seats, site size, or tracked users. | Released Hub licensing is based on active licensed users on the Jira Cloud site, rather than just the authors using Released Hub. | Frill charges a flat workspace price by plan; every paid tier lists unlimited teammates, tracked users, and widgets. |
| Feedback collection and organisation | ||
| Feedback collection Collect ideas, requests, and problems from customers. | Supported | Supported |
| Feedback triage Review incoming feedback and organise it for follow-up. | Supported | Supported |
| End-user feedback portal Give customers a dedicated place to submit and browse feedback. | Supported | Supported |
| Respond to feedback Respond to customers and continue the feedback conversation. | Supported | Supported |
| Reply to feedback directly by email Record a customer’s email reply in the feedback thread without requiring a portal visit. | Supported | Not available |
| Feedback visibility controls Control whether feedback is private or visible to other customers. | Supported | Supported |
| Dedicated feedback forms Collect feedback through a dedicated form embedded in a website or app. | Supported Advanced plan | Supported |
| Automatic feedback capture Extract feedback from connected conversations without manually creating each entry. | Not available | Not available |
| Comments and discussions Discuss a request and add context in a shared conversation. | Supported | Supported |
| Private internal notes Keep team discussion separate from customer-visible replies. | Supported | Not available |
| Prioritisation and customer context | ||
| Wishlists and customer voting Understand which requests matter to customers through votes or personal selections. | Supported | Supported |
| Personal customer wishlists Let customers maintain a personal selection of the features they want. | Supported | Not available |
| Configurable wishlist limits Limit customer selections so they must choose what matters most. | Supported | Not available |
| Hide demand counts Hide totals to reduce the influence of other customers’ choices. | Supported | Not available |
| Customer segmentation Analyse feedback from particular customer groups. | Not available | Supported |
| Revenue-based prioritisation Consider account revenue when assessing customer demand. | Not available | Not available |
| Custom scoring frameworks Score requests using criteria chosen by the team. | Supported Through Jira/JPD | Supported |
| Prioritisation models Use formulas such as RICE or impact versus effort to compare priorities. | Supported Through Jira/JPD | Supported |
| Roadmap views and sharing | ||
| Public roadmaps Share upcoming work and progress with customers or stakeholders. | Supported | Supported |
| Board roadmap view Organise roadmap items into columns by status or planning stage. | Supported | Supported |
| Timeline view Show planned work against dates on a timeline. | Supported | Not available |
| Roadmaps across multiple projects Bring work from multiple projects into one shared roadmap. | Supported | Not available |
| Advanced roadmap filtering Choose which work appears using filters or advanced queries. | Supported | Not available |
| Separate customer-facing descriptions Write a customer-facing explanation separately from the internal planning description. | Supported | Not available |
| Show planning fields on the public roadmap Choose which internal planning fields customers can see on published items. | Supported | Not available |
| Control over roadmap publishing Decide when internal changes become visible to customers. | Supported | Supported |
| Release communication | ||
| Release notes Publish updates that explain what has changed in the product. | Supported | Supported |
| Release-note drafting workflow Compare where AI drafting happens and how source material reaches the writer. | Built-in AI drafting from selected Jira work | Not available |
| Reusable release-note templates Reuse an agreed structure when preparing each product update. | Supported | Not available |
| Configurable AI writing instructions Guide generated writing with tone, examples, or custom instructions. | Supported | Not available |
| Embedded product updates Show product updates directly inside a website or application. | Supported | Supported |
| Changelog email subscriptions Let readers subscribe to product updates by email. | Supported | Supported |
| Shipment communication Tell customers when new work becomes available. | Supported | Supported |
| Request-specific status notifications Notify people about progress on the particular requests they follow. | Not available | Supported |
| Integrations | ||
| Website and app embeds Bring customer-facing content into an existing website or application. | Supported | Supported |
| Support tool integrations Bring feedback from support conversations into the product workflow. | Supported Native through Jira | Supported |
| Team chat integrations Connect team chat to feedback collection or notifications. | Supported | Supported |
| Publishing integrations Distribute product updates to other tools and channels. | Limited Through embeds | Supported |
| API and webhooks Read or update data programmatically and react to product events. | Not available | Supported |
| Access and administration | ||
| Audience controls Choose which customers, teams, or individuals can access shared content. | Supported | Supported |
| External customer participation Let customers contribute without requiring an internal team licence. | Supported | Supported |
| Custom domains Publish customer-facing content under a domain your organisation controls. | Supported | Supported |
| SOC 2 compliance Assess the product’s documented SOC 2 compliance status. | Supported | Limited SOC 2 compliance is listed with the Enterprise plan. The public pricing page presents SOC 2 under Enterprise; the underlying report or certification scope was not independently reviewed. |
| Single sign-on Let users sign in through an existing identity provider. | Not available | Supported |
| Team roles and permissions Assign team members different responsibilities and access levels. | Not available | Supported |
| Jira integration | ||
| Jira issue linking Associate customer requests with Jira work items, including linking restrictions. | Supported | Limited Sending an idea to Jira creates a Jira Cloud issue with the title, description, and a link back to Frill. The integration is limited to Jira Cloud and one configured project. |
| Jira status sync for linked ideas Keep connected ideas or roadmaps aligned with Jira status changes. | Supported Controlled publishing | Not available |
| Show feedback on Jira work items Review customer feedback from a Jira work item rather than searching another tool. | Supported | Limited The created Jira issue includes the idea title, description, and a link back to Frill. The documentation does not describe a native Jira panel showing votes or discussion. |
| Create insights in Jira Product Discovery Create customer insights on Jira Product Discovery ideas. | Supported | Not available |
| Release notes from Jira work Use selected Jira work as the source for release-note drafts. | Supported | Not available |
| Atlassian user management Compare how team access is managed alongside Atlassian accounts and permissions. | Uses Jira permissions | Frill uses its own workspace roles and integration administration alongside Jira authorization. |
Released Hub 
Released Hub is particularly strong when delivery work already lives in Jira. Its AI drafts use selected work items as source material, while templates and writing instructions provide a consistent structure and style for updates.
Released Hub separates internal planning changes from customer-facing updates. Roadmap data stays connected to Jira, while teams decide when changes are ready to share—a useful fit for teams that need to review plans before communicating them.
Personal wishlists, configurable limits, and hidden counts encourage customers to make deliberate choices about the features they want.
Bring customer feedback into Jira Product Discovery as insights, keeping customer input alongside the ideas your team evaluates.
Frill 
Combine idea submission, voting, comments, a public roadmap, and product announcements.
Show Ideas, Roadmap, Announcements, and surveys inside an existing website or product.
Pay a flat plan price with unlimited teammates, tracked users, and widgets.
Released Hub Frill Look beyond vote totals to understand which requests matter, who needs them, and how they inform priorities.
Scoring and prioritisation use the capabilities of Jira and Jira Product Discovery, including custom formulas such as RICE in JPD.
Personal wishlists offer configurable selection limits and hidden counts, encouraging customers to choose what matters most. Why personal wishlists work better than public voting.
Teams can configure priority factors and compare ideas in a prioritisation matrix. Frill supports user segments and custom attributes for targeting and analysis.
Look at how feedback connects to Jira work and what your team needs to manage across the two tools.
Feedback on a roadmap item links automatically to its Jira work item, keeping customer input connected to the work being discussed. Teams can also link general feedback from the inbox. Jira-connected roadmaps retain control over when updates are shared publicly.
Sending an idea to Jira creates a Jira Cloud issue with the title, description, and a link back to Frill. The integration is limited to Jira Cloud and one configured project.
Consider how delivery work becomes a clear product update, from drafting through to publishing and distribution.
AI drafts release notes from selected Jira work items, with reusable templates and editing controls to shape each update. Teams can also write content manually.
Readers can subscribe to changelog emails through the portal or widget, connecting published updates with their audience.
Frill Announcements publishes product updates with categories, media, comments, and reactions. Readers can subscribe to Announcements and receive product-update emails.
Compare the context customers can see and the control your team has over sharing plans and progress.
Board and timeline views turn Jira-connected plans into customer-facing roadmaps. Teams choose which planning fields to display and can write a separate public description for each item.
Jira data stays current in the backend, while the team controls which updates reach customers and stakeholders, and when they are shared.
Frill includes a public roadmap connected to ideas and statuses. Frill widgets embed Ideas, Roadmap, and Announcements as launchers, inline frames, popovers, or modals.
Documentation reviewed 2026-09-15 / 2026-09-16. Based on product documentation and pricing sources.
Reviewed by Jens Schumacher
Last updated:
For teams already using Jira or Jira Product Discovery, Released Hub connects customer feedback, public roadmaps, and release notes with the work they already manage.
