Background lines

Where it runs

Waypoint runs in Waypoint's cloud or self-hosted in your own environment, with the model provider you already use & the same product either way, so where your data lives & whose model reads it are your decisions.

Our cloud or yours

Run Waypoint as a service in Waypoint's cloud, or self-hosted inside your own environment, so your cases, tables & documents stay where your security team wants them. Everything runs where you put it, including the sandboxes that execute code for your pipelines. Start in Waypoint's cloud from the trial; for self-hosted, tell us what you run.

Bring your own model

Chip works with the model provider you already use, so the model & the account stay yours. An administrator adds a model configuration under Integrations: a name, the provider, the model & the credentials, which are stored encrypted & never shown again. Once added, it appears by name wherever a step chooses its model & a step that names it runs on nothing else. A workspace holds more than one, so a labeling step runs on a small model & the judgement step on a large one.

What stays where

  • Your data is held in your workspace, apart from every other workspace's; every query stays inside it.
  • Connected systems stay the system of record. Waypoint reads the mirror & writes back only what a pipeline you switched on tells it to.
  • Credentials for connected systems & model providers are stored encrypted & are write-only: set once, never read back.
  • Code & coding agents run in isolated sandboxes, one per run; the sandbox runs in your environment when Waypoint does.
  • Model calls go to the provider you chose & nowhere else.

Read next