Skip to main content
A Platform in LaunchLab is a third-party launch environment built on top of Raydium’s LaunchLab program. Platforms can brand themselves, charge their own fees, and configure the post-bonding-curve migration parameters for every token launched under them — without running a separate on-chain program. Raydium’s own launch UI is just one platform among many.

​
Why platforms exist

Raydium wanted LaunchLab to be a shared primitive, not a single branded product. The Platform PDA system lets ecosystems, tooling providers, communities, and meme teams offer curated or branded launch experiences that all settle into the same underlying LaunchLab bonding-curve program and CPMM post-migration pool. Examples of platforms you might see in the wild:
  • Raydium’s own LaunchLab UI at raydium.io/launchlab — the reference implementation.
  • Partner launchpads — third parties who’ve registered their own Platform PDA to brand the launch experience.
  • Niche platforms — e.g. a community-specific platform that only launches memecoins tied to a particular theme, with a custom fee share funding its treasury.
All of these tokens still live on the same LaunchLab program, graduate to the same CPMM program, and can be routed by the same aggregators.

​
The Platform PDA

Each platform is represented by a Platform PDA stored in the LaunchLab program. Fields include: Exact field names are in the LaunchLab IDL (sdk-api/anchor-idl). The table above is a descriptive overview.

​
What a platform can control

Fee capture:
  • Platform fee share on every pre-migration buy/sell.
  • Post-migration share — before the 2026-08-17 upgrade, the creator scale produced a separate creator Fee Key. For migrations executed afterward, platform_scale + creator_scale becomes one platform-owned locked-LP position and burn_scale is burned.
Post-migration destination:
  • CPMM with an AmmConfig chosen via cp_config_id. All newly initialized launches use CPMM.
  • AMM v4 remains only as the graduation path for existing launch state created with the legacy migrate type.
User experience:
  • Branding metadata used by the Raydium app and any wallet / explorer that surfaces LaunchLab tokens.
  • Launch-page customization — platforms that host their own frontend can filter tokens to only show their own platform’s launches.

​
What a platform cannot control

  • Bonding-curve math. The curve shape (logistic, exponential, etc.) is part of the LaunchLab program itself. Platforms choose from the supported curves; they cannot add arbitrary custom curves.
  • Migration threshold logic. The condition that triggers graduation to CPMM is program-enforced.
  • Core security / audit posture. Every platform inherits LaunchLab’s audit history; a malicious platform cannot bypass it by altering the program.

​
Registering a platform

The LaunchLab program exposes a create_platform instruction (exact name from the IDL). Callers pass:
  • The seed that will derive the Platform PDA.
  • The fee destination account.
  • Desired fee bps (subject to program-level caps).
  • Post-migration config (CPMM AmmConfig ID if applicable).
  • Branding metadata.
Rent for the Platform PDA is paid by the creator. Updates to branding and some fee parameters are permitted post-creation by the platform’s authority; structural parameters (migration destination program) typically are not. See products/launchlab/instructions for the exact instruction signature in the current LaunchLab IDL.

​
Economic interaction

A single swap on a LaunchLab bonding curve distributes value roughly like this (exact ratios set by the platform):
Post-migration, LP tokens have two effective destinations:
The platform Fee Key represents claimable LP-fee rights without an ability to withdraw the locked liquidity. Burned LP has no Fee Key holder.

​
Restricting global configs

A platform admin can set restrict_global_config = 1 and create one PlatformAllowConfig per accepted GlobalConfig. New launch transactions must then append the matching allow PDA. With restriction disabled, the platform accepts any config that passes the program’s other validation.

​
Integrator notes

  • Listing tokens by platform. Use the API pool-info / mint endpoints with a platform filter (when supported) to list only tokens launched under a specific Platform PDA.
  • Branding display. If you build a wallet or explorer that surfaces LaunchLab tokens, reading the platform’s name / image URL from the Platform PDA is far better UX than showing “LaunchLab” for every token.
  • Fee math. Every bonding-curve quote must account for the platform fee in addition to the protocol and creator fees. The SDK’s quote helpers do this automatically when the platform PDA is supplied.

​
Where to go next

Sources:
  • LaunchLab program IDL bundled in the Raydium SDK v2: raydium-io/raydium-sdk-V2 under src/raydium/launchpad/.
  • api-v3.raydium.io/launchlab/platforms endpoints (when available).