Owning source you cannot operate is not ownership. This is what ships with the platform, and what does not.
Every vendor says the platform is documented. Few will tell you what that means before you have paid, which is how teams end up with a folder of screenshots and a support address.
So: this page is the list. It is deliberately specific about what is there and blunt about what is not.
Deployment and configuration
Written for the engineer who has to stand the platform up, not for the person who signed for it.
- Environment and dependency requirements
- Installation and first-run configuration
- Environment variables, services and what each one does
- Wallet and network setup, per chain
- Payment and provider integration points
The API reference
The part your own developers will live in.
- Public endpoints — assets, prices, markets, transaction history
- The authenticated private API
- WebSocket feeds for trades and market data
- Authentication, rate limits and error shapes
Running it day to day
The admin panel is where the exchange is actually operated, and it is the half most vendors leave undocumented.
- Markets, assets, pairs and fee configuration
- Verification review, withdrawal approval and dispute handling
- Roles and permissions
- Reports, and what each one is derived from
What is not here
Named plainly, because a documentation page that only lists what exists is an advertisement.
- The documentation is delivered with the platform; it is not published on this site
- There is no public sandbox with API keys — the demo exchange is a running platform, not a developer environment
- No architecture decision records or internal design docs
- No SDKs in other languages; the API is HTTP and WebSocket, and clients are yours to write
Where the questions actually go
Documentation answers the second question. The first one is usually asked out loud.
- Six months of support is included with the Full Suite
- Deployment is done with your team rather than handed to them
- You hold the source, so an unanswered question is readable rather than a ticket
- Extended support is a separate arrangement if you want one
Questions you might have
Can we see the documentation before buying?
Not on this site, but it is a reasonable thing to ask for on a call, and we would rather show it than describe it.
Is the API documented well enough to build against?
That is the claim, and the way to test it is to have your engineer ask specific questions on the technical walkthrough.
Do you document the database schema?
The source is complete and unencrypted, so the schema is readable directly. There is no separate published data dictionary.
What happens when documentation is wrong?
Tell us during the support window and it gets corrected. After that you own the source and can correct it yourself, which is the trade you made.
Ask an engineer, not a brochure
The technical walkthrough is the one where this page stops mattering: bring your developer, open the source, and check the documentation against it.