How it works
Four steps, no ceremony
The path from first call to production decisions, exactly as we run it.
01
Scoping call → Order Form
We map your stack and goals, agree which modules fit, and put the selection on an Order Form under the standard MSA. If a module is not a fit, we say so on this call.
02
Sandbox keys + schema mapping
You get sandbox credentials the same week. Together we map your event schema to the platform's ingestion format and confirm identity and consent fields.
03
Integration + joint validation
Your team integrates over REST, webhooks or the SDK. We validate the data flowing in, then run first decisions against a holdout so measured behaviour — not opinion — decides go-live.
04
Production rollout + reviews
Progressive rollout with uplift reported against the holdout, monthly. Quarterly reviews cover model performance, experiment backlog and any Order Form changes.
Environments, auth, versioning
| Environments | Separate sandbox and production, each with its own keys and data. Nothing crosses between them. |
|---|---|
| Authentication | API keys per environment · OAuth2 client credentials for server-to-server |
| APIs | versioned paths (/v1/…) · breaking changes only in new versions · deprecation windows in writing |
| Delivery | REST request/response for decisions, webhooks for asynchronous outputs, thin client SDKs where they help. |