Feature Coinbase CDP Facilitator Self-hosted facilitator
Operational burden None — Coinbase runs it Winner You run it
Cost (low volume) Free up to ~1000 settlements/month Winner RPC costs + your gas + ops
Take-rate flexibility Coinbase-set You set it (e.g. 1.5% via proxy) Winner
Multi-network support 22 networks out of the box Winner Whatever you wire up
Censorship resistance Subject to Coinbase ToS Self-controlled Winner
Audit transparency Coinbase-managed Your ledger (e.g. public SQLite) Winner
Coinbase CDP Facilitator Wins
3
Ties
0
Self-hosted facilitator Wins
3

Final Verdict

Default to Coinbase CDP. Self-host (or run a take-rate proxy in front of CDP) only when you have a real reason: custom take-rate, censorship-resistance, or a public take-rate ledger as a feature.

The hybrid pattern

Most production deployments run a thin take-rate proxy that calls Coinbase CDP under the hood and writes settlement metadata to a local append-only ledger. You get most of the operational simplicity with the audit and take-rate features.

Pro Tips

Start with CDP. Add a take-rate proxy when (and only when) you have third-party listings to monetise.
A public ledger of every settlement is a marketing asset; it justifies the operational cost of a proxy.
Copied to clipboard!