An exchange is a custody business that happens to have a trading screen. Almost every catastrophic failure in this industry has been a custody failure, not a matching-engine one.
Nobody loses an exchange because the order book was slow. They lose it because keys were held badly, a withdrawal went out that should not have, or nobody noticed a balance drift until it was large.
So the questions worth asking a vendor are about wallets and approvals, not about latency.
The wallet layer
What actually holds the assets, across however many chains you support.
- Unlimited networks; ERC20, TRC20, BEP20 and Bitcoin out of the box
- System wallets separate from user wallets
- Per-network balance snapshots across both
- Deposit confirmation settings per chain
Getting money out is the dangerous part
Deposits are easy. Withdrawals are where exchanges are lost.
- Withdrawal approval as an explicit administrative step
- Per-asset and per-network withdrawal fees and limits
- Limits tied to a user's verification tier
- Account restriction and suspension when something looks wrong
Noticing before it is large
Reconciliation is a daily habit that software can support and cannot replace.
- Every deposit, withdrawal, trade and transfer in one auditable view
- Price feeds tracked per market, with reconciliation tools
- Live health and start/stop control for every background service
- Queue and socket status, because a stalled service is how a gap opens quietly
What this is not
Custody deserves a plain paragraph rather than a confident one.
- Not an insured custodian — insurance is a policy you buy, not a feature
- Not a key management service; where your keys live is your architecture decision
- Not independently audited — there has been no third-party security review of this codebase
- The source is complete and unencrypted, which is what allows you to commission one
Own it outright
A clone in the marketplace sense is a copy you rent or cannot read. This is the opposite arrangement.
- Complete source code, with no encryption and no obfuscation
- Deployed on infrastructure you control
- No recurring licence, and no vendor approval needed to change how it works
- $24,900 one-time for the Full Suite, with deployment and six months of support
What custody actually requires
| The capability you are after | How it works here |
|---|---|
| Many chains | Unlimited networks, with the major standards supported out of the box |
| Separated holdings | System wallets distinct from user wallets, with snapshots across both |
| Controlled withdrawals | Approval as its own permission, with per-asset and per-network limits |
| Limits that follow identity | Withdrawal limits tied to the user's verification tier |
| Daily reconciliation | Auditable transaction view plus per-market price feed reconciliation |
| Early warning | Live status for every background service, queue and socket |
| Reviewable code | Full source, unencrypted, on infrastructure you control |
Questions you might have
Do you hold keys or assets?
No. It is deployed on your infrastructure and you operate it. We are the software vendor, not a custodian.
Is cold storage supported?
Where the keys for your system wallets live is your architecture decision; the platform separates system from user wallets and reports on both.
Has the code been audited?
Not independently. We would rather say that than let it be assumed — and full source is what makes an audit you commission possible.
Can withdrawals be fully automatic?
They can, and for small amounts most venues do it. The approval step exists so that is a decision you make rather than a default.
See the platform behind the comparison
A private demo walks the platform with the people who deploy it. Bring the feature list you started with and check it against what is on screen.