Fdback Alternative: a Flat Board With MCP, or a Human Decision
On 2026-10-02 fdback.io showed Free $0/mo, Pro $15/mo, Enterprise $30/mo. MCP is on Pro and can edit feedback, comments, votes, and changelogs. A named approval gate is not shown. Feedjolt is a HITL voting board.
Looking for an fdback alternative when the job is a public voting board plus MCP, and you want a person to decide what gets published? Fdback (fdback.io) is a hosted feedback board: people submit and vote, a public roadmap shows what is next, and a changelog closes the loop. Feedjolt is a hosted human-in-the-loop (HITL) voting board with public feedback, voting, a public roadmap, a changelog, and MCP so an agent can propose and a human decides. This page is that dated plan walk, not a second copy of Fdback. Homepage only: https://www.feedjolt.com/?utm_source=blog&utm_medium=organic&utm_campaign=seo-fdback-alternative.
We checked these on 2026-10-02 (Madrid): fdback.io (prices in the #pricing section; there is no separate /pricing page), the MCP page, the Canny compare page, and the blog marked Updated August 13, 2026. The docs home was not a price source. Re-open the cards the week you buy. Also: public roadmap tools and closing the loop.
What Fdback optimizes for
An fdback.io feedback board is hosted. People post requests, bugs, and questions. Others vote. A public roadmap shows what is next. A changelog announces what shipped. Hero that day: “The simplest way to collect product feedback.” Steps: collect, plan on a roadmap they call drag-and-drop, close the loop with a changelog. Tabs: board, widget, integrations, updates.
On those pages the product is one board for requests, bugs, and questions; votes; a public roadmap they call drag-and-drop; a changelog; a widget; and homepage integrations named Slack, Linear, Asana, Jira, and Zapier. JSON-LD names the organization “Fdback”, https://fdback.io, [email protected], BusinessApplication, operating system Web. A legal suffix, a founded year, and a copyright line are not on the page. The FAQ says, in their words: “No VC funding, no enterprise sales team, no bloated overhead. Just one developer focused on building a great product at a fair price.”
The homepage describes a widget, not a native mobile SDK. The August 13 blog adds “React component included.” That is a widget and a React component, not an iOS or Android SDK. A native SDK line is not on the pages opened that day. “Powering feedback at” names VFAT, Arya, KeyAuth, and VaultCord. The vote counts in the hero are a demo graphic.
The homepage integration list (Slack, Linear, Asana, Jira, Zapier) and the August 13 blog list are separate. “Basic” versus “Advanced” is not defined for a named tool or an AI behavior. A plan is named for Slack, Jira, or auto-tagging only when the page being quoted names that plan.
Fdback is its own product
Homepage JSON-LD names Fdback at https://fdback.io. The homepage, the MCP page, and the Canny compare page do not mention Rapidr, ProductLift, FeatureOS, Hellonext, FeedBear, or Feature Upvote. UserVoice appears as a footer compare link, not as the company name. Rapidr is a different product, already covered in the Rapidr alternative post. See how to choose a feedback board.
What the homepage pricing section showed on 2026-10-02
Prices below are the homepage cards. There is no separate /pricing page. The cards live on the homepage at https://fdback.io/#pricing. JSON-LD offers on the same page: Free price 0 USD, Pro price 15 USD, Enterprise price 30 USD. No billing interval is in those offers. Visible cards that day:
- Free: $0 /mo — “For early-stage teams.”
- Pro: $15 /mo — “Most popular.”
- Enterprise: $30 /mo — the plan button also says “Unlimited everything. No constraints.”
The meta description that day includes “Flat $15/mo pricing with a free plan — no per-user fees,” after the collect, vote, roadmap, and changelog sentence. There is no billing-commitment line and no period toggle. Each card ends in “/mo”. Commitment length is unknown. The suffix is not a second price. $15 is the Pro card on 2026-10-02, not a locked contract. Re-open the cards the week you buy.
Free vs Pro vs Enterprise is a workspace, branding, and API gate
The Free card says “Perfect for side projects and validation.” Its bullets are unlimited posts, unlimited users, unlimited voters, Basic AI Features, Basic Integrations, and 1 Workspace. That $0 card is a real board, with unlimited posts, users, and voters.
The Pro card says “For teams serious about building what users want.” It is “Everything in free,” plus 10 workspaces, custom domain, remove branding, API access, Advanced AI Features, and Advanced Integrations. The $15 is that day’s card.
The Enterprise headline says “Unlimited everything. No constraints.” The bullets under it are narrower: “Everything in Pro,” unlimited workspaces, “SSO (Coming Soon),” “New features in advance,” dedicated support, and unlimited team members. SSO on Enterprise is marked Coming Soon, not a feature already shipping.
A team-member cap on Free and Pro is not on the cards. Only Enterprise lists “Unlimited team members.” No seat count is printed for Free or Pro. The Free card already says unlimited users and unlimited voters. The gate that is printed is workspaces, branding, custom domain, API access, and, on the MCP page, the remote server on Pro.
Trial, card, refund, and the custom domain FAQ
The homepage pricing cards do not say “free trial,” “no credit card,” or a refund window. Those lines are absent from the pricing section. The Canny compare page, opened the same day, does say “Free plan to start. No credit card.” and “Free plan · No credit card required.” That “no credit card” wording is on the compare page, not on the pricing cards.
The homepage FAQ answers “Can I use my own domain?” with “Yes. Connect your custom domain and your feedback portal lives at feedback.yourdomain.com.” The FAQ does not name a plan. Custom domain and “Remove branding” are both on the Pro card. Custom domain is not on the Free card. “Free plan to start” is not the same as a custom domain on Free.
The homepage FAQ also says: “Mark feedback as completed and everyone who voted gets an email automatically. You can also link it to a changelog entry for a public announcement.” The updates tab says the same kind of thing: publish an update, and everyone who voted gets notified. That email-on-complete line is Fdback’s claim, not a Feedjolt feature.
Remote MCP is on Pro, and it can write
fdback.io/mcp is titled “MCP Server — Connect AI Tools to Your Feedback Board.” In their words, it is a remote server for Claude, Cursor, Codex, or Gemini. “Triage feedback, draft changelogs, and summarize what users want.” Setup is an API key under Settings → API, endpoint https://app.fdback.io/api/mcp, a bearer token, and Streamable HTTP. Clients named on the page: Claude Code, Claude Desktop via mcp-remote, Cursor, Codex, Gemini, and “any MCP client.”
The plan answer, in their words: “What plan do I need for MCP access? MCP access is part of the Pro plan ($15/month), which includes API access.” That matches the Pro card’s “API access.” MCP is on Pro, not on Free. The $15 is the same day’s Pro card. The billing interval is still not on the page.
Tools in the examples are list_feedback, update_feedback, create_changelog, publish_changelog, list_filters, and list_comments. The page also says the model can read boards, find duplicates, update statuses and tags, write a changelog in markdown, read threads, post comments, vote, and mark requests shipped. “Safe by design. No delete, archive, or merge tools exist on the server. The API key acts as you — your workspace role bounds every call.” The FAQ limits writes to creating and editing feedback, comments, votes, and changelog entries, and says the AI cannot delete. That is the write scope.
A named approval gate is not on the MCP page. The words “human,” “HITL,” and “approve” are not there. In the ship-day example a person types “yes, publish it,” then publish_changelog runs. That is a demo transcript, not a documented setting. The Monday example closes spam and moves requests to In Review “without opening the dashboard.” Fdback has MCP on Pro, and that is not the same as a named human approval gate.
Homepage cards versus the August 13 blog
The blog says “Updated August 13, 2026.” Its Fdback paragraph says “free plan (full features, 1 workspace), then Pro at $15/month flat,” and “Nothing scales with users, seats, or feedback volume.” AI in that section is duplicate detection before submission, spam filtering, auto-tagging, and smart suggestions, with “auto-tagging on Pro.” Integrations in that section are Slack, Discord, Linear, Asana, store-review import, and webhooks for Zapier or Make. Visitors, they say, can vote and browse without an account on the board.
The same post says “What fdback doesn’t do”: weighted scoring matrices, user segmentation by MRR, Salesforce/HubSpot sync, or multi-level approval workflows. That line is not the MCP write scope. Fdback can say it does not sell multi-level approval and still let the API key create and edit board records.
The “full features” sentence disagrees with the 2026-10-02 cards. Free does not list custom domain, removed branding, API access, or advanced AI, and the MCP page puts MCP on Pro. The cards are the plan gate. The integration lists stay separate: the homepage names Jira, and the blog names Discord, store-review import, and Make, without naming Jira in that sentence. We didn’t check other vendors’ prices in that roundup for this article.
Fdback vs Canny, on Fdback’s compare page
For fdback vs canny, Fdback’s compare page is their positioning, not Canny’s price on 2026-10-02. The title is “Fdback vs Canny: Flat Pricing, No Tracked Users.” We didn’t check canny.io that day. The page says “Canny details from their public pricing and docs, August 2026.” Those Canny lines are Fdback’s August 2026 claim. Canny’s price on 2026-10-02 is unknown.
In that claim, without a dollar figure carried forward as today’s price, they describe a tracked-user model, a capped free plan, a paid entry above the Pro card that rises as tracked users accumulate, custom domain on a paid Canny plan in their telling, and “Spend limits pause new feedback capture.” Their Fdback column matches the cards: “no user counting,” unlimited users and voters, domain and branding on the $15 Pro card, and “REST API, Zapier, Jira & Linear sync, MCP” on Pro. “Set up in minutes, cancel anytime.” Nearby posts on the same questions: Feedjolt vs Canny, flat-pricing Canny alternatives, and flat-price boards.
The import tile says “One-click Canny CSV import” and “2 min to import.” The steps under that tile are three: export a CSV from Canny, upload at Settings → Import, and the board is live with votes. Both descriptions are on the page. We didn’t run the import for this article, so “one click” is the tile’s label, not the only description of the steps.
What a current search covers, and what it misses
A search on 2026-10-02 for “fdback alternative” did not turn up a dedicated Fdback roundup in the results we checked. Those results were other products’ own pages, and they were not the price source. We didn’t open an iTechGuides “Fdback Pricing in 2026” snippet.
Those third-party homepages do not set the three cards next to a remote MCP server that can write. This page does: unlimited posts, users, and voters on $0; domain, branding removed, API, and MCP on Pro at $15 /mo; unlimited workspaces and Coming Soon SSO on Enterprise at $30 /mo.
Which job fits which board
| Question | Fdback, homepage cards 2026-10-02 | Feedjolt |
|---|---|---|
| Cards | Free $0 /mo, Pro $15 /mo, Enterprise $30 /mo. Billing interval unknown. No separate /pricing page | Price is not in this post |
| Free board | Unlimited posts, users, and voters. Basic AI. Basic integrations. 1 workspace | Public feedback and voting |
| Pro | 10 workspaces, custom domain, remove branding, API access. MCP page puts MCP on Pro | Custom domain here is Fdback’s Pro line |
| Enterprise | Unlimited workspaces. SSO marked Coming Soon. Dedicated support. Unlimited team members | SSO here is Fdback’s Coming Soon line |
| MCP writes | Create and edit feedback, comments, votes, and changelogs. No delete, archive, or merge. API key acts as you. Named approval gate not shown | Agents propose and a human decides |
Fdback fits when you want that hosted board: unlimited posts, users, and voters at $0, Pro when you need the domain, branding removed, the API, or remote MCP, and Enterprise for unlimited workspaces or SSO still marked Coming Soon. A hosted HITL board fits when agents should propose and a human should decide, and you do not want an API key that “acts as you” for creates and edits.
Where Feedjolt places
Feedjolt is a hosted HITL voting board: public feedback, voting, a public roadmap, a changelog, and MCP so agents can propose and a human decides. It is not a suite. Feedjolt’s price is not in this post. This post does not describe a Feedjolt custom domain, SSO, native mobile SDKs, email when something ships, or Feedjolt’s MCP tool list. The widget, the React component, and the named integrations above are on Fdback’s pages.
The $0 card is one workspace and basic AI. The $15 Pro card on 2026-10-02 adds the domain, branding removed, the API, and MCP writes, with no delete, archive, or merge tools and no named approval gate. The $30 card adds unlimited workspaces, or SSO still marked Coming Soon. Feedjolt fits when a human decides what an agent publishes. Neither is a CRM or a weighted-scoring tool on its own.
FAQ
What is a practical fdback alternative if you want a person to decide?
A practical fdback alternative is a hosted voting board where agents can propose and a person decides what is published. It is not a second copy of Fdback. Fdback already has the board, the votes, the public roadmap, the changelog, and a remote MCP server on Pro. That server can create and edit feedback, comments, votes, and changelog entries. Delete, archive, and merge tools are absent. A named approval gate is not shown, and the API key acts as you. Feedjolt is the HITL board for that decision: public feedback, voting, a roadmap, a changelog, and MCP. The $0, $15, and $30 figures are the homepage cards on 2026-10-02. The billing interval is unknown.
On fdback vs canny, what is the claim and what is the card?
Fdback vs Canny on their compare page is their positioning. The page dates the Canny details to August 2026. We didn’t check canny.io, so Canny’s price on that day is unknown. Their own column puts domain, branding, and MCP on the $15 Pro card, not on Free. The August 13 “full features” sentence on the free plan disagrees with the homepage: Free does not list custom domain, remove branding, API access, or advanced AI, and MCP is on Pro. The homepage cards are the plan gate. They also say they do not sell multi-level approval workflows. That line can sit beside an MCP server that still writes under the API key.
What does an fdback.io feedback board include on Free, and what waits?
On Free, at $0 /mo on 2026-10-02, an fdback.io feedback board includes unlimited posts, unlimited users, unlimited voters, Basic AI Features, Basic Integrations, and 1 workspace. Custom domain, remove branding, API access, advanced AI, advanced integrations, 10 workspaces, and the remote MCP server are on Pro at $15 /mo. Unlimited workspaces, dedicated support, unlimited team members, early features, and SSO marked Coming Soon are on Enterprise at $30 /mo. A team-member cap on Free and Pro is not on the cards. A trial, a card requirement, and a refund window are not on the pricing cards. “No credit card” is on the compare page. What the “/mo” suffix commits you to is not on the card.
Where to start
Pick the job before the feature list. Fdback when the $0 card is the board you want, Pro at $15 /mo on the 2026-10-02 homepage when you need the custom domain, branding removed, the API, or MCP that creates and edits feedback, comments, votes, and changelogs, and Enterprise at $30 /mo when you need unlimited workspaces or the SSO line still marked Coming Soon. Feedjolt when you want a hosted HITL voting board and a human decision. Feedjolt’s price is not in this post. The homepage is here:
https://www.feedjolt.com/?utm_source=blog&utm_medium=organic&utm_campaign=seo-fdback-alternative
