Ending a pilot

Every pilot has a scheduled end, agreed in writing before it starts. Here is exactly what happens if you don’t convert — no surprises, no hostage data.

What you keep

• Your data — because it never left. Credentials and data stayed on your systems throughout; there’s nothing for us to return or delete on the data plane.
• Everything the agents produced for you: pipelines, documentation, fixes, analyses — they’re in your systems and your repos.
• Your context graph. Export it to DataHub or OpenMetadata before the end date; your named engineer will help.
• Your audit trail. Export receipts and audit logs for your records.
• The open-source core — forever. Apache 2.0 is its license; wind-down doesn’t touch it.

What ends

• The evaluation license expires on the agreed date.
• Your customer npm token is revoked (private packages stop installing — expected).
• Any hosted workspace is deprovisioned, with residual operational data purged on a 90-day clock.
• The pilot support channel closes.

Your checklist (about 30 minutes)

1. Export the context graph and audit logs you want to keep.
2. Remove the MCP server from team clients: claude mcp remove data-workers (or your client’s equivalent).
3. Clear the npm token: npm config delete //registry.npmjs.org/:_authToken.
4. Delete connector environment variables / service-account credentials you created, and revoke those service accounts in your systems.
5. Expect private-package installs to fail afterward — that’s the checkpoint that revocation worked.

(Your pilot agreement explicitly exempts the Apache-2.0 open-source core from uninstall-on-exit — anything your team runs under that license is yours to keep running, with community support.)

What we do on our side

Within five business days of the end date: revoke the token, deprovision hosted resources, start the 90-day purge clock, confirm telemetry from your installs has gone silent, and close out the support channel.

It’s reversible

Winding down doesn’t burn a bridge. Your export is importable again, the OSS core keeps working, and a later start picks up where the graph export left off.