Marketplace data inside your network.
For teams that cannot send queries outside their environment: licensed datasets deployed into your cloud, data center or air-gapped network, with access governed by Data.co Control.
Queries that must not leave your network
Some research queries are themselves sensitive — a litigation strategy, a deal target, a patient cohort. Private deployment keeps both the data and the queries inside your boundary.
It is only possible where the provider's license allows a hosted copy. For LAW.co datasets that requires the pending written agreement, so private deployment of LAW.co data is not available yet.
If your concern is governance rather than the queries themselves — who can use external data, for what purpose, with what audit trail — the hosted marketplace accessed through Data.co Control gateways may be enough, and it avoids the cost of operating a copy.
Deployment models
Your cloud
Deployed to your AWS, Azure or GCP account, inside your network controls and key management.
On-premises
Installed on your hardware alongside Data.co Control.
Air-gapped
Delivered with signed offline updates for disconnected networks. The runtime does not call home.
From request to running deployment
- 1
Confirm rights
We confirm with each provider that its license permits a hosted copy in your environment, and on what terms: users, purposes, reporting and retention.
- 2
Design the environment
Compute, storage, network boundary, identity integration and how updates arrive — online sync or signed offline bundles.
- 3
Install and load
Deploy the runtime and load the licensed dataset versions, each with its provenance and license metadata.
- 4
Apply policies
Set Data.co Control policies for who can query which datasets, for which purposes, with approvals where you want them.
- 5
Operate and update
Apply dataset updates as signed releases, keep an audit trail of access, and report usage to providers only where their license requires it.
Hosted, private connection or private deployment
| Need | Hosted marketplace | Private connection | Private deployment |
|---|---|---|---|
| Where queries run | Data.co | Your systems, on a delivered copy | Your environment |
| Where data lives | Provider or Data.co | Your warehouse or storage | Your environment |
| Updates | Live | Scheduled sync | Signed releases |
| API and MCP surface | Yes | No — your own tools | Yes, local |
| Rights required | Per-record access | Redistribution | Hosted copy |
What we will ask you for
Scoping goes faster when these are known up front.
- The datasets you need and the intended uses
- The number and type of users, people and agents
- Target environment: cloud account, data center or air-gapped network
- Identity provider for user and agent access
- How updates may enter the environment
- Retention and deletion requirements
- Your security review process and contacts
What a hosted-copy license usually covers
A provider that allows a hosted copy typically sets conditions: who may query it, whether outputs may be shared outside your organization, whether the data may be used to train or evaluate models, how long the copy may be kept after the agreement ends, and whether aggregate usage must be reported. These terms are agreed with the provider before deployment and enforced in configuration where they can be.
When a license ends or a provider withdraws rights, the deployment removes the affected dataset version on the next update and logs the removal. That revocation path is part of the design, not an afterthought.
What comes with it
- Same API and MCP surface as the hosted marketplace
- Access policies and audit logs via Data.co Control
- Signed dataset updates
- License terms enforced in the deployment
- Usage reporting back to providers where required
- Managed operation available
- Documentation for your security review
Questions buyers ask
Can we deploy LAW.co data privately today?
No. Private hosting of LAW.co data needs the written LAW.co–Data.co agreement, which is pending. We can scope the deployment now so it is ready when rights are confirmed.
Do providers see our queries?
Not in a private deployment. Providers may receive aggregate usage reporting if their license requires it, which is disclosed up front.
Is the local API the same as the hosted one?
It is designed to be: the same v1 envelope with data, meta and error, the same scopes and the same MCP tools, so code written against the hosted marketplace can be pointed at the local endpoint.
How are dataset updates delivered to an air-gapped network?
As signed release bundles you transfer through your own process. The runtime verifies signatures before loading and keeps the previous version until the new one passes checks.
Does private deployment meet our regulatory requirements?
It is designed to support your controls by keeping data and queries in your boundary and logging access. Whether your use meets a given regulation is for your own review.
Scope a private deployment.
Tell us the datasets, environment and constraints. We will confirm licensing and propose an architecture.