License Support | 6MM Docs

License planning is part of a broader launch plan. The right path depends on target markets, user type, product scope, custody model, and the operational responsibilities of each party.

Planning inputs

Input	Why it matters
Target jurisdiction	Determines regulatory expectations and required local review.
User type	Retail, professional, institutional, or partner-distributed users may require different controls.
Product scope	Spot, derivatives, wallet, custody, and brokerage features can change the compliance model.
Operating model	White-label, embedded, broker, and institutional models have different responsibility boundaries.

How to use this documentation

Use these docs to align technical and operational requirements before legal review. The documentation can help teams describe architecture, data flow, signing, security, asset movement, and trading lifecycle responsibilities.

Important

Licensing decisions must be reviewed with qualified legal and compliance advisors for the relevant jurisdiction.

Compliance Overview: information to prepare and recommended review path.
Partner Responsibility Matrix: ownership across infrastructure, users, assets, and incidents.
Compliance, Licensing & Trading Technology: connect the operating model to technical controls.
Production Launch Checklist: confirm readiness before public access.

Planning inputs

How to use this documentation

Related review materials