Alternatives

Coinbase identification mark

Coinbase Alternatives — Evidence Comparison

Alternative venues are shown for evidence comparison and are not recommendations. They are included because published evidence attributes differ from Coinbase — not because Coinbase is “bad”, and not because of commercial relationships.

Why these venues are included

Each candidate differs from Coinbase on at least one published evidence attribute (regulation, legal-entity mapping, PoR, custody, geographic records, products, or completeness). Inclusion is deterministic from the public snapshot.

Evidence attributes

VenueRegulationLegal entitiesPoRCustodyGeographic scopeProductsCoverage
2101526 / 7i
26221677 / 7i
4413347 / 7i
11111657 / 7i
11112847 / 7i
11111567 / 7i
OKX identification mark

OKX

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction
  • — Regulatory records on file: Coinbase 2 (exact IDs 2) vs OKX 2 (exact IDs 1).
  • — Custody claim records: Coinbase 1 vs OKX 2.
  • — PoR snapshots on file: Coinbase 0 vs OKX 2 (PoR ≠ audit).
  • — Fee snapshots on file: Coinbase 1 vs OKX 2.
Binance identification mark

Binance

Regulatory evidenceCustody modelPoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction
  • — Regulatory records on file: Coinbase 2 (exact IDs 2) vs Binance 4 (exact IDs 4).
  • — Custody claim records: Coinbase 1 vs Binance 3.
  • — PoR snapshots on file: Coinbase 0 vs Binance 1 (PoR ≠ audit).
  • — Fee snapshots on file: Coinbase 1 vs Binance 2.
Kraken identification mark (not an official logo)

Kraken

Regulatory evidencePoR availabilityFee transparencyRegional availabilityProduct availabilityPublic-record completenessJurisdiction
  • — Regulatory records on file: Coinbase 2 (exact IDs 2) vs Kraken 1 (exact IDs 1).
  • — PoR snapshots on file: Coinbase 0 vs Kraken 1 (PoR ≠ audit).
  • — Fee snapshots on file: Coinbase 1 vs Kraken 2.
  • — Geographic restriction records: Coinbase 5 vs Kraken 16.
Bitget identification mark (not an official logo)

Bitget

Regulatory evidencePoR availabilityFee transparencyRegional availabilityProduct availabilityJurisdiction
  • — Regulatory records on file: Coinbase 2 (exact IDs 2) vs Bitget 1 (exact IDs 0).
  • — PoR snapshots on file: Coinbase 0 vs Bitget 1 (PoR ≠ audit).
  • — Fee snapshots on file: Coinbase 1 vs Bitget 2.
  • — Geographic restriction records: Coinbase 5 vs Bitget 28.
Bybit identification mark (not an official logo)

Bybit

Regulatory evidencePoR availabilityFee transparencyRegional availabilityProduct availabilityJurisdiction
  • — Regulatory records on file: Coinbase 2 (exact IDs 2) vs Bybit 1 (exact IDs 0).
  • — PoR snapshots on file: Coinbase 0 vs Bybit 1 (PoR ≠ audit).
  • — Fee snapshots on file: Coinbase 1 vs Bybit 2.
  • — Geographic restriction records: Coinbase 5 vs Bybit 15.

What remains unresolved

Open questions and missing domains stay unknown. An empty cell is not a safety finding.

  • Coinbase: No crypto-native PoR snapshot row. SEC/audited financials and customer-asset safeguarding disclosures remain separate transparency (see attributedStatements) — not mapped into por[].
  • Coinbase: 2026-09-13 re-check: Coinbase Advanced Trade full maker/taker VIP schedule still behind Help/Cloudflare or signed-in Advanced fees / authenticated brokerage APIs. Recorded only official simple limit-order execution fee (1%). Do not treat 1% as Advanced Trade. Coinbase Exchange fee tables are a different product surface.
  • OKX: Status page located; no dated material incident structured this phase
  • Binance: ADGM Nest trio roles mapped from official ADGM Terms; Binance FZE mapped from FZE Terms + VARA VL/24/04/001. Do not treat any single entity licence as brand-wide global authorisation. Nest Trading Limited role kept as unknown enum (broker-dealer/off-exchange per terms) pending richer role taxonomy.
  • Kraken: Status page located; no dated material incident structured this phase
  • Bitget: FSA Seychelles lists BTG Technology Holdings Limited on the VASP Assessment list (2026-03-09). Not a granted licence. Operator marketing licences (AUSTRAC etc.) were not confirmed on primary registers in this pass; VARA public register has no Bitget VASP licence row (2026-09-13).
  • Bitget: No confirmed primary incident record packaged
  • Bybit: SATOS partnership terms are regional/partner-scoped; not applied as global Bybit custody. Added PoR wallet-disclosure claim only.

Limitations

This is not a “best alternative” ranking. Evidence differences can change as records are re-verified. Regional records do not imply global approval.