Skip to main content
Leading options · 9 ranked from 14 screened

Token Launch Platforms

Token Launch Platforms evaluated across unavoidable protocol fee and fee disclosure, creator control surface and published ranges, graduation and LP disposition, and post-deploy rug surface and admin powers.

#1 of 9 · published ranking
Bags
81ChainChoice Score
Why it leads
Best in the pool on protocol fee floor and disclosure (9/10; next 8/10)
Cost
Not priced · No comparable price is published
No provider can pay for a position in this table. The code that computes this order cannot read which links earn us a commission, and every build proves it. Every score below rebuilds from the published criteria.Ranking 2026.08 · 4 criteria · 9 products · same inputs, same order
Personal comparison

Token Launch Platforms ranked comparison

No comparable price is published; ranking still uses verified product evidence.

RankProviderBest fitScore
1
BagsA permissionless token launch venue on...Top ranked
Protocol fee floor and disclosure — 9/10Trade-off: The issuer's side of the contract freezes at launch and the venue's side does not. "T...
81score
Check availability for your countryVisit Bags · bags.fm

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

2
Raydium LaunchLabRaydium LaunchLabSolana bonding-curve launch program, ru...
Creator control surface — 9/10Trade-off: You are not the customer here — the front end you launch through is. Since the 2026-0...
80score
Check availability for your countryVisit Raydium LaunchLab · raydium.io

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

Same score, not joint · ordered by weighted total (47.00 against 46.90)
3
ClankerClankerA permissionless token factory on Base...
Graduation and lp disposition — 9/10Trade-off: Your fee split is set once and is permanent. The docs state it plainly but only insid...
80score
Check availability for your countryVisit Clanker · clanker.world

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

4
Jupiter StudioJupiter StudioJupiter's own Solana token launcher: a...
Creator control surface — 9/10Trade-off: Two live Jupiter pages give opposite answers to the only question that matters about...
78score
Check availability for your countryVisit Jupiter Studio · jup.ag

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

5
HeavenHeavenSolana launchpad that owns its own AMM:...
Protocol fee floor and disclosure — 8/10Trade-off: Heaven's docs sell the launch as unconditional — permissionless.md: "Every token laun...
77score
Check availability for your countryVisit Heaven · heaven.xyz

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

6
four.memefour.memeBNB Chain bonding-curve launch venue wh...
Creator control surface — 8/10Trade-off: The venue's own admin powers are the one thing it refuses to document, and they are n...
72score
Check availability for your countryVisit four.meme · four.meme

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

3 more assessed and ranked below — none of them hidden for commercial reasons.
Ranking blindCommercial terms excludedDated primary sources

Ranked on 4 published criteria weighted 30/30/25/15, which set goal alignment — 30 of the 86 points. The rest: regional access 20, evidence depth 18, ease of use 10, institutional trust 8. Profile match is shown in breakdowns but carries no weight.

Audit
Infrastructure
Methodology
2026.09.15
published 2026-09-16
Providers tracked
980+
across 119 categories
Last verified
2026-08-27
newest dated pricing or sentiment read
Named on the roster
2 people
managing directors · 6 automated processes
Decision guide

What matters most before choosing in this category

Weighted on the protocol fee an issuer cannot configure away (30), the control surface they keep at deploy (30), where the liquidity lands when the curve completes (25), and the residual power the venue holds over a live token (15). FEE AND CONTROL SHARE THE LEAD BECAUSE BOTH ARE ONE-WAY. The venue is chosen once, on the day the token is deployed, and its fee is then charged on every trade for the life of that token; vesting, cliffs, fee splits and revoked authorities are set at deploy and cannot be revisited once it is trading. THIS PAGE RANKS DOCUMENTATION, AND SAYS SO. The venue that documents best is not where most people launch — the leader earns it on a proxy-topology table and a seven-mode fee schedule, and the runner-up largely on one page that both renounces and admits what it keeps. Where a venue’s page and its deployed config disagree, the config wins the fee and the page loses the disclosure point; the disagreement is never itself scored as the fee. THERE IS NO TRACK-RECORD SCORE, deliberately. Not one venue in this pool publishes its own launch archive with outcomes, so a record here would be assembled from third parties. The rug criterion instead reads what each venue states CANNOT be done to a token once it is live, which is the only half of that question anyone has put in writing.

What matters most before choosing in this category

Weighted on the protocol fee an issuer cannot configure away (30), the control surface they keep at deploy (30), where the liquidity lands when the curve completes (25), and the residual power the venue holds over a live token (15). FEE AND CONTROL SHARE THE LEAD BECAUSE BOTH ARE ONE-WAY. The venue is chosen once, on the day the token is deployed, and its fee is then charged on every trade for the life of that token; vesting, cliffs, fee splits and revoked authorities are set at deploy and cannot be revisited once it is trading. THIS PAGE RANKS DOCUMENTATION, AND SAYS SO. The venue that documents best is not where most people launch — the leader earns it on a proxy-topology table and a seven-mode fee schedule, and the runner-up largely on one page that both renounces and admits what it keeps. Where a venue’s page and its deployed config disagree, the config wins the fee and the page loses the disclosure point; the disagreement is never itself scored as the fee. THERE IS NO TRACK-RECORD SCORE, deliberately. Not one venue in this pool publishes its own launch archive with outcomes, so a record here would be assembled from third parties. The rug criterion instead reads what each venue states CANNOT be done to a token once it is live, which is the only half of that question anyone has put in writing.

Which part of the fee can you never configure away — and did the venue publish it as a rate, or as a floor?
What can you still set at deploy — vesting, cliff, fee split — and is the range published anywhere?
When the curve completes, who holds the LP position and the claim on your token’s trading fees?
What can the venue still do to the token after it is live, and has it written down what it cannot?
Current editor lead

Expert review and scoring weights

BagsData checked Aug 2026
A permissionless token launch venue on Solana (Meteora DBC/DAMM v2) and Robinhood Chain whose defining feature is fee-splitting: a SOL-quoted launch must allocate its trading-fee stream across up to 100 named claimants in explicit basis points, while the non-SOL path skips the fee-share config entirely.

A permissionless token launch venue on Solana (Meteora DBC/DAMM v2) and Robinhood Chain whose defining feature is fee-splitting: a SOL-quoted launch must allocate its trading-fee stream across up to 100 named claimants in explicit basis points, while the non-SOL path skips the fee-share config entirely. Strongest on unavoidable protocol fee and fee disclosure (9/10): This overturns the panel brief's TRAP 6 ("Bags' '1%' is a null... publishes elaborate BPS plumbing and no take rate"). That is no longer true: Bags now publishes the most granular fee schedule in the pool, exceeding the Heaven anchor on the trade-fee axis. Weakest on post-deploy rug surface and admin powers (6/10): A split verdict, and the criterion's 'honest retention outranks silence' rule is what saves it. Published price: PUBLISHED, and on two surfaces, not one. Solana trade fees, https://docs.bags.fm/how-to-guides/customize-token-fees (read 2026-08-27): "There are seven available fee modes.

Best forProtocol fee floor and disclosure — 9/10
Main tradeoffThe issuer's side of the contract freezes at launch and the venue's side does not. "The `bagsConfigType` is set once when creating the fee share config and cannot be changed after the token is launched" — the fee mode is permanent. But Bags' own powers over an already-launched token are retained and live: BagsBondingCurve and BagsFeeShare are beacon proxies where a single `upgradeTo` "retargets **all** curves at once" / "retargets **all** fee-shares at once", i.e. one transaction rewrites the trading and fee-claiming logic of every token ever launched on the chain simultaneously. I read `factory.owner()` on the deployed BagsFactory and it returned 0xDEf671F11C8a30818eb3D9Cc9476EEEc805f9058, which has no bytecode — a plain EOA, not a multisig, holding that key. Second discovery: the published fee is not the fee. Docs state creationFee "default 0.02 ETH"; the live `factory.creationFee()` returns 0, and `factory.graduationThreshold()` returns 5 ETH, a figure the docs never state. The docs concede this themselves — "Always read these live from the contracts before rendering or signing — never hardcode" — so a buyer budgeting from the page is working off numbers the vendor disclaims. Third: on Solana, the flagship product, the disposition of the SPL mint, freeze and update authorities is never stated anywhere in the 103-page developer corpus. Fourth, found on verification: Bags answers the question of whether you can ever change who receives your fees TWICE, in opposite directions. The developer docs sell it as a feature — `bags config update` "requires admin authority", `bags config transfer-admin --new-admin` moves the key. The consumer help centre refuses it as policy: "We cannot allow changes to royalty recipients, as doing so would undermine trust and integrity within our community… That's why this policy is in place" (support.bags.fm/en/articles/13434866-change-royalty-recipient). Both were live on 2026-08-27.
Verify before signupPUBLISHED, and on two surfaces, not one. Solana trade fees, https://docs.bags.fm/how-to-guides/customize-token-fees (read 2026-08-27): "There are seven available fee modes. If you don't specify a `bagsConfigType`, the **Default** mode is used." Default mode table: "Pre-migration | 2% | 1% | 1% | —" and "Post-migration | 2% | 0.75% | 0.75% | 0.5%" (columns: Total Fee | Protocol | Creator | Compounding). The seven published modes span 0.25%, 1%, 2% and 10% total fees; the "2% Base with 96% Supply Locked" mode publishes a post-migration decay "starting at 2% and decaying to a 0.5% floor". CORRECTION TO THE FIRST DRAFT, which asserted "NO creation cost is published anywhere for the Solana path": the Solana cost to launch IS published — not in the developer docs, but on the vendor's own help centre. https://support.bags.fm/en/articles/13434740-sol-needed-to-launch (read 2026-08-27): "To launch a token on Bags, you'll need approximately 0.2 SOL to cover network fees and transaction costs. We recommend keeping a little extra in your wallet just in case the Solana network is busy." Corroborated at https://support.bags.fm/en/articles/13434607-taking-sol-but-not-creating-token: "Please make sure to have around 0.2 SOL for the launch on your wallet for a smooth launch experience." Bags attributes that 0.2 SOL to network and transaction cost, not to a platform charge; no Bags-charged creation fee for the Solana path appears anywhere in the 103-page developer corpus, which is a finding at equal weight to a price. Robinhood Chain, https://docs.bags.fm/robinhood/overview (read 2026-08-27): "A flat **2% fee is charged on the ETH/WETH leg of every trade, in both phases**", creator half 1%, protocol half 1%; plus "There is also a one-time **launch fee** (`creationFee`, default 0.02 ETH) paid to the vault when a token is created." That published EVM launch fee is not currently charged: `factory.creationFee()` on the deployed BagsFactory (0xe8Cc4431adF8b5A847C113EF0c6af9043219Cb37, chain 4663, block 47,695,550, 2026-08-27) returns 0, while `factory.graduationThreshold()` returns 5 ETH — a figure the docs never print. The docs disclaim their own numbers: "Always read these live from the contracts before rendering or signing — never hardcode." The bags.fm app publishes nothing readable — https://bags.fm/, /fees, /docs and /terms all return HTTP 200 with between 0 and 16 readable characters after stripping scripts and tags (/terms' entire readable content is the string "Terms of Service") — but SECOND CORRECTION TO THE FIRST DRAFT: bags.fm returns the same ~52.9KB shell for ANY path, including https://bags.fm/zzz-nonexistent-xyz, so this is a client-rendered application, not a suppressed fees page, and the draft's use of "https://bags.fm/fees returns HTTP 200" as evidence of an empty fees page does not hold. The readable consumer surface is https://support.bags.fm (18 articles).
Methodology

How this category is reviewed

Reviewed on unavoidable protocol fee and fee disclosure, creator control surface and published ranges, graduation and LP disposition, and post-deploy rug surface and admin powers.

The order on this page is the published ranking for this category. Every criterion, weight and source behind it is on the methodology page.
Frequently asked

Questions people ask before choosing token launches

Is this not the same as a launchpad?
No, and the two are ranked separately for that reason. A launchpad serves the buyer of an allocation — it is where you try to get into someone else’s sale. This serves the ISSUER choosing where to deploy a token they intend to keep. Same word in the market, opposite side of the table, and the pools deliberately do not converge.
Why is the fee weighted so heavily when the headline numbers look small?
Because it is one-way and permanent: picked once on deploy day, then charged on every trade for the life of the token, with nothing to renegotiate afterwards. It is also the number most often misstated. Two of the nine published a floor as if it were the rate, and the worst gap was a venue publishing 0.25% against 1.05% all-in on its own front end once its published formula is applied and the deployed config is read.
Why is there no score for how launches actually turned out?
Because not one venue in this pool publishes its own launch archive with outcomes, so any track record would be assembled from third parties and presented as if it were the venue’s own disclosure. Instead the residual-power criterion reads what each venue says CANNOT be done to a token once it is live. That is the inverse of a track record, and it is the half that is actually in writing.
REVIEWEDAugust 27, 2026METHOD4 criteriaCATEGORYtoken_launch_platforms
Not financial advice · For informational purposes only · Always do your own research
ChainChoice
Compare onchain. A brighter future.
© 2026 ChainChoice. All rights reserved.
System statusFeeds last refreshed 9 days ago
Built from commit ba0993b · rankings.json sha256 e1eb24980abb
ChainChoice · The decision layer for crypto · Not financial adviceEducational analysis, not investment advice. Affiliate links may contribute to operations but never alter rankings.

ChainChoice provides informational content only. Nothing on this site constitutes financial, investment, legal, or tax advice. Always do your own research and consult a qualified professional before making financial decisions.