Question 1

What is Flunes?

Accepted Answer

Flunes turns your team's feedback into clean GitHub issues, no GitHub account needed. Give your PMs, QA, designers, and support one link; they report a bug or idea in a simple form, and it lands in your repo as a structured GitHub issue. AI structuring keeps it clean, the enhancer, not the point.

Question 2

Who is Flunes for?

Accepted Answer

Dev teams who get bug reports and ideas from non-technical teammates (PMs, QA, designers, support, ops) who need an easy way to send feedback but should not need GitHub accounts.

Question 3

How does the workflow work?

Accepted Answer

Connect your GitHub repo, share an invite link with collaborators, and they submit feedback through a simple form. AI structures each submission into a draft issue. You review, triage, and publish to GitHub.

Question 4

Is Flunes a replacement for GitHub Issues?

Accepted Answer

No. Flunes handles the intake layer, feedback collection, AI structuring, and triage. It creates proper GitHub issues so your team keeps shipping from GitHub.

Question 5

Do I need to change how my team uses GitHub?

Accepted Answer

Not at all. GitHub remains the execution layer. Developers still work from GitHub issues. Labels, assignees, and milestones are all set when the issue is created. The only difference is where the feedback comes from.

Question 6

Is a GitHub account required?

Accepted Answer

Yes, you sign in with GitHub to connect your repos. Collaborators submitting feedback do not need GitHub accounts.

Question 7

What permissions does Flunes need?

Accepted Answer

We request repo access to create issues and labels, and read:org for organization repository listing. Flunes only reads your README, topics, and file paths, never your file contents.

Question 8

Can I use private repositories?

Accepted Answer

Yes. Flunes works with both public and private repositories.

Question 9

What happens when a GitHub issue is created?

Accepted Answer

Flunes creates a standard GitHub issue with the AI-structured title and body, applies type and priority labels, and links back to the original submission for context.

Question 10

How do issue labels work?

Accepted Answer

Flunes creates 'bug', 'enhancement', and 'collaborator-feedback' labels in your repo. Priority labels (low/medium/high) are also applied based on the collaborator's impact rating.

Question 11

Do collaborators need accounts?

Accepted Answer

No. Collaborators access the submission form through a unique invite link. No GitHub account, no password, no email verification required.

Question 12

How do I invite collaborators?

Accepted Answer

From the Collaborators page in your dashboard, create an invite with a name and email. Flunes generates a unique link you can share. The collaborator uses it to submit feedback.

Question 13

Can collaborators see each other's submissions?

Accepted Answer

By default, no. Each invite link gives a collaborator their own private submission history.

Question 14

Can collaborators track the status of their submissions?

Accepted Answer

Yes. Through their invite link, collaborators can see whether their submissions are pending review, open in GitHub, or resolved.

Question 15

Can collaborators reply to dev follow-ups?

Accepted Answer

Yes. After a developer comments on a submission, the collaborator can reply directly on the status page or by replying to the email notification. Replies are saved in the submission timeline and synced back to the GitHub issue thread automatically, no GitHub account required. This works on every plan, including Free.

Question 16

Can I have multiple collaborators?

Accepted Answer

Yes. All plans support unlimited collaborators. Create as many invite links as you need.

Question 17

Can I start on Free and upgrade later?

Accepted Answer

Yes. The free tier is permanent for one active repo with 5 AI-structured submissions per month. Upgrade when you need more volume, repos, or plan-specific controls.

Question 18

What changes when I upgrade?

Accepted Answer

Higher tiers expand repository capacity, AI throughput, and screenshot allowances, and unlock features like digest emails, Slack notifications, duplicate detection, and custom form fields and issue templates.

Question 19

Do collaborators need paid seats?

Accepted Answer

No. Flunes pricing is centered on workspace capability. There is no per-collaborator pricing.

Question 20

Can I downgrade or cancel anytime?

Accepted Answer

Yes. You can downgrade or cancel from your billing page. You retain access to paid features until the end of your current billing period.

Question 21

How does AI structuring work?

Accepted Answer

When a collaborator submits feedback, Flunes uses an LLM to analyze the report and restructure it into a clear GitHub issue format, with a descriptive title, structured summary, reproducible steps, expected vs actual behavior, and environment details.

Question 22

Does Flunes look at my codebase?

Accepted Answer

Yes, partially. When AI structures a submission, Flunes reads your connected repo's README, primary language, topics, and a recursive file tree snapshot (capped at 200 paths). It only reads your README, topics, and file paths, never your file contents. The AI uses this context to write a 'Potential Areas to Investigate' section pointing at folders or files that may be relevant. Pro users can remove this section from their custom template.

Question 23

Do you train on my data?

Accepted Answer

No. AI providers (DeepSeek, Google Gemini, Groq, OpenRouter) process submission text for structuring only and do not retain data for training. See our Privacy Policy for details.

Question 24

How many AI-structured submissions do I get?

Accepted Answer

Free: 5/month, Starter: 50/month, Pro: 250/month. Quotas reset monthly, and you can track usage on your dashboard. Nothing is ever dropped. If you reach the limit, new submissions still become GitHub issues, just raw and unstructured, until your quota resets or you upgrade.

Question 25

Can I customize the AI output format?

Accepted Answer

On the Pro plan, you can customize the AI prompt template to match your team's preferred issue structure.

Question 26

Who processes payments?

Accepted Answer

Polar.sh Inc. acts as the Merchant of Record. Polar handles all billing, invoicing, tax calculation, and payment processing. Your payment method will show Polar on your statement.

Question 27

Where can I find my invoices?

Accepted Answer

Paid subscribers can access invoices and payment history through your Customer Portal, linked from your billing page and in your email receipts.

Question 28

How do I delete my account?

Accepted Answer

You can permanently delete your account from Settings. This removes all your workspaces, submissions, and personal data. The action is irreversible and cannot be undone. See our Privacy Policy for data retention details.

Question 29

What data do you collect?

Accepted Answer

We collect your GitHub email and name (via OAuth), workspace configuration, and collaborator submission content. Full details in our Privacy Policy.

Frequently Asked Questions

Getting Started

GitHub Integration

Collaborators

Pricing & Plans

AI Features

Billing & Account

Give outside feedback a proper front door.