Running a pilot

We run free pilots: 90 days, the full Scale surface, no card. When it ends you convert to Scale or Enterprise, or wind down cleanly on the terms fixed before anything installed.

How it starts

1. Scope it together. Before anything installs, we agree in writing: which systems you’ll connect, what success looks like, and the wind-down terms. You should know on day one exactly what happens on day 90.
2. Sign the pilot terms. Evaluation license for the term, confidentiality, telemetry consent (below), and uninstall-on-exit — with the open-source core explicitly exempt, because it’s yours regardless.
3. Get provisioned. You receive a customer npm token (scoped, read-only, expiring on the pilot end date) and a welcome email with your install path — then you follow the pilot onboarding track.

What we ask of a pilot

• Run with telemetry on. Usage counters (documented exactly in Usage data & telemetry) are how we produce the evidence a pilot decision deserves. It’s in the agreement, you can opt out at any time, and opting out doesn’t end the pilot.
• A working cadence. A 30–60 minute onboarding call to get your first system to 🟢, then a short check-in roughly every two weeks with a usage report built from real counters — never extrapolated.

How success is measured

Against the goals you set in step 1 — typically: time from install to first verified connection, which agents your engineers actually use week over week, and a handful of concrete artifacts (an incident diagnosed, a pipeline shipped, a migration translated) rather than a vanity score.

As the end approaches

Two weeks before the end date we’ll bring the evidence and have the conversation: convert, extend deliberately, or wind down. Wind-down is a documented, honest process — see Ending a pilot — and your data was never in our hands to return.

Start one: [email protected].