Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raydium.io/llms.txt

Use this file to discover all available pages before exploring further.

Raydium publishes its programs and SDK as open source. License terms differ between repositories — the on-chain programs are Apache-2.0, the TypeScript SDK is GPL-3.0. The canonical text is the LICENSE file in each repository; this page summarises but does not replace it.

​
On-chain programs

The deployed Raydium programs are published with their full source under the Apache License 2.0.
RepositoryLicenseCoverage
raydium-ammApache-2.0AMM v4 (constant-product, OpenBook-integrated).
raydium-cp-swapApache-2.0CPMM (standard constant-product, no orderbook, Token-2022 capable).
raydium-clmmApache-2.0CLMM (concentrated liquidity, sqrt-price ticks).
Apache-2.0 grants you the rights to use, modify, distribute, and sublicense the code, including for commercial purposes, subject to the conditions in the license text — primarily attribution preservation and a patent grant. It does not require derivative works to also be Apache-2.0 (unlike GPL-family licenses). For Farm and LaunchLab program licenses, check the LICENSE file in their respective repositories under the Raydium GitHub organization. Licenses can be updated at the repository owner’s discretion; the LICENSE file at master (or main) is the source of truth.

​
TypeScript SDK

The official SDK package @raydium-io/raydium-sdk-v2 is licensed under GPL-3.0.
PackageLicenseRepository
@raydium-io/raydium-sdk-v2GPL-3.0raydium-sdk-V2
raydium-sdk-V2-demo (sample integrations)See repo LICENSEraydium-sdk-V2-demo
GPL-3.0 is a strong copyleft license. Implications for your project:
  • Linking matters. If you embed the SDK and distribute the result (binary, npm package, hosted service), the distributed work generally has to be GPL-3.0 too.
  • SaaS exception. GPL-3.0 (unlike AGPL-3.0) does not require source disclosure for purely networked use — i.e. running the SDK server-side and exposing only its results over an API does not by itself trigger source-disclosure obligations.
  • Patent grant. GPL-3.0 includes an explicit patent grant from contributors covering their contributions.
If your use case is incompatible with GPL-3.0 — for example, you’re building proprietary closed-source software that statically links the SDK and ships it to end-users — talk to the Raydium team via Discord (#dev-support) before you ship. Alternative arrangements are sometimes possible. Don’t assume an unlicensed alternative exists; assume GPL-3.0 unless you have written agreement otherwise.

​
REST and Trade APIs

The HTTP APIs at api-v3.raydium.io and transaction-v1.raydium.io are services, not licensed code. Usage is governed by the implicit terms of service of the hosted endpoints — primarily reasonable rate limits, no abuse, and no claims of warranty. See sdk-api/rest-api for details. These APIs are operated as a public good for ecosystem integrators. Heavy commercial use should be coordinated with the team to avoid being rate-limited.

​
Documentation

This documentation set is published by the Raydium project. Unless an individual page states otherwise, the prose, code samples, and examples on this site are made available under Creative Commons Attribution 4.0 (CC-BY-4.0). You may:
  • Quote, excerpt, or republish content from these docs.
  • Translate the docs into other languages.
  • Use the code samples (which are functionally short illustrations) directly in your project.
You should:
  • Provide visible attribution to “Raydium documentation” with a link back to docs.raydium.io.
  • Not represent your derivative as the official Raydium documentation.
If you spot a mistake or want to suggest a change, every page has a “Suggest edit” button (top-right), or open a PR / issue against the docs repo.

​
Trademarks

The following are trademarks (registered or unregistered) of the Raydium project:
  • The “Raydium” name and word mark.
  • The Raydium logo and symbol mark.
  • The “LaunchLab” product name in association with Raydium’s bonding-curve venue.
Trademark rights are separate from copyright and license rights. Apache-2.0 and GPL-3.0 grant you the right to use the code — they do not grant you the right to use the Raydium name and logo in your derivative product. Trademark use is governed by the Brand kit, which permits attributions like “powered by Raydium” and forbids implications of partnership without explicit agreement. If you fork the code and ship a derivative protocol, you must:
  • Comply with the source license (Apache-2.0 / GPL-3.0).
  • Choose your own name and visual identity. Don’t call your fork “Raydium X” or use the Raydium logo.
  • Make clear in your README that you have forked the original Raydium code and are not affiliated with the Raydium project.

​
Disclaimer of warranties

All code and documentation is provided “as is,” without warranty of any kind, express or implied, including but not limited to merchantability, fitness for a particular purpose, and non-infringement. The full warranty disclaimer text lives in each repository’s LICENSE file. In plain English: the Raydium project does not guarantee that the code is bug-free, that the on-chain state is invulnerable, that you will not lose funds. The audits (security/audits), bug bounty (security/disclosure), and operational controls (security/admin-and-multisig) are mitigations, not guarantees. Evaluate your own risk before integrating or providing liquidity.

​
How to verify

For any specific repository, the canonical license text is the LICENSE file at the current HEAD of the default branch: 
# Apache-2.0 programs
curl -s https://raw.githubusercontent.com/raydium-io/raydium-cp-swap/master/LICENSE | head -3
curl -s https://raw.githubusercontent.com/raydium-io/raydium-clmm/master/LICENSE | head -3
curl -s https://raw.githubusercontent.com/raydium-io/raydium-amm/master/LICENSE | head -3

# GPL-3.0 SDK
curl -s https://raw.githubusercontent.com/raydium-io/raydium-sdk-V2/master/LICENSE | head -3
If the head of these files doesn’t match the license claimed on this page, the repository wins — file an issue against the docs.

​
Pointers

For licensing questions not answered here: For commercial licensing arrangements outside the standard terms, contact the team via Discord and ask to be routed to the partnerships channel. Sources: