Dagster+ Hybrid deployment

In a Dagster+ Hybrid deployment, the orchestration control plane is run by Dagster+ while your Dagster code is executed within your environment.

For an overview of the Hybrid design, including security considerations, see Dagster+ Hybrid architecture.

Getting started

To get started with a Hybrid deployment, you'll need to:

1. Create a Dagster+ organization.
2. Install a Dagster+ Hybrid agent in your environment:
   • Kubernetes
   • AWS ECS
   • Docker
   • Microsoft Azure
3. Add a code location to your deployment, typically using a Git repository and CI/CD.

tip

If you're not sure which agent to use, we recommend the Dagster+ Kubernetes agent in most cases.

note

If you are migrating from from Dagster+ Serverless, see the Dagster+ Serverless to Hybrid migration guide.

Best practices

Recommended compute resources

• Agent container - Start at 0.25 vCPU core and 1 GB RAM, then scale with concurrent runs and the number and size of code locations.
• Code server container - Budget for imports, plus the definition graph, and any heavy initialization. We recommend starting with 0.25 vCPU cores and 1GB RAM.
• Runs: 4 vCPU cores, 8-16 GB of RAM depending on the workload

For compute-heavy jobs, increase memory and/or CPU where the run workers are (i.e. Kubernetes pods or ECS tasks), not just the code server.

Security

To make your Dagster+ Hybrid deployment more secure, you can:

• Disable log forwarding
• Manage tokens