Enterprise
Built for teams with obligations
When on-chain history feeds trading systems, risk models, and production research, it stops being a convenience and starts being a dependency. Enterprise engagements exist for exactly that case.
What enterprise adds
Beyond the price sheet
- Volume without ceremony
- Full-history archives delivered at the scale quantitative research and model-training workloads actually require.
- Governance & access control
- Organization-level controls over who can access which datasets, with auditable usage records.
- Delivery into your cloud
- Parquet drops into object storage you control, so data lands where your governance already applies.
- Private & dedicated options
- Dedicated pipelines and private deployment models for teams with isolation requirements.
- Named technical support
- Direct access to the engineers responsible for the datasets you depend on — not a ticket queue.
- Clear operational ownership
- Published processing status, incident communication, and explicit ownership of every dataset we operate.
How an engagement runs
Evaluate first. Commit after.
01
Scope
Tell us the datasets, windows, and delivery targets. We confirm coverage and any gaps against your requirements.
02
Evaluate
Your engineers get sample partitions and manifests to validate schemas, completeness, and integration before any commitment.
03
Contract
License terms, invoicing or wire payment, and procurement paperwork handled directly with our team.
04
Deliver
Files land in your S3 or GCS buckets — as a one-time archive or kept current on each dataset's cadence.
What we will put in writing
- File-level checksums and immutable published versions
- Documented lineage for every dataset you license
- Corrections republished to you at no cost
- Named engineering contacts for the datasets you depend on
- Clear incident communication when something goes wrong
What we won't claim
We don't decorate this site with certification badges we haven't earned, customer logos we don't have, or uptime numbers nobody has audited. Specific commitments — delivery cadences, support response, liability — belong in a signed agreement, where they mean something. That's where we put them.
Start the conversation