Feedback board
Users submit ideas and vote — no account needed. Organise by category and status, and reply with an owner badge.
Changelog · Feedback · Uptime
Feedfast gives every project a public hub: release notes, a feedback board people actually vote on, and a status page that stays honest. Canny + Instatus without the enterprise bloat.
Free forever for one project. Pro is $9/mo — one price, no seats.
Overview
Every card opens its module — try Feedback, then vote on something.
Most teams stitch these together from three products. They belong on one page.
Users submit ideas and vote — no account needed. Organise by category and status, and reply with an owner badge.
14 Aug 2026
Scheduled maintenance windows
Write in markdown, publish to a public page, an RSS feed and an embeddable widget. Tags for New, Improved and Fixed.
HTTP checks on a schedule, incidents confirmed over two failures, email alerts, and a status page your users can subscribe to.
Your hub page is the home for all of this — but nobody should have to visit it. Put the pieces on your own site, or let an agent drive them.
One script, then place what you want where you want it: a feedback button on your own markup, an uptime bar in the footer, changelog entries as cards or an inline list.
→ publish_changelog
project: "acme"
title: "Webhooks v2"
tags: ["New"]
← published
feedfa.st/p/acme/changelog/webhooks-v2
Connect Claude or any MCP client and let it publish release notes, schedule maintenance, and read your board and uptime — through a scoped API key you can make read-only.
Both are included on every plan, Free as well as Pro. Read the docs.
Feedback becomes a roadmap, the roadmap becomes a changelog, the changelog brings people back to leave more feedback.
Someone requests it
Feedback board
You mark it Planned
Status changes
You ship it
One click → changelog
Everyone finds out
Widget, RSS, email
Scheduled maintenance
Announce planned downtime. Incidents are suppressed and uptime maths skip the window, so a migration doesn't look like an outage.
Voting without accounts
One click to upvote. No sign-up wall between your users and their opinion.
RSS for everything
Changelog and status both publish real feeds, so anyone can follow along from a reader without an email address.
Times are stored in UTC and shown where they belong. Your dashboard uses your zone. Visitors see their own, with a toggle back to yours. Emails always carry the offset — never a bare “02:00”.
Maintenance window, three ways:
Tue 20 Aug, 02:00–03:00 (UTC)
Tue 20 Aug, 05:00–06:00 (UTC+3)
Mon 19 Aug, 19:00–20:00 PDT (UTC-7)
Including the two where the answer is no.
No. They can post an idea, vote and comment without signing up — email is optional and only used so their votes follow them between devices. That is the main reason boards here fill up when a form on your site doesn't.
Both, and you choose. Every project gets a public hub page, and one script tag lets you put the same things inside your own app: a feedback button on your own markup, an uptime bar, changelog entries, and a floating What's new badge with an unread dot. The widgets are styled from your accent colour and use your own logo.
Mostly that it's one product, one bill and one login instead of two or three — and that the modules are connected. Marking a request Done pre-fills the changelog entry, publishing it notifies your users through the widget, and the person who asked gets a public reply linking to the release. That loop is the thing separate tools can't do.
One project with the full product: the feedback board, 15 changelog entries, one monitor checked every five minutes, a public status page with up to 25 subscribers, every widget, the REST API and the MCP server. It's free forever, not a trial — the only thing you'd upgrade for is scale and taking our badge off.
Nothing is deleted. Extra projects and monitors go read-only or paused, your data stays, and everything comes back if you upgrade again. A cancelled subscription also keeps Pro until the end of the period you already paid for.
Yes — Feedfast ships an MCP server, so your assistant can read the feedback board, publish changelog entries, schedule maintenance and check uptime. It has no access to your code or your deploys; it's a client of the same REST API you could call with curl, and you can scope its key read-only.
Not yet. Public pages live at feedfa.st/p/your-slug, and custom domains are on the backlog rather than shipped. If a status page on status.yourcompany.com is a hard requirement today, this isn't the right tool for you yet.
Not yet — a project has a single owner, and team members are on the backlog. In practice that suits a solo maker or a small team happy to share one login, and it's a poor fit if several people need their own access and an audit trail.
About five minutes: sign in with Google, GitHub or a magic link, name a project, and you have a public hub page. Pasting the widget script and pointing a monitor at your site is another couple of minutes. Pro is $9 a month or $79 a year when you need it.
Something not covered? The docs go into detail, and the pricing page lists every limit.
Sign in with a magic link, name your project, publish something. That's the whole setup.
Start freeA note about cookies
We use a couple of cookies to keep you signed in, and optionally one to remember your timezone. No analytics, no advertising, nothing shared with anyone.