FeedLog
Self-hosted feedback boards and changelogs with built-in AI.
Tagline
Own your feedback loop.
Stop paying per user for basic feedback.
Board, roadmap, and changelog in one place.
Self-hosted feedback for Cloudflare and Vercel teams.
The self-hosted Canny replacement for teams that want ownership, not a per-user bill.
The page explicitly positions against Canny and calls out tracked-user limits, which is a strong wedge for budget-conscious SaaS teams that hate pricing tied to user growth.
The first feedback platform that bundles board, roadmap, changelog, and AI without SaaS lock-in.
FeedLog combines the full workflow instead of only one piece, and the MIT/open-source + own Postgres story differentiates it from hosted competitors.
A zero-DevOps feedback stack for Cloudflare and Vercel teams.
The deployment story is unusually specific: instant support for Cloudflare Workers, Vercel, Docker, and Postgres. That makes it appealing to modern web teams who want infrastructure they already know.
Primary user
Founders or product managers at early-stage B2B SaaS companies who want a public feedback loop without paying Canny pricing
ICP #1
Bootstrapped B2B SaaS founder with 500-5,000 active users
Pain
They’re paying for Canny or Featurebase and resenting tracked-user pricing, while still manually merging duplicate requests and writing changelogs from scratch.
Why this solves
FeedLog replaces the hosted fee with open-source self-hosting, removes tracked-user limits, and automates the two highest-friction jobs: duplicate merging and release-note drafting.
ICP #2
Product manager at a developer-tool startup with a small product team
Pain
They need a transparent board-roadmap-changelog workflow, but don’t want another SaaS that stores customer feedback and roadmap data in a vendor database.
Why this solves
FeedLog keeps feedback, votes, and roadmap state inside their own Postgres while giving them the board, roadmap, and changelog workflow in one system.
ICP #3
Technical founder who wants a branded feedback portal embedded in their product
Pain
They need a feedback widget and branded UI, but don’t want to wait on a custom build or accept a rigid SaaS template.
Why this solves
FeedLog already offers a public feedback board and has a planned framework-agnostic Web Component widget, plus the MIT license means they can fork and customize it.
Strengths
- +The positioning is sharp and differentiated: self-hosted, open-source, MIT license, and zero SaaS tax all show up immediately.
- +The feature stack is concrete and credible, especially the semantic duplicate detection and AI changelog assistant.
- +The comparison table makes the competitive story easy to understand in one glance.
Weaknesses
- −The page leans too hard on anti-Canny messaging and under-explains why FeedLog is better for day-to-day workflow beyond price.
- −The AI story is interesting, but the visual proof is thin; there’s no clear demo of the semantic merge or changelog output quality.
- −There’s too much infrastructure language for non-technical buyers; terms like Workers, Vercel, Docker, and pgvector can scare off product managers who just want a board.
- −The product’s most compelling promise - own your feedback loop - is diluted by too many deployment options and technical details.
- −The universal widget is listed as coming soon, which weakens the “deploy anywhere” story unless it’s framed more carefully.
- −The current page doesn’t speak enough to migration pain from Canny/Featurebase beyond a vague CSV import mention.
Fix these
- Add a 30-second product demo showing feedback submission, duplicate detection, merging, and AI changelog generation end-to-end.
- Create a dedicated migration section for Canny and Featurebase users with exact steps, supported exports, and a stronger promise around switching cost reduction.
- Split messaging into two paths: a simple no-code cloud version for non-technical teams and a self-hosted technical path for engineers.
- Replace some infrastructure jargon with outcome language like 'no per-user billing,' 'no vendor lock-in,' and 'feedback, roadmap, and changelog in one place.'
- Add social proof or real usage examples from specific SaaS use cases, because the current page has no credibility layer beyond feature claims.
Drop-in replacement copy
Headline
Own your feedback loop
Self-hosted boards, roadmap, and changelog with AI built in.
Kill per-user pricing
Run your feedback system on your own infrastructure instead of paying another monthly bill that grows with your product. FeedLog gives you the same core workflow without the tracked-user tax.
Keep feedback, roadmap, and changelog together
Users submit ideas, vote, comment, and see progress in one place. Your team moves requests from Open to Planned to In Progress, then publishes changelogs linked back to the original feedback.
Let AI handle the boring parts
FeedLog suggests similar requests while people type, so duplicates get caught early. It can also draft changelog posts in a writing style you choose, which saves time every release.
Deploy where your stack already lives
Use Cloudflare Workers, Vercel, Docker, or your own Postgres setup. FeedLog fits technical teams that want control, portability, and data ownership from day one.
FAQ
Is FeedLog a replacement for Canny?
Yes. It covers the core workflow: public feedback board, voting, roadmap, changelog, and AI helpers. The main difference is that you own the infrastructure and database.
Do I need to be technical to use it?
No for the hosted-style experience, yes for self-hosting. The product is designed so founders and PMs can use the workflow, while technical teams can deploy it where they want.
Can I import existing feedback?
Yes, migration is a core use case. The goal is to make switching from tools like Canny or Featurebase feel like a move, not a rebuild.
What does the AI actually do?
It suggests similar posts as feedback is being written, and it can generate changelog drafts from your releases. It is meant to remove repetitive work, not replace product judgment.
What stack does it work with?
FeedLog can run on Cloudflare Workers, Vercel, or Docker, and it uses your own PostgreSQL database. If you want the AI features, pgvector support is available for semantic matching.
Canny bills get worse with growth. FeedLog is self-hosted feedback boards + roadmap + changelog, with AI duplicate detection and release-note drafting. Own the data. Kill tracked-user pricing. Ship updates faster.
Stop overpaying for feedback boards. I built FeedLog: an open-source, self-hosted alternative for SaaS teams who want feedback, roadmap, and changelog in their own stack. MIT licensed. Own your Postgres. No SaaS tax.
Built duplicate detection in the browser. As people type a request, FeedLog suggests similar posts using semantic matching. Goal: fewer messy boards, less manual triage, and way less "we already have this" work.
Watch AI write release notes. FeedLog turns product changes into a changelog draft in your writing style, linked back to source feedback. Less copy-paste. Less blank-page dread. More shipping.
The fastest win is obvious. Teams switching from hosted feedback tools usually care about two things: lower cost and fewer duplicate requests. FeedLog is built to solve both before the month even ends.
Tracked-user pricing is a tax. Your feedback board should not cost more because your product is growing. FeedLog gives you the same workflow, but you own the infra and the data.
Feedback, roadmap, changelog. Done. FeedLog bundles the whole loop: public board, Kanban roadmap, changelog, votes, comments, markdown, uploads, and AI helpers. One system. One database. No vendor lock-in.
I wanted this for my own stack. Cloudflare, Vercel, Docker, Postgres. No weird dependencies, no roadmap tool living in someone else’s database. So I shipped FeedLog as open source instead of another hosted bill.
Duplicate requests are pure waste. FeedLog suggests similar feedback while users type, then helps you merge the noise instead of manually sorting it later. That’s the boring work AI should actually do.
Technical founders want ownership. If your team already runs on Postgres and deploys to Vercel or Cloudflare, FeedLog fits the way you work instead of forcing another SaaS portal into the stack.
Angle: self-hosted replacement for Canny and Featurebase
Most feedback tools charge you for growth. That never made sense to me. If your product gets more users, your board gets more useful. Why should the bill get worse at the same time? I built FeedLog for teams that want a public feedback loop without the SaaS tax. It gives you: - a feedback board with voting and threaded comments - a roadmap in Kanban form - a changelog with reactions and links back to source feedback - AI duplicate detection and changelog drafting The bigger point is ownership. Your feedback, roadmap state, and release history live in your own infrastructure. Your team controls the data. Your users get a clean workflow. If you’ve been tolerating Canny or Featurebase because switching feels annoying, I’d love to hear what’s blocking you: migration, setup, or just inertia.
Angle: AI that removes real product ops pain
A lot of AI features are just decoration. I wanted FeedLog’s AI to do boring work that product teams actually hate. Two places stood out immediately: 1. Duplicate feedback People submit the same idea in slightly different words. FeedLog suggests similar posts while they type, so you reduce clutter before it lands in the queue. 2. Changelog writing Teams ship something useful, then spend 20 minutes turning it into release notes. FeedLog can draft a changelog entry in the style you choose and link it back to the original request. That’s the kind of AI I care about: - less manual triage - less empty-page writing - less time spent copy-pasting between tools The goal isn’t to make feedback software feel futuristic. It’s to make the feedback loop smaller, cleaner, and easier to run every week. If you’re a founder or PM, I’d love to know: which part of your feedback workflow wastes the most time today?
Angle: built for modern technical teams who want control
There’s a specific kind of team I built FeedLog for. They ship on Vercel, Cloudflare, or Docker. They already have Postgres. They don’t want another SaaS storing customer feedback somewhere else. They want: - a branded public feedback board - roadmap status in one place - changelogs they can publish fast - data they own So FeedLog stays close to that reality. It’s open source. It supports self-hosting. It works with your own Postgres, including pgvector for the AI pieces. I think this matters more than people admit. Once a product is public, feedback becomes part of your product surface area. It should be as controllable as the rest of your stack. Curious: do you prefer managed tools for this, or owning it yourself?
Tagline
Self-hosted feedback boards with AI
Description
FeedLog is an open-source feedback board, roadmap, and changelog for SaaS teams. Run it on your own infrastructure, keep data in your Postgres, and use AI for duplicate detection and changelog drafting.
Maker's first comment
I built FeedLog because I kept seeing the same pattern: teams would pay for feedback software, then resent the bill as soon as their product grew. That felt backwards. The more your product matters, the more feedback you get, and the more expensive the tool becomes. FeedLog started as a way to fix that for teams like mine: founders, PMs, and technical operators who want a public feedback loop without handing the whole thing to a vendor. I wanted the board, roadmap, and changelog to live in the same system, on infrastructure the team actually controls. The AI pieces came from the same frustration. Duplicate requests are tedious to merge. Changelog writing gets pushed to the side. So I built semantic duplicate detection and an assistant that can draft release notes in a chosen style. I’d love feedback on two things in particular: whether the self-hosted angle is strong enough to switch, and whether the AI workflows feel useful instead of gimmicky.
Pinned maker comment
I’d especially love feedback from people who currently use Canny, Featurebase, Fider, Upvoty, or Nolt: what would need to be true for you to switch?
Meta
Paying per user for feedback?
Hypothesis: bootstrapped SaaS founders with 500-5,000 active users are tired of tracked-user pricing and manual duplicate merging. FeedLog is a self-hosted feedback board, roadmap, and changelog with AI duplicate detection and changelog drafting. Own the data. Cut the SaaS tax.
Google Search
Self-hosted Canny alternative
Hypothesis: people searching for Canny alternatives want lower cost, data ownership, and a simpler migration path. FeedLog gives you a public feedback board, roadmap, changelog, and AI helpers in your own infrastructure. No tracked-user bills. No vendor lock-in.
Reddit Promoted
We stopped paying for feedback software
Hypothesis: indie founders and technical PMs in r/indiehackers and r/SaaS want a credible self-hosted replacement for paid feedback tools. FeedLog is open-source, MIT licensed, and runs on your own Postgres. It handles voting, roadmap statuses, changelogs, duplicate detection, and AI release-note drafts.
Subreddits
r/indiehackers
Share the build story: why self-hosted feedback tooling exists, how you replaced tracked-user pricing, and what AI does beyond hype.
Rules: No pure promo. Lead with a real lesson, numbers if you have them, and ask for feedback.
r/SaaS
Talk about feedback ops for SaaS teams: handling duplicates, publishing changelogs, and owning customer data.
Rules: Self-promo is heavily scrutinized. Frame it as a discussion or teardown, not an ad.
r/SideProject
Show the product demo and the tech stack: self-hosted board, roadmap, changelog, AI duplicate detection.
Rules: Share what you built and how, and be transparent that it’s your product.
r/microsaas
Target bootstrapped founders who feel pricing pain from user-based tools and want a lighter stack.
Rules: Keep it practical, mention costs and tradeoffs, avoid hype, and answer comments quickly.
r/EntrepreneurRideAlong
Document the launch journey and the reason FeedLog exists: replacing expensive hosted feedback tools.
Rules: Posts should be journey-oriented, not just product drops; engage in comments with substance.
Communities
Post a build-in-public thread about replacing Canny-style pricing, then follow up with a concrete demo and lessons learned.
Start engaging 1-2 weeks before launch on similar maker launches, then ask for specific product feedback instead of generic support.
Share the technical angle only if you can make it useful: self-hosting, Postgres, Cloudflare/Vercel deployment, and what you learned.
The SaaS Club
Look for founder/operator Slack groups where people discuss churn, pricing, and product ops; contribute to threads before mentioning FeedLog.
Cold outreach template
Hey {firstName} - noticed {context}. If you’re using a hosted feedback tool, FeedLog might be useful: self-hosted feedback boards, roadmap, changelog, and AI duplicate detection. If you want, I can send a 2-minute setup demo.
Product Hunt timing
Launch on Tuesday at 12:01am Pacific Time. That gives you the full US workday for product-led traffic, catches Europe in the morning, and avoids the weekend trough when founders are offline.
Indie Hackers post ideas
- 01I replaced a paid feedback tool with self-hosted open source
- 02How I built semantic duplicate detection for feature requests
- 03What actually matters in a feedback board migration from Canny
Competitor alternatives
Current tone of voice
Direct, anti-SaaS, and founder-friendly with a slightly rebellious edge; for example, "Zero SaaS tax" and "Stop overpaying for basic feedback boards."
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique