Providers that hold keys for others, run wallets, nodes and analytics for blockchains. It has no schema of its own: companies here are mapped on the Crypto-asset companies schema, and what it does not cover is recorded as gaps.
© 2026 System Atlas · Built by MIOSA
Free to map your own company · Members $300 a yearHow automatable each primitive is, estimated from the 0 organizations mapped in public on the Crypto-asset companies schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Custody and key management Supply: making or delivering the offer | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Order matching engine Supply: making or delivering the offer | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Accounting and close Money: getting paid and paying | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Core system of record Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Communication tools Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Integrations Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.
Focused research on the organizations with the fewest mapped parts in custody, wallets and blockchain infrastructure; what it finds is public for everyone.