Everything a changelog
actually needs.
Six product surfaces, one platform. Below is what each one does and why it’s built that way.
Pull from where you ship.
Authorize once, sync on demand, never get surprised by a polling job. We currently connect to JIRA Cloud, GitHub, Bitbucket Cloud, and Markdown files committed to a Bitbucket repo. Each source is its own button - your team chooses when releases become entries.
- JIRA fix versions → entries (issues grouped by type)
- GitHub Releases → entries (one per release, body rendered from markdown)
- Bitbucket tags → entries (one per tag, dated by commit)
- Bitbucket Markdown → entries (frontmatter + body)
- Tokens AES-256-GCM encrypted at rest
- Token refresh on Bitbucket; reconnect flow on JIRA
- Per-sync history + error surfaces
A page people actually visit.
Every workspace gets a clean public changelog and a sidebar-driven guides site at {slug}.usedrumroll.com. Five built-in themes, custom logo + favicon + tagline, optional custom domain (after we deploy). Looks like a SaaS landing page, behaves like a SaaS marketing site.
- Public changelog with date column + tag chips
- Public guides with tree-nav sidebar
- Five themes: default, light, dark, ocean, sunset
- Custom branding: logo, favicon, tagline
- Custom domains via Cloudflare for SaaS (post-deploy)
- Per-page favicon + OG metadata
Drop it into your own app.
A 5 KB IIFE, served from app.usedrumroll.com/embed.js. Add one script tag and a target div, get the latest entries themed to your brand. Vanilla JS, no framework conflicts, no iframe required. CORS handled. Async-loaded so it never blocks your page.
- 5 KB raw / 2 KB gzipped
- Vanilla JS - works inside React, Vue, Webflow, anything
- Theme-aware (light/dark/auto via data-theme)
- Configurable via data-* attributes (workspace, target, limit)
- Iframe alternative at /embed/changelog with frame-ancestors *
- CORS + cache headers tuned for performance
Write here, or in your repo.
Compose guides in our TipTap rich-text editor - bold, italic, headings, lists, links, code blocks. Or commit Markdown files to your repo and sync them. Both render to the same public surface. Page tree with parent / child nesting and reorder.
- TipTap editor: bold, italic, code, links, h2/h3, lists, blockquote, code block
- Page tree: nest guides under parents, reorder with up/down
- Drafts vs. published - preview before going live
- Markdown sync auto-deletes orphans on next sync
- Synced guides are read-only in app - edit in repo to update
- Frontmatter: title, slug, date, tags, status, order
Built for teams from day one.
Workspaces are first-class. Each one has its own subdomain, theme, branding, integrations, and authoring team. Clerk Organizations underneath - invite teammates, manage roles, single sign-on later.
- Clerk Organizations as the auth + tenancy backbone
- Subdomain routing via Next 16 proxy.ts
- Per-workspace theme + branding + slug
- Reserved-slug list (no acme.usedrumroll.com squatting on /admin)
- Workspace rename keeps Clerk org slug in sync