Name: Crew Launch
Brand: DEPLOYR
Price: 299 USD
Availability: PreOrder

Picture this

Who it is for

An open-source maintainer wants to reward 40 contributors. Crew Launch reads their merged work, proposes allocations, and vests them with locked liquidity.

Two ways to own it

What you get

Base$299

$75 deposit to reserve

Contribution import, allocation editor, vested token, LP lock.

You choose: chain
You choose: name and logo
You choose: accent color

Customfrom $2,000

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

What is new

Contribution-weighted vested launches have been done by hand; packaging it as a product is uncommon.

Closest things out there

Developer DAO allocated $CODE from Coordinape contribution data with vesting, and Mangrove and Morpho vested contributor tokens, but these were one-off allocations, not a reusable launch product.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Turns shipped work into ownership.

The Regatta Board

Races it can enter

grant · Optimism Collective · rolling

Optimism Retro Funding

rounds/seasons; current round unknown

Official page ↗

Retroactive; needs measurable impact.

Their rule on existing code: Retroactive: existing deployed projects with measurable impact required

grant · Gitcoin · upcoming

Gitcoin Grants rounds

quarterly-ish rounds; next round dates unknown

Official page ↗

Existing open-source projects OK.

Their rule on existing code: Existing open-source projects OK (generally required)

What you own

The whole app, not a starter kit.

The complete Crew Launch app: maintainers turn merged work into a weighted, vested token launch for the people who shipped it, with a reason next to every name, disputes, a farming filter, a USDC paywall and receipts built in.

Base price · $299

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: ownership follows the work, a reason per name, vested and signed by you.

Launch progress and next actionHome

Terms, roll, approve and launch with one clear next step and recent activity.

Launch terms editorTerms

Chain, crew pool, vesting, cliff, liquidity lock and what counts as work, drawn live.

Farming filterTerms

Tiny PRs collapse to one and new accounts are held for the maintainer.

Repo importRoll

Reads public merged PRs, reviews, docs and triage. Never private messages.

Weighted crew roll with reasonsRoll

Every name opens a reason sheet with the maths behind the share.

Held account reviewRoll

Keep a farmed account held or include it at one small fix.

Disputes and approvalRoll

Accept or decline disputes with a public note, then approve the roll.

Contributor emailsRoll

A private note to each contributor with share, reason and dispute link. Gated behind Fleet when the owner turns it on.

Paid launch with USDC checkoutLaunch

Buy a launch in USDC on Base, then sign to deploy token, Merkle roll, vesting and LP lock.

Onchain receipts and unlock curveLaunch

What went onchain, what stays private, and the crew unlock schedule.

Monthly epochsEpochs

New work joins each month and the maintainer signs a new root. Gated behind Fleet.

Plans, receipts and settingsMe

Pricing from the owner paywall, payment receipts, Safe signing and permissions.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

Launch fees, recurring plans, incoming USDC, payouts and accepted payment methods.

Launch pipelineLaunches

Every project's stage, where launches stall and a one tap help note.

Scoring rulesRules

Tiny PR size, account hold age, dispute window, per person cap, chains and gas.

Agent logAgent

What the helper did, what failed, how it adapted, and running costs.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Office hours loop and referralsGrowth

Run a dev community call, track crew turned maintainers and referral launches.

The money path, built in

How it earns for you

A flat fee per launch plus a monthly plan for living projects that run recurring crew rolls. The owner never takes a share of anyone's token.

Crew$149 per launchOne repo, up to 50 contributors, vesting, LP lock, one dispute round

Fleet$79 a monthMonthly epochs, unlimited contributors, farming review queue, contributor emails

FoundationCustomMany repos, custom weights per repo, Safe workflows, audit exports

Launch gas can be sponsored by the owner, usually under $5 on Base. Payments arrive in USDC on Base, other chains or by card on-ramp.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

Crew become maintainers: people paid in a roll run one for their own projects
Every contributor email and share card names the tool
Public formula pages that other maintainers fork
Maintainer office hours with dev communities that run bounties
Maintainer to maintainer referral links with a discount on both launches

Roadmap · build the next phase with us

Where it goes next

v1 included

The full launch app

Repo import with farming filter
Weighted crew roll with reasons and disputes
Token, Merkle roll, vesting and LP lock
Monthly epochs
USDC paywall and receipts

Included

More kinds of work

Import design, forum and Discord support work
Per repo weights for monorepos
Public roll page with epoch diffs
Bounty boards feed the roll

Add-on from $500

Portable crew history

Contributor passport across projects
Private proof of a place on a roll
Retro funding and grant exports
Multi Safe flows and auditor view

Add-on from $1,200

For investors and grant reviewers

The pitch, ready

Launch a token that only your verified contributors can receive, weighted by the work they actually shipped.

Problem: Open source tokens are allocated in spreadsheets or by raffle. Reviewers, docs writers and triagers get missed, farmed accounts get paid, and nothing vests.

Solution: Import the repo, get a weighted crew roll with a reason per name and a farming filter, answer disputes, sign, then deploy a vested token with locked liquidity and a monthly roll.

Why now: Cheap L2 gas, signed wallet links and small models that can explain a share in plain words make a fair, reusable launch product possible for any maintainer.

Market: Thousands of active open source projects and developer communities on Base, Arbitrum and Optimism, plus foundations running retroactive rewards.

The ask: Pilot launches with 10 open source maintainers, and introductions to dev communities that already run bounties.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: meet Ines in Valparaiso, see the next action
Terms: set a 10% pool, 24 month vesting and a 12 month LP lock
Roll: read the merged work, open Aiko's reason, hold the typo account, accept Dele's dispute and approve
Launch: buy the launch with USDC on Base and sign to deploy, then read the receipts
Epochs: unlock Fleet and sign the next monthly roll
Owner Revenue: change the Fleet price and preview the user Plans sheet
Owner Agent and Rules: see the wrong turns and tighten the tiny PR rule
Owner Roadmap: request v2 with DEPLOYR

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work covers new importers, bespoke scoring formulas, Safe and governance integrations, branding and audits of your own contracts, scoped on a call from $2,000.

Custom from $2,000

BLUEPRINT

Why it matters and how it really works

The need

Open source projects that launch a token usually allocate it by hand in a spreadsheet, or by raffle and snapshot. Quiet contributors such as reviewers, docs writers and issue triagers get missed, farmed accounts with dozens of trivial PRs get paid, and recipients sell on day one because nothing vests.

What exists and what is new

This has been done before, by hand. Developer DAO allocated $CODE to early contributors using Coordinape contribution data with vesting, and Mangrove and Morpho vested tokens to core contributors through governance proposals. Those were one off allocations run by each team. What is new here is packaging it as a reusable launch product: import a repo, get a weighted crew roll with a reason per name, a farming filter, maintainer approval, then vesting and a liquidity lock in one flow. Research verdict: rare, medium novelty.

The data it runs on

Public repository history: merged pull request authors and size, Co-authored-by trailers, approving reviews, docs changes and issue triage. Wallet links signed by each contributor. The maintainer's chosen weights and terms. Private messages and closed repos are never read.

1.The mission

When people build something together, ownership should follow the work they actually shipped, not who arrived loudest at launch.

2.Why people can't resist it

A reason next to every name Each contributor sees their share and exactly which work earned it, so the roll can be argued with and fixed before it is final.

The quiet work counts Reviews, docs and triage carry weight, so the person who read every change is not left at a fraction of a percent.

A monthly roll New merged work joins the next epoch, so contributing keeps earning a place instead of ending at a snapshot.

3.How it works for real

Import: GitHub App with read only access to public repo data. An indexer pulls merged PRs, reviews, trailers, docs paths and issue labels into Postgres.

Score and explain: A deterministic scoring formula the maintainer configures does the math. A small model such as Claude Haiku writes the plain reason per contributor and flags patterns like bursts of tiny PRs from new accounts. A larger model is only used on flagged cases.

Link wallets: Contributors sign in with Privy and sign a message proving they control both the GitHub handle and the wallet. The link is stored privately; only the wallet goes into the roll.

Approve: The maintainer reviews flags and disputes, then signs the roll from a Safe. Nothing deploys without that signature.

Deploy: An ERC-20 on Base, Arbitrum or Optimism, a Merkle root of the crew roll, linear vesting streams with an optional cliff, and the liquidity position sent to a time locked contract.

Attest and notify: An EAS attestation records the roll hash and scoring formula version. Contributors get an email with their share, reason and claim link. Each monthly epoch posts a new root.

4.Cost per use and pricing

Scoring a 40 person repo with six years of history is about 2,000 PRs and 4,000 reviews. Reasons with a small model run roughly 300k input and 40k output tokens, under $1. On Base, deploying the token, vesting and lock is a few transactions, usually well under $5 in gas at normal fees; claims are paid by each contributor and typically cost cents. Example month for an owner running 10 launches plus monthly epochs: about $40 to $80 in model and gas costs, plus hosting.

Crew $149 per launch

One repo, up to 50 contributors, vesting and LP lock, one dispute round.

Fleet $79 per month

Monthly epochs, unlimited contributors, farming review queue and contributor emails.

Foundation Custom

Multiple repos, custom weights per repo, Safe workflows and audit exports.

5.Growth loop

Every contributor email and share card names the project and the tool. Maintainers who are paid in a crew roll tend to run one for their own projects, and each public roll links back to the formula it used.

6.Risks and guardrails

Securities and tax: Tokens given for work can be treated as income or securities depending on the country. The product gives no legal advice, shows a clear warning, and owners should get local counsel before launching.

Gaming the metric: Any formula can be farmed. Tiny PR collapsing, new account holds and maintainer approval reduce it but do not remove it, which is why a human signs every roll.

Unfair weights: The maintainer picks the weights and could favour friends. Weights, formula version and reasons are published so the crew can see and dispute them.

Privacy: Linking a GitHub handle to a wallet can deanonymise people. Links stay private by default and contributors can opt out of the roll entirely.

Contract risk: Vesting and lock contracts must be audited, well known implementations. A bug could freeze or release tokens early.

No promised value: The token may be worth nothing. The app never shows price predictions and never presents the allocation as income.

7.Build order

GitHub import and contributor table for one public repo
Configurable weights, tiny PR filter and new account hold
Per contributor reason text and a dispute form
Wallet linking by signed message
Merkle roll, linear vesting and LP lock on Base testnet, then mainnet
Contributor emails with claim link and share card
Monthly epochs with a new root

8.Where this is going

Now
A maintainer launches a token to the 40 people who built the project, weighted by real work, vested and locked.
Next
Monthly rolls keep new contributors arriving, and other kinds of work such as design and community support can be imported.
Later
A portable crew history: a contributor can show every roll they earned a place on, across projects, without exposing who they are.
The world it builds
Shared ownership becomes the default way open work is rewarded, so the people who keep public tools alive share in what those tools become.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Crew Launch

When projects reward contributors, the tokens usually end up with farmers and insiders. Own Crew Launch and you run the launch tool that reads merged work and vests tokens to the people who built the thing, from your wallet and your brand. The launch fees, the maintainer relationships and the onchain record of every fair launch are yours.

What’s stopping you?

“Is launching a token legal?”

It depends on where you and the project are, and on what the token does. Crew Launch is a tool; the project launching the token should get its own legal read. You should not promise holders any value.

“What if contributors argue about allocations?”

They will. The allocation editor shows the raw data and lets the maintainer adjust with a public note. Make a dispute window part of every launch.

“I can't code.”

You do not need to. Crew Launch arrives working, deployed from your own wallet with a written guide for every step. You will click, paste and fill in names. If you ever want a change you cannot make, the custom option or a freelancer can handle it, but the first launch needs no code.

“Is it really mine?”

Yes. The contract is deployed from your wallet on Base, the code sits in your own git repo, and the name and brand are yours. DEPLOYR does not hold your keys or take a cut of what Crew Launch earns. If you stop paying anyone tomorrow, the app keeps running on your wallet.

“What if nobody uses Crew Launch?”

That is the most likely early outcome, and it is fixable. The paths below start with you as the first user, then ten real open source maintainers and project leads you can name today. If ten people you message do not care after you have shown it to them, you have learned something useful in a week instead of a year.

The million-dollar ladder

A flat setup fee per launch plus an optional monthly plan for projects that run recurring contributor rewards. This ladder is a target, not a promise.

$300

$3,600

$42,000

$85,000

First 10 users

2 pilot launches a month

$150 each

Proof it works

12 launches a month

$300 each

Real business

60 launches and recurring reward plans