Frequently asked questions

A crowdfunding platform for software features. People propose features on projects they care about, vote for the ones they want, and pledge toward a build budget. When a feature reaches its goal, an AI agent builds it and opens a pull request that the maintainers and backers review before it is merged.

A Claude agent run by nabled, in an isolated environment with a checkout of the project's repository. Each project's maintainers choose the model and effort level it uses. Every build is capped at its feature's budget, and the build log and pull request are visible on the feature page.

Work delivered to a project is contributed under that project's license, like any other contribution. Repositories nabled creates live in the nabled GitHub organization; a maintainer who connects their own repository keeps it.

One credit is one US dollar. You buy them by card (at least $10, with the card processing fee shown before you pay) and spend them on nabled: proposing, voting, pledging and supporting projects.

Credits can't be cashed out. When a feature you backed closes, your share comes back to you as credits.

Each project sets a proposal stake ($5 by default). It becomes your first contribution to the feature. A spec review costs $2 and that $2 counts toward the stake. Maintainers propose on their own projects without a stake or review fee.

If a proposal never opens for funding, the stake goes to the project's pool.

A vote is a small deposit, at least the project's minimum ($1 by default). Anything above the minimum counts as an early pledge. When enough people have voted (the project sets the number, 5 by default), funding opens.

The goal is three things added together, shown on every pledge button:

The build budget: two and a half times the spec review's estimate of what one build costs, with a $5 minimum, to cover a retry and the review pass. The maintainer fee: a default by size (Small $10, Medium $20, Large $40, Epic $80), the project's own default, or a fee the maintainer sets for that feature. The platform fee: 10% of the goal, at least $2.

It goes to the project's pool. Maintainers can direct pool money at other features on the project, by hand or automatically with auto-fund.

Yes, as credits. Contributions are returned in proportion to what each backer put in, after any build cost already spent on the feature. If a maintainer rejects a feature, it gets one rebuild aimed at their reason; if they reject it again, backers are refunded in full and the project pool pays the build cost instead.

Newly bought credits can back features straight away, but they can't be spent on a build for 7 days, in case a card payment is disputed. A funded build waits until the credits behind it clear. The feature page shows when that is.

A private, free proposal in progress. Only you can see it. It saves as you type, and you can come back to it from your dashboard or the project's features page.

An AI reviewer reads your proposal, asks up to four questions whose answers would change the build, refines the spec and estimates what the build will cost. You get three rounds: answer the questions, refine, and propose when you're happy. The estimate sets the build budget.

Yes. Images (PNG, JPEG, WebP, GIF), PDFs up to 20 pages, and Markdown or text files, up to 10 MB each and 10 per proposal. The reviewer and the builder read them. They are private while you draft and public once you propose, like the spec. Location data is removed from photos when you upload them.

The author can edit the spec and attachments while the feature is collecting votes, and maintainers can until funding completes. Once funded, the spec is what backers paid for and it is frozen.

It needs two keys. The backers vote to accept or ask for a rebuild, one person one vote: the proposer and everyone whose money is in the feature. The maintainer chooses merge, rebuild or reject. Both have 7 days.

Before the vote opens, the pull request's CI checks run and an automated review compares the work with the spec, so everyone can see how it did.

The vote needs at least 3 ballots or a quarter of the backers, whichever is larger (never more than the number of backers). Below that, the backers' key follows the automated review: accept if it passed, rebuild otherwise. Ties count as rebuild.

The builder runs again with the comments, on the same branch, paid from the remaining build budget. A feature gets up to two rebuilds; if it still doesn't get both keys, it fails and backers can close it for a refund or propose it again with a changed spec.

Backers see build summaries, CI results, the automated review and previews, but not the code, branches or full logs. Those are visible only to the project's maintainers.

Start a project and either let nabled create a repository, fork a public one, or connect your own repository (public or private) through the nabled GitHub App. You keep ownership of a repository you connect.

Every feature's goal includes a maintainer fee, paid to the project when the feature ships. Set your own default for each feature size in project settings, or a different fee on any feature while it collects votes. Once funding opens you can only lower it.

Fees from shipped features add up in your payout balance on your dashboard. Contact us to arrange a payout.

Yes. In project settings, pick the model (Claude Sonnet, Opus or Fable) and the effort level. Spec reviews price new proposals for the model you choose, so backers see the right goal.

Yes. Project settings has badges for features funding and total pledged, plus a "Fund features on nabled" button for your website.

Yes. Connect your assistant and it can find projects, write drafts, attach files and help you answer spec-review questions. nabled is in Claude's connector directory.

Assistants never spend credits, start a paid review, vote, pledge or propose for you, and you can disconnect them at any time.

We use it to run nabled. Card details go to Stripe, not to us, and there are no ads or third-party analytics. Specs and attachments are sent to our AI provider to review and build features.

Send us a message and we'll take care of it. Unspent credits can't be cashed out, and contributions to features that are still active stay with those features.