What you ship, told to the people who use it.
Roadmap, changelog and wiki published from the same base your tickets arrive in. Julia writes the release notes — and asks before she publishes.
14-day trial · No card · Then a free plan
Julia, Marketing: “Write the changelog for version 2.4.”
Draft ready: CSV export, a new date filter and two fixes, in Portuguese and English. Shall I publish it to the changelog? Publish version 2.4.0 to the public changelog. Published. The entry is now on the changelog for your users.
Studio Bravo is a demo company. Made-up data.
The product, before and after
User requests are scattered across emails, tickets and chats.
Users suggest and vote on the roadmap, and you prioritize by what they ask for.
The release goes out and nobody hears about it.
Every release becomes a changelog entry, published right away or scheduled.
The documentation lives in a drive nobody updates.
The wiki is internal or public, in categories, in the same place as support.
Release notes get left for later — and later never comes.
The agent drafts the changelog and waits for your OK to publish.
From request to release, in public
Three surfaces your users see — published without building a website.
Roadmap
Show what's coming next
A public roadmap with what's being built and what comes after. Your users comment, suggest ideas and vote.
- A public board by status
- Votes and comments from users
- Suggestions for new ideas
Changelog
Announce every release
Release notes with labels and a version number, in more than one language. Publish right away or schedule them to go live later.
- A draft before publishing
- Scheduled publishing
- Reactions and email subscription
Wiki
Documentation support actually uses
An internal or public knowledge base, organized in categories. Its articles are the basis of the support agent's answers.
- Internal or public
- Organized in categories
- The source of the agent's answers
In your product
Where your users already are
Roadmap, changelog and wiki go into your site or app by iframe. On paid plans, the roadmap and changelog come without the BaseOS badge.
- Iframes for roadmap, changelog and wiki
- A public page of its own for the wiki
- No BaseOS badge on paid plans
The product, wired to support and marketing
- From wiki to supportThe support agent answers with wiki articles, and what's missing becomes a draft article.
- From changelog to marketingThe same agent that writes your campaigns writes your release notes.
- From Factory to productThe Factory has its own wiki and support stages: the product it launches already comes with them.
Modules you can switch on today
Read from the same catalog as the module store: if it's listed here, it's in the product.
- Roadmap, Changelog & Wikifree plan available
- RoadmapA public product roadmap showing what is in flight and what comes next.
- ChangelogA release changelog to announce every delivery to your users.
- WikiA knowledge base and documentation, internal or public.
Do I have to pay for a public roadmap?
No. The public roadmap and changelog are on the free plan; the wiki and voting are on paid plans.
Can the agent publish without me seeing it?
No. She saves the release notes as a draft and stops. Publishing is a separate step that waits for your OK.
Can I put it on my website?
Yes. Roadmap, changelog and wiki each have an embeddable iframe version, and the wiki also has a public page of its own.
Do the votes decide what we build?
Votes show what users ask for; the decision stays yours, and you move each item between the roadmap's statuses.
Be the owner again.Not the integrator.
Start with the area that hurts most. In 14 days you'll know whether BaseOS stays — no card, and a free plan afterward.
14-day trial · No card · Then the free plan