Skip to main content

​
How DataFramer connects to your stack

Your stack on the left, DataFramer on the right, and the four connections between themYour stack on the left, DataFramer on the right, and the four connections between them

​
Two ways to deploy

Both run the same application. They differ in where your data is processed and stored.

​
DataFramer-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 model credential; see AI usage and credits. Nothing to deploy — just sign up.

​
Customer-hosted

Use this when your data cannot leave your own cloud. DataFramer keeps the control plane: the web app, job orchestration, and 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. DataFramer's control plane on the left, the data plane in your cloud account on the right; every arrow across the boundary starts on your side DataFramer's control plane on the left, the data plane in your cloud account on the right; every arrow across the boundary starts on your side
  • 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 credential.
  • Same functionality as the DataFramer-hosted version.
Contact us to plan the rollout.