Releasenote
Releasenote turns raw engineering activity into customer-facing release notes. It pulls commits, pull requests and issues from GitHub, Jira and Linear, drafts structured notes with AI, then publishes them to a branded public changelog.
What is Releasenote?
Releasenote is a web application that turns the raw output of a development cycle into release notes a customer can actually read. Its own framing is modest and precise: a small SaaS release workflow. The promise on the home page is that release notes should be fast to generate, easy to edit and safe to publish.
The workflow it describes has three stages. First, connect the sources: Releasenote advertises connectors for GitHub, Jira and Linear, pulling commits, pull requests and issues from a product workflow into one place. Second, generate: the AI produces structured HTML drafts deliberately tuned for customer-facing updates rather than internal summaries. Third, publish: the finished note goes to a branded public changelog portal, and the portal's subscribers are notified.
Signing up is deliberately light. The form asks for a first name, a last name, an email address and an organisation name, then sends a magic link, so there is no password to choose. That organisation field signals a team product rather than a personal one.
What a prospective user should understand is how little of this is visible before creating an account. The public surface is three pages: the home page, the login page and the signup form. The Try Builder call to action does not open a sandbox, it redirects to the login page. There are no screenshots, no video and no demonstration portal. Requests for a pricing page, an about page, a contact page, documentation, a blog, a security page, legal notices, a sitemap and a robots.txt all returned 404 on 23 August 2026. The Terms of Service and Privacy Policy linked from the signup checkbox return 404 as well, even though the form asks users to accept them.
Two technical facts come from the application's own health endpoint. It names azure-openai as the AI provider, and it reported the database as unhealthy on three separate checks the same day. The domain's first archived capture, in January 2023, shows a different product entirely, so the current build is a later rebuild rather than a continuous service.
What it does
- Pull commits, pull requests and issues from GitHub, Jira and Linear into one place
- Generate a draft release note with AI from that raw engineering activity
- Produce structured HTML tuned for a customer-facing audience
- Edit the generated draft before anything goes out
- Publish the finished note to a branded public changelog portal
- Notify the portal's subscribers when a release ships
- Keep an organisation's release history in a single workspace
When to use Releasenote / When not to
A quick filter to help you decide if Releasenote is the right fit.
When to use Releasenote
- Product teams that ship frequently and have to announce every release to customers
- Small SaaS teams wanting a release workflow they do not have to build themselves
- Teams already working in GitHub, Jira or Linear, whose commits, pull requests and issues can feed the drafts
- Product managers and technical writers who own the changelog and would rather edit a draft than face a blank page
- Teams that want a branded public changelog portal without hosting one
When not to use Releasenote
- Buyers who need published terms of service and a privacy policy before signing up, since both links on the signup form return 404
- Anyone who needs to know who the vendor is: the site shows no company name, no postal address and no contact email
- Teams that require a public price before creating an account, as no pricing page exists
- Developers looking for a public API or developer documentation, neither of which is published
- Organisations with formal GDPR obligations, as no DPA, subprocessor list or retention rule is documented anywhere
How to use Releasenote
A typical end-to-end flow, from setup to results.
- Click Start Free on the home page
- Fill in your first name, last name, email address and organisation name on the signup form
- Tick the box accepting the Terms of Service and Privacy Policy, noting that both links currently lead to 404 pages
- Submit the form and wait for the magic link sent by email, as no password is created
- Open that link to finish registration and reach the dashboard
- Connect your sources, GitHub, Jira or Linear, so the tool can read commits, pull requests and issues (everything from this point sits behind the login and could not be verified)
- Open the builder to start a new release note
- Let the AI produce a structured HTML draft from the collected engineering activity
- Edit the draft until it reads the way you want your customers to read it
- Publish to the public changelog portal, which notifies its subscribers
Pros & Cons
Pros
- Covers the whole chain in one product: sources, AI draft, publication and subscriber notification
- The three advertised connectors are the tools most product teams already use
- A hosted public changelog portal means nothing to build or host yourself
- Output is structured HTML, usable as it stands
- Signing up is passwordless and takes four fields
- The entry point is advertised as free
- Scoped to an organisation from the first screen, so it suits a team rather than an individual
Cons
- No pricing page, so there is no way to learn what it costs without creating an account
- No terms of service and no privacy policy: both URLs return 404, even though the signup form asks you to accept them
- The vendor is unidentifiable, with no company name, no postal address, no contact email and no about or contact page
- Nothing demonstrates that the product works: no screenshots, no video, and Try Builder simply redirects to the login page
- The application's own health endpoint reported its database as unhealthy on three checks on 23 August 2026
- No documentation, no public API and no identifiable support channel
- No social accounts, and no mobile or desktop application
Pricing & Plans
No pricing is published. The pricing page returns 404, no amount appears anywhere on the site, and a targeted web search returned nothing. The only pricing signal is the wording of the main call to action, Start Free, which indicates that an account can be opened at no cost but does not state whether this is a permanent free plan or a time-limited trial. No amount, currency or billing period could therefore be established.
Data, GDPR & hosting
A consolidated view of how Releasenote handles your data.
GDPR overview
There is no mention of the GDPR anywhere on Releasenote's public pages. A search of both the rendered text and the archived HTML of the home page, the login page and the signup form returns no occurrence of GDPR, CCPA, SOC 2, ISO 27001 or HIPAA. No data protection officer is named, no Article 27 representative is designated, and no privacy contact address is published. The signup form does show a checkbox stating that the user agrees to the Terms of Service and the Privacy Policy, but both links point to pages that returned 404 on 23 August 2026, so neither document could be read. This matters, because the same form collects a first name, a last name, an email address and an organisation name. In short, the site makes no GDPR claim and offers nothing on which compliance could be assessed.
Hosting summary
The vendor publishes nothing about data hosting. There is no privacy policy, as that URL returns 404, and no jurisdiction, region, country or subprocessor is named anywhere on the site. What can be said comes from network observation alone, and it describes how the website is delivered rather than where user data is stored. The site responds with a server: Vercel header and was served from a Paris edge node; the domain resolves to 216.198.79.1, an anycast address belonging to AS16509, Amazon.com, in the United States. The domain registrar is Cloudflare, Inc., also in the United States. Separately, the application's own health endpoint names azure-openai as its AI provider, which means content submitted for generation is processed by a third party, though the endpoint says nothing about where. None of these observations should be read as a hosting commitment. They indicate that the front end is distributed through a US-based platform, not that user content, connected repository data or published changelogs are stored in any particular country. Anyone with a data residency requirement would have to ask the vendor directly, and no contact address is published.
Things to keep in mind
Risks and trade-offs to weigh before adopting Releasenote.
- You are asked to accept a Terms of Service and a Privacy Policy that do not exist, so you sign up to an agreement nobody can read
- Connecting GitHub, Jira or Linear hands internal engineering history, including commits, pull requests and issue titles, to a vendor whose identity is not published
- Nothing states whether your content is used to train models, and no opt-out is documented
- No retention or deletion rule is published, so there is no way to know how long anything is kept
- The health endpoint reported the database as unhealthy on the day of review, putting anything stored there at risk of loss or unavailability
- An AI-drafted note published without careful review can leak an internal feature name or misdescribe what actually shipped
- Relying on a hosted portal for durable customer communication means your changelog history lives somewhere you do not control
Setup & Integrations
Technical difficulty
Very low, at least as far as anyone can verify. Creating an account takes four fields and a magic link, with no password to set, nothing to install, no extension and no command-line tool. The one genuinely technical step is connecting GitHub, Jira or Linear, which requires the right permissions on those systems and, in most organisations, an administrator's cooperation. Beyond that, no setup documentation is published, so the real effort of connecting sources and configuring the public portal cannot be assessed from outside the login.
Deployment
Integrations
Behind Releasenote
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What does Releasenote do?
Which tools does it connect to?
How do I create an account?
What does it cost?
Can I try it without creating an account?
Is there a public API?
Is there a mobile app?
What do the terms of service and privacy policy say?
Which AI model does it use?
Should you pick Releasenote?
Releasenote describes a genuinely useful and well-bounded job: take the raw output of a sprint, the commits, pull requests and issues, turn it into something a customer can read, then publish it somewhere public. The three connectors it names, GitHub, Jira and Linear, are the right ones, and the chain from source to branded portal to subscriber notification is the chain product teams actually need.
The difficulty is that almost none of it can be checked. On 23 August 2026 the public site was three pages long, with no pricing page, no about page, no contact page, no documentation and no security page. The Try Builder button, which reads like an invitation to test the product, redirects to the login form, and no screenshot or video shows the generator at work.
More seriously, the Terms of Service and Privacy Policy that the signup form asks you to accept both return 404. That leaves a tool which collects your name, email and organisation name, and which is designed to read your engineering history, with no published contract, no stated retention rule, no subprocessor list and no position on whether your content trains a model. The vendor itself is anonymous.
The application's own health endpoint added a further caution, reporting its database as unhealthy on three consecutive checks that day, while naming Azure OpenAI as its provider.
None of this means the product does not work. It means that, at the time of review, a prospective user could verify almost nothing before handing over access to internal engineering data. Treat it as an early-stage product, evaluate it with a throwaway repository rather than a production one, and expect to ask directly for the terms the site does not publish.
- Choosing a selection results in a full page refresh.
- Opens in a new window.