Pilot program
Apply to the Driftlock pilot cohort.
The pilot intake takes the structured signal a regulated buyer already collects on a second call — company, repo URL, monorepo LoC tier, primary language, dependency-count bucket, current automation tool, and primary compliance need — and turns it into a one-page brief that lets the cohort reply with a calendar link within two business days. Every submission lands in storage and notifies the operator; nothing leaves the row until the cohort confirms a trial date.
Time to apply
~3 minutes, one screen
Seven dropdowns and two free-text inputs; no file uploads, no second call required to qualify.
Storage
ContactMessage row
Submissions land in the installed contact-form store; the operator email is fired from the same route handler.
Reply window
two business days
The cohort replies with a calendar link, the trial scope document, and a one-page brief on the cohort scope.
Intake
Seven fields, one structured submission.
Each field here maps to a column the Driftlock team already triages against on the second call — the same fields the cohort scrolls in a tabular brief at /docs/compliance. Submitting the form sends the structured record to the operator (driftlock@polsia.app) without leaving the row in storage first.
- One structured intake — seven required fields.Company, repo URL, monorepo LoC tier, primary language, dependency-count bucket, current automation tool, primary compliance need.
- Submissions persist via the same contact-form store.Rows land in ContactMessage; no new schema, no new migration. The operator receives an email notification per submission.
- Pre-trial scoping confirmed within two business days.The Driftlock team replies with a calendar link, the trial scope document, and a one-page brief on the cohort.
- Repo, language, and dependency bucket set the trial agenda.Each cohort installs Driftlock against a real monorepo — the structured fields shape the four trial deliverables the cohort iterates on.
Pilot application
Tell us about your repo, your tooling, and your compliance need.
All fields are required. The structured payload lands in storage and goes to the operator's inbox.
seven fields · structured payload · ContactMessage row · operator notified via the email module
Read the references
Pair the intake with the deep-dive posture.
The structured fields above are short on context by design — the cohort reads more at /docs/compliance (SOC 2 + data-handling), /architecture (sandboxed topology), /pricing (tier composition), and /security (custody + retention). Apply first, read second.
Reply SLA
Driftlock replies within two business days.
Every operator notification includes the structured payload as /api/contactsees it — so the cohort has the same context the operator does when triaging the row.
seven fields · ContactMessage row · operator email fired from the same route