How GetAppBuilt works
- Start with an outcome. Request something new or point to a GitHub issue that needs work.
- Make the work clear. Scope, acceptance criteria, non-goals, funding, and review expectations are set before workers rely on them.
- Build and submit. A worker claims a funded bounty and submits a pull request, patch, branch, or artifact.
- Review and settle. GetAppBuilt records review evidence, then follows the locked terms for payout, refund, or dispute.
A request is not claimable work. Backing interest shows demand, not locked funds. Work becomes claimable only after it is a scoped, funded bounty.
Delivery and ownership
Where does a new app's code go?
Every accepted new app or tool is delivered as a public open-source repository in the GetAppBuilt GitHub organization. Repositories use Apache License 2.0, include a GetAppBuilt notice, and ask commercial users to credit and link to the upstream source.
Can GetAppBuilt release an iOS app?
Yes. An iOS request can add submission through our company App Store account. The source remains public. Apple controls review and approval, so submission does not guarantee acceptance or a release date.
What about a feature for an existing app?
Existing-app work may target the owner's repository. The owner or maintainer keeps repository access, merge, and release authority, including for an authorized private repository.
Do you host or maintain the finished app?
No. GetAppBuilt does not provide customer hosting, domains, production infrastructure operation, or long-term maintenance. Web and backend deliveries include setup and operation instructions. Future fixes or upgrades are separate bounties.
Who can do what
If I request or sponsor work
You can describe the outcome and fund a scoped bounty. You control only your own contribution. Funding does not grant merge, payout approval, publication authority, or control over other funders' money.
If I do the work
You can claim eligible funded work, submit evidence, and receive the advertised worker payout when the locked terms are met. You cannot approve your own Submission or payout.
If I maintain the repository
You keep repository review, merge, release, and publication authority. A funded bounty does not force you to merge or publish a Submission.
If I review work
GetAppBuilt review is currently operator-run. Reviewers record evidence against the locked terms; review work is separate from implementation work and has a separate fee when configured.
Money, fees, and refunds
Who can use the fiat pilot?
The initial pilot is for people aged 18 or older acting for a registered company or licensed freelancer. Payees initially need a UAE company or freelance licence and must complete payment-provider onboarding.
Is backing interest a payment?
No. It measures demand for a request. Card checkout is shown separately as a temporary authorization that can transfer to a converted bounty; it is still not captured payment.
What does a worker receive?
The worker receives the advertised worker payout when the bounty's locked terms are satisfied. The platform fee is sponsor-side, and maintainer fees, review fees, stakes, gas, and payment-provider fees are separate.
How do I provide an invoice for a fiat payout?
Before work starts, complete the worker legal/tax profile, reserve your invoice-series prefix, and appoint GetAppBuilt as disclosed invoicing agent. At exact capture, GetAppBuilt issues one worker invoice per sponsor in your name and series, plus a separate WEB3 platform invoice. Each document uses the frozen Work Order allocation, is hashed and kept in private storage, and a mandatory e-invoice waits for accredited-provider acceptance before work can proceed. The payout step waits for the full set to pass operator review before executing the payout. Self-billing is not enabled for the initial launch.
Can I get my contribution back?
Before committed work, you may be able to refund your own contribution under the bounty rules. After work starts, refunds follow the locked terms, timelock, payment-provider state, and dispute process. Open the bounty or My work to see the available action.
Can I pay with crypto?
Not during the first public launch. Native USDC on Arbitrum One is coming soon as a separate rail. A bounty never mixes fiat and crypto funding, payout, or refunds.
GitHub and private work
GitHub identity is required for repository permissions, maintainer checks, worker claims, and implementation Submissions. Email sign-in is enough to request or back work that does not need a GitHub action yet.
Private repository work stays limited to authorized users. Public viewers do not receive private code, artifacts, or confirmation that a hidden record exists. Maintainers keep normal GitHub merge and release authority.
Detailed claim, stake, review-fee, and preflight rules are on the repo policy page.
Review and disputes
Review compares the submitted work with the bounty's locked acceptance criteria and required checks. A review verdict does not automatically merge a pull request or publish a product.
A dispute asks a narrow question: did the Submission satisfy the locked terms? The operator may request more evidence and records the resulting payout, partial-credit, refund, or hold decision. Repository, payment-provider, and onchain states can remain separate.
Start from the affected bounty or My work so the correct record and available next action are visible.
Automation access
Can an AI agent or command-line tool use GetAppBuilt?
Approved automation can use a scoped, first-party account. Start with the public service health and active-rail checks, then email support@web3.consultingfor the current versioned operator guide and access flow. Customer actions remain tied to each real participant: a sponsor, worker, maintainer, reviewer, or payout operator cannot borrow another role's authority. Automation must wait for the prior actor's recorded evidence and unlock condition before continuing.
The first public money rail is USD card authorization and provider payout. Crypto automation is testnet-only until the separate Arbitrum rail launches. Never paste cards, tokens, private keys, or private repository data into support messages or command arguments.
Account and privacy
Use email to request or back work. Connect GitHub when a task needs repository identity or permission. Your Profile shows connected identity, reputation, payout setup when available, and account privacy links.
Read the Privacy Policy for account, GitHub, wallet, payment, artifact, cookie, retention, and data-rights details. The Terms of Service cover eligibility, fees, acceptable use, disputes, and legal limits.
For support, complaints, legal notices, or privacy requests, email support@web3.consulting. This is the current public support channel.