ShipShipShip is a self-hosted changelog and roadmap application for small product teams that publish product updates and let their community vote on upcoming features. Built with SvelteKit and Go, it combines Markdown changelogs, a votable roadmap with a kanban planning board, emoji reactions and comments, and a documented REST API in a single Docker container backed by SQLite. It suits teams that want the update-to-feedback loop under their own control with no paid tiers.[1][2]
Quick verdict
Small product teams and individual maintainers that want a self-hosted changelog and roadmap portal benefit most from ShipShipShip. Its Markdown changelogs with images and scheduling, community voting on upcoming features, kanban planning board, emoji reactions and comments, multi-member admin dashboard with roles and audit logs, and documented REST API cover the update-to-feedback loop in one Docker container on SQLite, free under Apache-2.0 with no paid tiers. The material constraints are operations and proof: there is no managed cloud, SSO, or enterprise support documented, and no independent Reddit or G2 firsthand reports surfaced, so evaluate from the docs and a trial. If a free single-container portal under your own control matters more than peer proof, start with the Compose quickstart; if the team needs hosted SLAs or published enterprise guarantees, choose a managed feedback suite instead.[1][2][3]
Key features
Markdown changelogs Changelog posts support Markdown with images, public or private visibility per project, and scheduled publishing so releases can be prepared ahead of time.[1]
Roadmap voting Upcoming features are proposed and voted on by the community, so the most requested items rise to the top of the public roadmap.[1]
Reactions and comments Every update accepts emoji reactions and threaded comments, giving users a lightweight way to respond without writing a full post.[1]
Kanban planning board A built-in kanban board helps the team plan what ships next alongside the public-facing roadmap view.[1]
Multi-member administration Organizations support multiple members with roles, a dedicated admin dashboard, per-organization API keys, and audit logs of administrative activity.[1]
Single-container self-hosting Deployment is one Docker Compose command with a six-variable .env file, SQLite by default with optional Postgres, and a published ghcr.io image for plain Docker runs.[1]
REST API and docs A REST API at /api covers projects, posts, votes, comments, and reactions with per-organization keys, an interactive Swagger UI, and reference documentation on the official site.[1][2]
Newsletter subscriptions Visitors can subscribe to updates from the portal, so published changelogs reach followers without a separate mailing tool.[1]
Who will love it
Small product teams publishing changelogs: Markdown posts with images and scheduling plus a multi-member admin dashboard cover the weekly release-notes workflow.[1]
Maintainers gathering votes on a public roadmap: community voting plus the kanban planning board turns scattered requests into a prioritized, visible plan.[1]
Self-hosters wanting a single-container feedback portal: the Docker Compose quickstart with a SQLite default and optional Postgres fits operators who want full data control with minimal setup.[1]
Who should avoid it
Teams needing a managed cloud with SLAs face a gap: no hosted plan, pricing tier, or enterprise support program is documented, and the only hosted surface observed is a free trial demo.[1][2]
Teams requiring SSO, published data regions, or offline use face gaps: the documented login is email and password, and none of these capabilities appear on the inspected official pages.[1]
Independent review coverage is thin: targeted searches surfaced no original Reddit or G2 firsthand reports, so teams must evaluate from documentation and a trial rather than peer experience. Treat this assessment as docs-based until community evidence appears.[1][2]
Alternatives and compatibility
Conditional alternatives Teams with nobody willing to operate infrastructure fit a hosted changelog or feedback SaaS better, since ShipShipShip's advantage shows most on the self-hosted path where the team owns deployment, upgrades, and backups.[1][2]
Existing catalogue neighbours The catalogue relates ShipShipShip to Fider as a competitor; both cover self-hosted request collection and voting with a REST API, so the choice turns on changelog depth, stack fit, license tolerance, and interface preference.[1][2]
Migration paths The REST API across projects, posts, votes, comments, and reactions keeps exit options open: board content can move or sync with other product tooling rather than locking into a proprietary-only store.[1][2]
Decisive tradeoff If the team wants a free Apache-2.0 changelog and roadmap portal it can self-host this week in one container, ShipShipShip covers publishing, voting, planning, and API access with no paid tiers. If the team needs managed hosting with SLAs, SSO, or published enterprise support, choose a hosted feedback suite instead.[1][2][3]
Questions worth asking
Can you self-host ShipShipShip?
Yes. The README describes ShipShipShip as a self-hostable web application with a quickstart of git clone plus docker compose up --build -d, and a separate docker run path using the published ghcr.io image with a named volume. SQLite is the default database so no external database is required, with optional Postgres for operators that want it.[1]
How much does ShipShipShip cost per month?
Self-hosting costs nothing beyond your own infrastructure. The codebase is Apache-2.0 licensed with no paid tiers, plan gates, or commercial extensions documented on the repository, README, or official site, and the live demo is free to try. Costs checked October 2026 on the inspected official pages.[1][2]
Does ShipShipShip have an API?
A documented REST API at the /api base path covers projects, posts, votes, comments, and reactions with create, read, update, and delete operations. API keys are generated per organization from the admin dashboard, and an interactive Swagger UI is served for exploration. Rate limits and client SDKs are not documented on the inspected pages.[1][2]
Who should choose ShipShipShip over a hosted changelog service?
Teams that want a single-container changelog and roadmap portal they fully control fit best, especially small product teams and individual maintainers already comfortable with Docker. Teams that need a managed cloud with SLAs, published SSO, or peer-reviewed proof should look elsewhere: no hosted plan is documented and no independent firsthand reports surfaced during research.[1][2]
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- ShipShipShip discovery lead (openalternative.co)
community · Observed October 12, 2026
Discovery-lead directory result: lightweight, self-hostable changelog and roadmap app for product updates and voting-based feedback, built with SvelteKit and Go.
- ShipShipShip repository (GitHub)
official · Observed October 12, 2026
Repository page: GauthierNelkinsky/ShipShipShip, changelog/roadmap/feedback/voting/self-hosted tags, homepage https://shipshipship.io, Apache-2.0 license, about 60 stars and 10 forks observed.
- ShipShipShip README (repository)
official · Observed October 12, 2026
Repository README: feature table (organizations, roles, Markdown changelogs with images and scheduling, REST API with Swagger UI, roadmap voting, kanban, themes, newsletter, audit logs); Docker Compose and Docker self-hosting; SQLite default with optional Postgres; Go plus SvelteKit; Apache-2.0 license.
- ShipShipShip official site
official · Observed October 12, 2026
Official site shipshipship.io: product name and changelog/roadmap positioning with links to documentation, live demo, and GitHub source code.
- ShipShipShip documentation (official)
official · Observed October 12, 2026
Official documentation API reference: REST endpoints for projects, posts, votes, comments and reactions, API key authentication, Swagger UI, plus deployment and configuration guides.
- ShipShipShip LICENSE (repository)
official · Observed October 12, 2026
Repository LICENSE file on main: full Apache License Version 2.0 text.
- ShipShipShip releases (GitHub)
official · Observed October 12, 2026
Repository releases page: maintained line from v1.2.1 through v1.3.5, latest observed v1.3.5; no archived or deprecation notice.
Compared with these products
No explicit proprietary baseline is recorded.