Paid pilots.
One archive.
Prove CORPUS on one of your real archives, inside your own cloud account. Pilots are paid, so both sides commit: you bring the archive and the budget, we bring the founder's time. Price is discussed on the call.
Paid pilots · a few at a time
What a paid pilot includes
Paid pilot
Fixed scope
One archive, inside your own cloud account.
- One archive you choose
- You apply our Terraform on a guided call
- We never hold credentials or receive your data
- Per-file audit report at the end
Before it starts
One call
We scope the pilot with you and put it in writing.
- Your archive, formats and languages
- Whose data it is and who signs off
- Your cloud account and timeline
- Scope, price and terms: pilot terms are agreed in writing
Who qualifies
We check all five on the call. Only teams ready to pay for a pilot qualify.
- 01
Your own data
Records your company created, or holds the rights to license. Not resold, scraped or bought in.
- 02
Legal in the loop
A legal or privacy owner who signs off before any data leaves.
- 03
Your cloud account
A cloud account you control (Azure for pilots now; AWS and Google Cloud next), and an engineer for the guided setup.
- 04
A real archive
An archive you hold today, and a buyer or use in view: an AI lab asking, a deal in discussion, or an internal project waiting on it.
- 05
Budget for a pilot
Budget to pay for a pilot, and someone who can approve it.
We don't accept
- Brokers or resellers without rights to the underlying data
- Scraped, bought-in or unclear-provenance datasets
- Teams with no archive or buyer yet, just exploring the market
- Requests to send data to us. We never host it.
How a pilot works
- 01
Request a call
No data, just a description.
- 02
Scope
Your archive, your rights, your environment.
- 03
Terms in writing
Scope and price agreed before anything starts.
- 04
Set up
You apply our Terraform. No internet access during processing.
- 05
First dataset
Verified files plus a per-file audit report.
Before you ask
Why paid pilots only?
A paid pilot means both sides are committed: you put a real archive and budget behind it, and we put the founder's time into setup, tuning and the audit report. We run a few pilots at a time.
What does it cost?
It depends on the scope: the archive, its formats and languages. We discuss price on the call; pilot terms are agreed in writing before anything starts.
Do you ever see our data?
No. CORPUS runs inside your own cloud account, on a private network with no internet access during processing. You apply our Terraform yourself on a guided call, so we never hold credentials in your account. Calls and forms use descriptions and synthetic look-alikes, never real files.
Which clouds do you support?
Azure, for pilots now. AWS and Google Cloud are next. You provide the cloud account and blob storage; CORPUS runs there for as long as you keep it, and you can destroy it at any time.
Is the output HIPAA or GDPR compliant?
CORPUS is a tool, not a certification or legal advice, and makes no compliance claim; that determination is yours. Under GDPR, consistent keyed replacement is pseudonymization (Recital 26), so treat the output as personal data. Under HIPAA, Safe Harbor or an expert's determination decides. You keep the keys, the mappings and a per-file audit report.
What does a paid pilot involve?
One archive you choose, inside your own cloud account. You apply our Terraform on a guided call; we never hold credentials or receive your data. It ends with a per-file audit report: what was found, what was replaced, what was held back, and why.
Who qualifies?
Teams with their own data or the rights to license it, a legal or privacy owner who signs off, a cloud account they control, a real archive with a buyer or use in view, and budget for a paid pilot.
What if we're not ready yet?
Join the waitlist. We'll email you when CORPUS opens more widely.