How DataFramer connects to your stack
Two ways to deploy
Both run the same application. They differ in where your data is processed and stored.Cloud-hosted
Everything runs in DataFramer’s cloud, and your data is stored there, scoped to your company. Model calls run on DataFramer credits, or on your own provider keys if you add them under Settings → Keys. Setup is signing up, then connecting your traces; there is nothing to deploy.Customer-hosted
Use this when your data cannot leave your own cloud. DataFramer keeps the control plane: the web app, sign-in, the API, workflow orchestration, billing, and a database of metadata. You run the data plane in your own cloud account, deployed with our Terraform module: the workers that process your data and the storage they use.- Your content stays in your account.
- No inbound connections. Every connection that crosses the boundary starts in your account or in your browser.
- Model calls use your own provider keys.
- Same functionality as the cloud-hosted version.