Flunes — Repo-aware AI feedback intake into GitHub Issues<br>English<br>Sign in

For developersBug reports and feature requests, straight into GitHub.

Stop rewriting feedback into GitHub by hand.<br>You're the developer receiving feedback. Your clients, PMs, and stakeholders submit bugs and feature requests through a simple form. Flunes turns them into ready-to-work GitHub issues in your repo. No copying, no pasting.<br>Start freeSee the product proofSee how it works<br>Permanent free tier · 1 repo free forever · No credit card required

What changes with Flunes<br>Clients, PMs, and QA submit in one focused portal instead of Slack threads, inbox dumps, and hallway messages.<br>Repo-aware AI turns rough reports into structured GitHub issues — with a 'Potential Areas to Investigate' section pointing developers at the right code.<br>People who submitted feedback can stay updated without joining GitHub or asking engineering for manual status checks.

Workflow<br>GitHub-first

Submitter access<br>No GitHub account needed for submitters

Product proof<br>See the handoff from collaborator input to developer-ready GitHub issue

TypeBug Report<br>Title<br>DescriptionTapping Pay on my phone just shows a spinner. It never moves past it.

See how Flunes structures it →

No parallel triage inbox for developers to learn.<br>Automatic GitHub issue creation from collaborator input.<br>Original context stays linked when the team needs to inspect it later.

Made for teams that collect feedback from people who should not live in GitHub<br>Useful for indie developers, product teams, agencies, and small SaaS companies working with clients, founders, PMs, ops teammates, or internal stakeholders who need a simple reporting path.<br>Sounds like you? Try it free

Stop translating chats into tickets by hand<br>The problem is not GitHub. The problem is everything that happens before something becomes a usable GitHub issue.

✕ Without Flunes<br>Feedback arrives across Slack, email, and random calls<br>You rewrite it into a GitHub issue yourself<br>Details get lost between messages and follow-ups<br>Collaborators ask for updates outside the workflow<br>Each report costs attention before work even starts

✓ With Flunes<br>You share one portal link per repo<br>People submit feedback without accounts<br>Repo-aware AI shapes the issue using your README and file structure<br>GitHub issues are created automatically<br>Your team triages from cleaner input<br>Each issue lists potential code areas to investigate<br>They can follow progress without chasing you

Start free and give outside feedback a proper front door.<br>Connect one repo, share one link, and let GitHub receive cleaner issues automatically.<br>Start free