Turn user feedback into shipped features.
The feedback board, roadmap, and changelog for small teams, plus the tasks to ship them. Collect what users want, build it, and tell the people who asked.
From feedback board to changelog
Feedback, roadmap, tasks, milestones, docs, and changelog live in one workspace. Each piece feeds the next, so the loop runs itself.
Collect, vote, and triage
Account-less requests come in and convert straight onto the roadmap, where the loop starts.
A public plan that stays in sync
Now · Next · Later · Shipped. Move an item and the people who voted for it watch it progress, no status meetings.
Turn the plan into shipped work
Drag work from Backlog to Done, link PRs and commits, and progress rolls up to the roadmap automatically.
Tell the people who asked
Draft what shipped, publish, and everyone who requested it gets notified automatically.
Group the work into milestones
Planning containers whose progress is calculated from the tasks inside, not dragged by hand.
Specs that live with the work
Lightweight PRDs, tech notes, and decision logs, linked to the tasks and milestones they describe.
Plugged into where the work happens
Connect your repo and your chat. PRs move tasks, shipped work pings the right channel, no copy-paste.
Git activity moves your tasks
Open a PR and the linked task moves to In Progress; merge it and the task moves to Done, without ever sliding backward.
AI does the busywork. You hit publish.
Feedock's AI dedupes, scaffolds, and drafts, then steps back. Nothing goes public until you approve it. AI assists; humans ship.
We pointed our AI agent at Feedock through the MCP and it just ran the loop, triaging new feedback, drafting the changelog, and telling the people who asked. We approve and ship.
{
"mcpServers": {
"feedock": {
"command": "npx",
"args": [
"@feedock/mcp"
],
"env": {
"FEEDOCK_TOKEN": "fdk_live_•••••"
}
}
}
}Your feedback hub, three ways
Put your feedback board, roadmap, and changelog wherever your users are: a hosted portal on your subdomain, a React component in your app, or a one-line script on any site. Same data, your brand.
Every signal feeds the loop
Feedback, upvotes, comments, and Git activity all stream into one workspace. Feedock watches every signal from first request to shipped, so nothing worth building slips past you.
FAQ
Feedock is a product operating system for solo founders and teams of two to five. It combines a public feedback board, roadmap, and changelog with internal tasks, milestones, and docs, connected end to end: a request becomes a roadmap item, tasks move with your commits and pull requests, and the shipped work becomes a changelog entry that emails the people who asked. A Featurebase or Canny alternative with execution built in.
Solo SaaS founders, micro-SaaS builders, 2-5 person product teams, and indie hackers building in public. If you want to know what to build, why it matters, what's in progress, and what changed, without a Jira-level tool to maintain, Feedock is for you.
Those are strong at feedback, roadmap, and changelog, but they aren't execution systems. Linear and Jira are execution systems but not public feedback hubs. Feedock is the connective tissue between the two, one workspace, one loop.
No. End users stay account-less, they submit, vote, and subscribe with just an email (verified by magic link). Accounts are only for your team.
Yes, three ways. A hosted public portal, a React SDK you drop into your app, or a single-script embeddable widget that renders in a Shadow DOM. Same data, your branding.
AI assists, humans approve. It dedupes similar requests into one opportunity, scaffolds tasks and specs, and drafts changelog entries, but you always publish.
Yes. Connect GitHub, GitLab, Bitbucket, or Gitea. PRs and commits referencing a task drive its status automatically, opened moves it to In Progress, merged moves it to Done.
