> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.6mm.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.6mm.com/_mcp/server.

# License Support

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.

<h2 id="planning-inputs">
  Planning inputs
</h2>

| 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. |

<h2 id="how-to-use-this-documentation">
  How to use this documentation
</h2>

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.