Releaseo
Start free

Releaseo overview: every release communication surface, explained

How Releaseo's surfaces fit together: changelog, in-app launches, feature requests, roadmap, help centre, inbox, segments, Monitor, widget and public site.

Releaseo is release communication for SaaS teams. You publish a release once, and it reaches the people it was built for: inside your product through the widget, on your own public site, and in Slack, Discord or email. The votes, requests and messages that come back land in the same workspace, so when you ship one of them, Releaseo can tell the people who asked for it.

This guide walks the whole footprint, surface by surface, and links to the docs page for each one.

One workspace, twelve surfaces

Everything below is one product and one install. Nothing is a separate plugin.

  1. Changelog. Write the release note once, from a post template. The same post lands in the widget, on your public site and in Slack.
  2. Roadmap. Columns you name yourself, and visibility set per item, not per board. Internal-only items never render publicly.
  3. In-app Launches. 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 changelog post it came from. See In-app Launches.
  4. Feature Requests. Ideas arrive from the widget. You approve what becomes public, and the votes do the sorting.
  5. Help Center. Folders and articles, published to your public site: the answers your inbox keeps repeating.
  6. Contact Inbox. Private messages from the widget, encrypted at rest.
  7. Users and Segments. 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.
  8. Notification Triggers. Post to Slack or Discord when something happens: a built-in Releaseo moment, or an event you define yourself.
  9. Static Data. The vocabulary everything else uses: your own statuses, categories and label groups, defined once.
  10. Monitor. Watch a business-critical process one step at a time, such as checkout, signup or a data import. Your backend reports each step with a single HTTP call, and Releaseo turns the calls into a live funnel, a run timeline and a Slack or Discord alert when a step fails. See Monitor.
  11. Widget. One script tag, 2,530 bytes gzipped. The UI runs in an iframe, so it never enters your bundle and sets no cookies. See the widget guide.
  12. Public Site. Your changelog, roadmap, feedback board and help centre on a hosted address, built from 16 templates. See Hosted public site.

How the loop closes

The product exists to close one loop:

  1. Publish. A release note goes out once and appears in the widget, on the public site and in the channels you connected.
  2. Collect. Feature requests, votes, follows on roadmap items and private contact messages come back into the same workspace.
  3. Ship. You move the roadmap item to its shipped column and publish the release.
  4. Tell the people who asked. With the GitHub and SMTP path connected, Releaseo tells the voters and followers already attached to that roadmap item that the work shipped.

The Free plan starts the loop: publishing in-app and collecting votes, requests and replies. Closing it is a Pro capability. The pricing page lays out which plan carries which step.

Where a release shows up

  • Inside your product. The widget opens from its own launcher or from any button you already have, and shows the changelog, announcements, feature requests, roadmap, contact form and a Home Hub with quick links. In-app launches render on your page itself, outside the widget iframe.
  • On your own site. The hosted public site is provisioned at your-brand.releaseo.io when you turn it on. A custom domain is a Pro feature. Sections, template, branding, SEO settings and indexing preference are all set from the dashboard, and edits stay in a draft until you publish.
  • In your team’s channels. Slack and Discord receive releases as you publish them. PostHog receives product events. Signed webhooks carry everything else to destinations you wire yourself. See Integrations.

Installing it

The fastest path is two script tags, no build step, described in the CDN quick start. Teams with a build step install @releaseo/sdk from npm and call releaseo.init(); the compatible runtime loads from the Releaseo CDN, so runtime fixes arrive without a reinstall. There are headless adapters for React and Vue, and a version-pinned @releaseo/sdk-core for applications that must bundle the runtime themselves. Every method on window.releaseo is listed in the SDK API reference.

Hosting, privacy and data

  • Hosting is in the EU by default, with US, UK or UAE regional hosting available on request. Releaseo confirms in writing which region a workspace sits in.
  • Contact-inbox messages are encrypted at rest.
  • The widget sets no cookies, and there is a GDPR erasure API for deleting a single end user on request.
  • The Privacy Policy is the full account.

What it costs

Four flat plans, priced per workspace rather than per seat: Free at $0, Starter at $19, Pro at $49 and Growth at $99 a month. Paying yearly gives two months free. Every first paid subscription carries a 30-day money-back guarantee. The pricing page has the comparison table and the FAQ.

Where to go next

  • Product: every surface, with screenshots.
  • Developers: the install and the API, written for engineers.
  • Docs: installation, packages, the API reference and each product surface.
  • Positioning: what Releaseo is, who it is for and where it deliberately stops.