Released
Released builds two Atlassian Forge apps for Jira Cloud: Hub, which turns completed Jira work into AI-drafted release notes, public roadmaps and customer feedback, and BetterBoard, a faster, more flexible board spanning every Jira space.
What is Released?
Released is a pair of Atlassian Forge apps published by Released Software Pty Ltd, a Sydney company founded in 2023 by former Atlassians Jens Schumacher and Adam Ahmed, with Stefan Saasen as principal architect. The team came out of Jira, Confluence and Bitbucket; the vendor was named Atlassian Partner of the Year 2023 and is a Silver Marketplace Partner. Both apps install into Jira Cloud from the Atlassian Marketplace and read Jira issues live, so Jira stays the source of truth and no second database has to be kept in step.
Hub covers everything a product team has to communicate outside the delivery team. It publishes live public roadmaps as a board or a timeline from Jira or Jira Product Discovery, with separate views for customers, executives and partners drawn from the same data and made public, password-protected or invite-only. It runs a feedback portal with wishlists and voting, an embeddable form and capture from Slack, funnelling everything into one inbox where each item links back to a Jira issue or a Product Discovery idea. External readers and contributors need no Jira licence. Its AI copywriter drafts release notes in one click from a changelist filtered by status, timeframe and labels; prompts can be tuned per issue type, templates fix the structure, and AI blocks fill a section while the rest stays hand-written. The approved update then goes out to a branded changelog on a custom domain, an embedded page or popup widget, Confluence, Slack or a Framer site, with email subscriptions for readers. AI use is metered in tokens, from 2,000 to 20,000 per user depending on the plan.
BetterBoard is the everyday half: one board across Jira Software, Jira Service Management and Jira Product Discovery spaces, chosen card fields, columns mapped to any field rather than status alone, filters as expressive as JQL without writing JQL, colour rules, time-in-status, private and shared boards, a Cmd+K palette, single-key shortcuts and bulk editing.
Security leans on the Atlassian platform: SOC 2 Type 2 with independent audits and penetration tests, SAML SSO through Atlassian Access, encryption in transit and at rest, and a stated commitment that customer data never trains AI models. Atlassian Cloud only.
What it does
- Draft release notes with AI from completed Jira issues
- Publish a live public roadmap straight from Jira or Jira Product Discovery
- Collect customer ideas, votes and feedback into a single Jira-linked inbox
- Send the same approved update to an announcement page, an embedded widget, Confluence and Slack
- Filter a changelist by status, timeframe and labels before drafting anything
- Run one board across Jira Software, Jira Service Management and Jira Product Discovery spaces
- Bulk-edit Jira issues from the keyboard through a command palette and single-key shortcuts
When to use Released / When not to
A quick filter to help you decide if Released is the right fit.
When to use Released
- Product managers who plan in Jira or Jira Product Discovery and have to keep customers, executives and partners informed
- Product teams that publish release notes and would rather not copy Jira tickets into a separate changelog tool
- Small Jira Cloud sites of up to ten users, for which both apps cost nothing
- Atlassian-centric organisations that want billing, single sign-on and permissions to stay inside the Atlassian platform
- Agile delivery leads and scrum masters who need one board across Jira Software, Jira Service Management and Jira Product Discovery spaces
When not to use Released
- Teams on Jira Data Center or Jira Server, since Hub is sold for Atlassian Cloud only
- Anyone who does not work in Jira, because every feature reads Jira issues
- Engineers who need to automate publishing through an API, as Released exposes none
- Organisations bound to keep customer data inside the European Union, since portal data sits in AWS us-east-1 and us-east-2
- Users expecting a native mobile app or phone support, neither of which exists
How to use Released
A typical end-to-end flow, from setup to results.
- Install the app into a Jira Cloud site from the Atlassian Marketplace, with no separate account to create
- Let the app reuse the Jira users, groups and permissions the team already has
- For Hub, set up the Product Hub space: branding, custom domain or embed, and trusted domains
- Turn on user verification if the portal has to stay restricted to named people or email domains
- Publish a first roadmap by picking the Jira or Product Discovery work and mapping fields to columns, statuses and themes
- Open the feedback portal or embed the feedback form so customers can submit and upvote ideas
- Build a changelist by filtering completed issues on status, timeframe and labels
- Generate the AI draft, then edit the headline, story, media and detail without leaving Jira
- Pick the channels — announcement page, widget, Confluence, Slack — and publish
- Tune the AI afterwards in the space settings: custom base prompt, per-issue-type prompts, tone, output language
Pros & Cons
Pros
- No second system to maintain: roadmaps, feedback and release notes all read live Jira data
- Customers and stakeholders read roadmaps and file feedback without a Jira licence
- Free for up to ten users on both products, and every BetterBoard feature is included at every tier
- Low per-user pricing beyond that, with automatic volume discounts down to USD 0.01 per user on Hub
- SOC 2 Type 2, plus a published DPA, EU Standard Contractual Clauses, subprocessor list and service level agreement
- Customer data is never used to train AI models, and OpenAI does not train on API submissions
- Fast to adopt: billing, single sign-on and user management are delegated to Atlassian
Cons
- Atlassian Cloud only: no Jira Data Center, no Jira Server, and useless outside Jira altogether
- No public API and no native mobile app
- Billing counts every active user on the Jira site, not only the people who open Released
- AI generation is capped by a token quota per user and per plan; more allowance has to be negotiated with support
- Portal data is hosted in AWS us-east-1 and us-east-2, with no announced European option
- Support runs in English or German only, within 24 business hours, 9am to 5pm AET, and excludes phone support
- Terms, privacy policy and DPA all still read 30 January 2024 although the product catalogue has moved on
Pricing & Plans
Released offers a permanent free plan on both products: Hub is free for up to ten users with 2,000 AI tokens each, and BetterBoard is free for Jira Cloud sites of up to ten users with every feature included. The lowest paid entry point is BetterBoard at USD 0.45 per user per month for sites of eleven users or more; Hub's first paid tier, Standard, is USD 1.10 per user per month. Every paid plan opens with a 30-day free trial, billing is handled by the Atlassian Marketplace, and volume discounts apply automatically as the Jira user tier grows.
- unlimited idea portals
- feedback inbox
- public board and timeline roadmaps
- AI-generated release notes
- templates
- automatic Jira issue linking
- publishing to Confluence and Slack
- everything in Free plus the option to remove the Hub watermark
- everything in Standard plus embeddable feedback forms
- feedback via Slack
- premium support and onboarding
- BetterBoard Small teams — USD 0 for up to 10 users
- with every BetterBoard feature included
- BetterBoard Growing teams — USD 0.45 per user per month from 11 users
- the same complete product
- paid through Atlassian
Data, GDPR & hosting
A consolidated view of how Released handles your data.
GDPR overview
GDPR is addressed explicitly and at length. The privacy policy borrows the Regulation's definitions and reserves clauses 16 to 21 for controllers, and Released commits to technical and organisational measures meeting both the Australian Privacy Act 1988 (Cth) and the GDPR. A published Data Processing Addendum covers the EU and UK GDPR, the UK Data Protection Act 2018, PECR 2003, CCPA/CPRA and the VCDPA, and incorporates the 2021/914 Standard Contractual Clauses, a UK Addendum and the revised Swiss FADP. Data subjects may request access, correction or erasure, complaints are answered within thirty days, and audits are allowed. Transfers reach the United States, Australia and the European Union. Two gaps remain: no Article 27 EU representative is named and no data protection officer is identified. Governing law is New South Wales unless the customer is itself a controller.
Who owns the data?
Under the published Data Processing Addendum the customer is the data exporter and controller, while Released Software Pty Ltd is the data importer and processor, so ownership stays with the customer. Jira data itself never leaves Jira: the app calls the Jira REST API from the user's browser, directly or through Released gateway services, and the security page states that no Jira data is ever loaded, created, updated or deleted outside an action the user started or outside the Jira site's permission model. Release notes, roadmaps and their metadata are stored by Released. The privacy policy commits to never selling or redistributing customer data, and on termination the customer chooses between having it returned or destroyed.
Reuse rights
Content published on the Released website belongs to the vendor or its licensors, and the terms forbid copying, redistributing, translating or deriving work from it unless the site explicitly allows a personal, non-commercial download. What a customer produces inside the product is a different matter: release notes, roadmaps and portal pages are built from that customer's own Jira issues and remain theirs to publish, embed on their site or share on a custom domain. On the vendor's side, the privacy policy limits processing to release notifications, product analytics and technical telemetry used for updates, support and marketing, with optional analytics cookies on the website. Atlassian handles commercial functions including payment processing, and OpenAI powers the AI features. Data is encrypted in transit and at rest, and both Released and OpenAI state that it is never used to train models.
Data retention & training
Hosting summary
Portal data — release notes, roadmaps and their metadata — is stored in a database in the AWS us-east-1 region, with backup copies kept in the same region for up to 30 days. Images embedded in restricted or public portals live in AWS us-east-2 behind obfuscated URLs. Publicly accessible portals are cached worldwide through AWS S3, AWS CloudFront and Cloudflare for delivery speed. The privacy policy adds that data is held on a PostgreSQL database in the United States through Supabase and that the product is hosted globally on AWS, with a commitment to notify customers if the storage location changes. Recipients of personal data may be located in the United States, Australia and countries within the European Union. Data is encrypted in transit and at rest. Jira data itself is not copied out of Jira: it is read through the Jira REST API under the signed-in user's permissions. Jurisdiction is New South Wales, Australia, unless the customer is itself a controller.
Where Released works
Country-level availability.
Not available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Released.
- The bill follows the Jira site, not usage: every active licensed user is charged even if only three people ever open Released
- A public portal is a public statement about the roadmap; the vendor itself warns against publishing information an attacker could use
- AI drafts read fluently and can be published almost untouched, which makes it easy to ship a release note nobody actually verified against the shipped work
- Portal images sit behind obfuscated URLs rather than authentication, so anyone holding the link keeps access
- Verification tokens stay valid for seven days on the issuing device, and backups persist for up to 30 days after a deletion
- Cancelling stops the next billing cycle but refunds nothing already charged, and the terms bar users located in embargoed countries or on United States restricted-party lists
- No Article 27 EU representative and no data protection officer are named, despite European customers and Standard Contractual Clauses in the DPA
Setup & Integrations
Technical difficulty
Low. Both apps install into Jira Cloud in one click from the Atlassian Marketplace, with no separate account and no code to deploy; they reuse existing Jira permissions and user management. One customer reports under fifteen minutes from install to a published roadmap. The optional steps are more technical without being hard: custom domain, page or widget embed, embedded feedback form, trusted domains and user verification. SAML SSO and automated provisioning require Atlassian Access. Tuning the AI is a prompt setting inside the space, not development work.
Deployment
Integrations
Supported languages
Behind Released
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Released.
Frequently asked questions
Which Jira versions does Released work with?
Do customers need a Jira licence to read a roadmap or send feedback?
Is there a free plan?
Why does the bill count every Jira user?
What is an AI token, and what happens if the quota runs out?
Is customer data used to train AI models?
Where is the data hosted and how long are backups kept?
Can a roadmap or portal be kept private?
Does Released offer an API?
What support is available?
Should you pick Released?
Released is a deliberately narrow tool, and that is its strength. Everything it does assumes the work already lives in Jira, and in exchange it removes the copy-and-paste layer most product teams build around it: a roadmap tool, a feedback database, a changelog app and a status deck collapse into two apps reading live Jira data. Functional coverage for that scope is unusually complete, from audience-specific roadmaps and a voting feedback portal to AI-drafted release notes, multi-channel publishing and a genuinely faster board.
The compliance file is stronger than the vendor's size would suggest: SOC 2 Type 2, a published Data Processing Addendum with EU Standard Contractual Clauses and a UK Addendum, a subprocessor list, a service level agreement, and an explicit commitment that customer data never trains AI models. Pricing is equally restrained: free up to ten users on both products, then USD 0.45 per user per month for BetterBoard and USD 1.10 for Hub's first paid tier, billed through Atlassian with automatic volume discounts.
The reservations are structural rather than incidental. It is Atlassian Cloud only, so Data Center and Server sites are out. There is no public API, no native mobile app and no phone support. Portal data lives in AWS us-east-1 and us-east-2 with no announced European option, which matters for organisations bound to EU hosting. Billing counts every active Jira user, not only the people who open Released, and AI generation is capped by a token quota. The terms, privacy policy and DPA all still read Last updated 30 January 2024 while the catalogue has clearly moved on.
For a team whose work already sits in Jira and whose real problem is telling everyone else about it, the fit is close to exact. For anyone else, it is not a candidate at all.
- Choosing a selection results in a full page refresh.
- Opens in a new window.