ProductReleaseo · release communication
The changelog, the in-app announcements, the requests board, the roadmap, the help centre and the hosted public site — one product, one install, one place the loop closes.
Every screen here is the product.Real posts, real dates, out of a live workspace.
Not only on your own site.
The whole footprint
People arrive for the changelog. This is the rest of what comes with it — drawn to scale, so you can see which parts are load-bearing.
Every block on this map is a page in the dashboard today.
Server-side
Watch a business-critical process one step at a time — checkout, signup, password reset, a data import. Your backend reports each step with a single HTTP call.
No SDK, nothing in the browser. Releaseo knows the steps you declared and the calls you sent, and turns them into a live funnel, a run timeline, and a Slack or Discord alert when a step fails.
Write the release note once, from a post template. The same post lands in the widget, on your public site and in Slack.
Columns you name yourself, and visibility set per item — not per board.
Inside your product
A toast, a modal or a banner, shown in your own app to the audience you picked and on the pages you chose.
Each launch can be sourced from the roadmap item or the changelog post it came from, so the announcement and the release never drift into two different stories.
Audience
Build an audience from recursive AND / OR / NOT conditions — who the user is, the plan they are on, what they have done in your product, and what they have done inside Releaseo.
Save it once, then point a launch or an announcement at it instead of at everybody.
Ideas arrive from the widget. You approve what becomes public, and the votes do the sorting.
Folders and articles, published to your public site — the answers your inbox keeps repeating.
Private messages from the widget, encrypted at rest. Nobody reading the database can read them — including us.
Post to Slack or Discord when something happens: a built-in Releaseo moment, or an event you define yourself.
The vocabulary everything else uses — your own statuses, categories and label groups, defined once.
One script tag, 2,530 bytes gzipped. The UI runs in an iframe, so it never enters your bundle and sets no cookies.
Your changelog, roadmap and help centre on your own domain, built from 16 templates.
Publish
One post fans out to the in-app widget, your hosted public site, Slack, Discord and email — plus an in-app launch if you want one. You write it in one editor and pick the targets on the way out.
One publish reaches
Both of these are published.Each one went out through its own publish dialog — the channels are a decision per post, not a setting you make once and forget.
Feature requests
Your users file requests from the widget inside your product or from your public site, vote on the ones they want, and argue it out in the comments. You never have to go and collect any of it.
What arrives lands in a queue, not on your public board. You work that queue — Pending, Approved, Rejected — and attach what survives to the roadmap item it actually belongs to.
Then move that item to Released, and the changelog post is already waiting for you. You are editing a draft, not starting from an empty page.
Publish it and Releaseo tells the people who asked for it — the voters and followers already attached to that roadmap item.
Four queues, one boardPending, Approved and Rejected are separate tabs. Only what you approve is ever visible to a customer.
Every roadmap item then carries its own:
The embed
No build step, no npm package, no migration window. Paste it into your layout: the widget is live in your product and in-app launches start delivering.
<!-- Releaseo widget — paste once, before </body> --><script src="https://cdn.releaseo.io/sdk/v0/loader.js"></script><script> window.releaseo.init({ publishKey: "pk_live_..." });</script>
Same tag, every surface.A launch you build here — toast, modal or banner — is delivered by the loader you already pasted. There is no second install.
2,530bytes, gzipped
The loader in full — the whole of what your page downloads from us.
0cookies set
Nothing to add to your cookie banner.
0 KBin your bundle
The widget UI runs in an iframe, so none of it is ever compiled into your app.
Support is the bill you pay after you ship. So the docs live in the same workspace as the release, and what still reaches you arrives triaged.
Nine articles, nine folders.The folder column is the structure your readers browse on the public site — you are not maintaining two trees.
Folders and articles you write here, or import straight from Markdown with a preview first. Attach an article to the changelog post it explains — up to four links per article — so the answer is already sitting beside the release that raised the question.
An article can also point at a roadmap item, a feature request, or a URL you host somewhere else.
Some of them will write in anyway.
Messages sent from the widget land in one inbox, tagged by how far the sender is verified. Bodies are encrypted at rest with a key version, every action is written to an audit log, and the export drops the email address.
Each message moves
Exporting is itself an audited event — the row says who exported it, and when.
Hosted public site
See a live one — Releaseo runs on itChangelog, roadmap, feature requests and a help centre, on your own domain and in your brand. Not a widget in the corner of your app — an address you can put in an email.
This is the customer’s view.Not the dashboard. This is the page your users land on, search and subscribe to — published from the editor your team works in.
Domain
Logo, colours, fonts and cover art, on a domain your customers already trust. Your own domain comes with Pro; before that it is a releaseo.io subdomain.
Templates
Four boards, their four detail pages and the idea form. Pick a template once and it dresses every one of them — you are not styling nine pages by hand.
Speed
The public site renders on its own servers, so none of it is added to your product's bundle and none of it slows your app down.
Free plan, one script tag, and a loop that finishes itself. CRPTON already runs on it — join them.