# Feedock

> Feedock turns user feedback into shipped features. It combines a feedback board, public roadmap, and changelog with the execution layer (tasks, milestones, Git integration) in one workspace, built for solo founders and teams of 2-5. A Featurebase or Canny alternative with execution built in.

Feedback becomes a roadmap, the roadmap becomes tasks, and shipped work becomes a changelog that automatically notifies the people who asked. AI drafts the busywork (deduping similar requests, scaffolding tasks, drafting changelog entries); a human always approves before anything publishes.

For a longer reference with the full definition, every FAQ answer, pricing, and how Feedock compares — all inline — see https://feedock.com/llms-full.txt.

## Main pages

- [Home](https://feedock.com/): what Feedock is and how the feedback-to-shipped loop works
- [Pricing](https://feedock.com/pricing): flat monthly plans; the feedback board, roadmap, and changelog are free, AI is the paid tier
- [Developer docs](https://feedock.com/developers): the MCP server (AI agents can drive the whole loop) and the public REST API
- [Slack integration](https://feedock.com/integrations/slack): Send Feedock events to Slack: new feedback, status changes, and published changelog entries land in your channel the moment they happen. Connect in one click.
- [Blog](https://feedock.com/blog): guides on feedback management, public roadmaps, changelogs, and building in public

## Blog posts

- [Time Tracking for Small Teams Without a Timesheet](https://feedock.com/blog/time-tracking-small-teams): Most time tracking hands a small team a second list of projects and tasks to keep in sync. Track the hours on the work you already have instead.
- [Visual Planning Boards for Small Product Teams](https://feedock.com/blog/visual-planning-board-product-teams): A visual planning board is where ideas get written down and connected before they become work. How to run one, and what to do with the notes that survive.
- [Introducing Feedock: from feedback to shipped, in one workspace](https://feedock.com/blog/introducing-feedock): Feedback tools collect requests and stop there. Execution tools ship work but never hear the request. Feedock is the loop that connects them, from a user's ask to the update that tells them it's live.
- [7 Best Featurebase Alternatives for Tiny Teams (2026)](https://feedock.com/blog/featurebase-alternatives): Comparing Featurebase alternatives for solo founders and tiny teams. Six honest options by category, plus how to pick feedback plus execution in one place.
- [The loop is the product](https://feedock.com/blog/the-loop-is-the-product): Compare Feedock feature by feature and you'll always find a box it ticks less thoroughly. That's the wrong lens. Its real feature is the loop that runs between the features, and here's how it flows.
- [7 Canny Alternatives for Tiny Teams in 2026](https://feedock.com/blog/canny-alternatives): Comparing Canny alternatives for small teams? Here are 7 honest options, why people switch, and how to pick the feedback tool that fits how you ship.
- [AI that drafts, humans that ship](https://feedock.com/blog/ai-drafts-humans-ship): Feedock's AI does the busywork around the loop: deduping requests, scaffolding tasks, drafting changelogs. What it never does is publish for you. Here's where the line sits, and why we drew it there.
- [How to Build a Public Product Roadmap People Follow](https://feedock.com/blog/how-to-build-a-public-roadmap): Build a public product roadmap people actually follow: simple columns, what stays private, tying items to voters, and closing the loop when you ship.
- [How to Write a Changelog Users Actually Read](https://feedock.com/blog/how-to-write-a-changelog): Write a changelog people actually read: what each entry needs, the right tone and cadence, clear categories, and how to notify the folks who asked.
- [How to Collect User Feedback Without Annoying Anyone](https://feedock.com/blog/how-to-collect-user-feedback-saas): Collect user feedback for your SaaS without friction: account-less submission, the right channels, de-duplicating requests, and a prioritized list.
- [Building in Public: A Playbook for Solo Founders](https://feedock.com/blog/building-in-public-playbook): A practical building in public playbook for solo founders: public roadmaps, changelogs, notifying voters, and a cadence you can actually keep.
- [Feature Request Management for Tiny Teams: A Simple Guide](https://feedock.com/blog/feature-request-management): A simple feature request management system for tiny teams: capture, dedupe, prioritize, convert to real work, and close the loop without Jira-heavy process.
- [How to Close the Feedback Loop](https://feedock.com/blog/close-the-feedback-loop): Learn what it means to close the feedback loop, why telling people what shipped builds trust, and the operational steps to do it without dropping requests.
- [How to Prioritize Your Product Roadmap (Small Teams)](https://feedock.com/blog/prioritize-product-roadmap): Prioritize your product roadmap when everything feels urgent. Lightweight signals over heavy frameworks, built for solo founders and tiny teams.
- [AI for Product Feedback: Triage Without Losing Control](https://feedock.com/blog/ai-product-feedback): A practical guide to using AI for product feedback: what it should draft, what it must never decide, and the guardrails that keep humans in charge.

## Key facts

- End users never need an account: they submit, vote, and comment with just an email, verified by a magic link.
- Three ways to embed: a hosted portal, a React SDK, or a one-script widget rendered in a Shadow DOM.
- Git integration: GitHub, GitLab, Bitbucket, and Gitea. PRs and commits referencing a task move it across the board automatically.
- AI assists, humans approve: dedupe/theming, task scaffolding, and changelog drafts are always reviewed before publishing.
- An MCP server (@feedock/mcp) exposes the workspace to AI agents: 23 tools covering feedback, roadmap, tasks, milestones, docs, and changelog.
- Publishing a changelog entry emails exactly the voters and requesters who asked for that change, plus subscribers (double opt-in).

## Pricing

Flat monthly plans anchored to the owning user (no per-seat surprises). The feedback board, public roadmap, changelog, tasks, milestones, and Git integration are on every plan; AI generation, white-label, custom domain, and team notification channels are the paid tiers.

- Free (Free): $0/month — 1 project, 2 seats, all the core surfaces.
- Pro: $25/month — 3 projects, 3 seats, AI, white-label, custom domain, team channels.
- Studio: $59/month — 5 projects, 5 seats, everything in Pro at a higher allowance.
- Every new account starts on a 14-day Pro trial, then lapses to Free by itself (no card required).

## How it compares

- vs Featurebase and Canny: both are strong feedback, roadmap, and changelog hubs, but they stop at the roadmap. Feedock adds the execution layer (tasks, milestones, Git-driven progress) in the same workspace, so a request travels from feedback to shipped without re-entry.
- vs Linear and Jira: those are strong execution systems but not public feedback or changelog hubs. Feedock pairs a public feedback board, roadmap, and changelog with lightweight execution built for solo founders and teams of 2-5.
- vs Nolt, Frill, and Upvoty: lighter voting boards that cover the public surfaces well; Feedock is the fuller workspace when you also want tasks and a changelog that notifies the people who asked.

## Contact

- Legal and privacy: legal@feedock.com
- GitHub: https://github.com/feedockapp