Dagster OSS
Data orchestration platform for developing, scheduling and observing data-asset workflows.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage.
Runs in
Documented customer environment
Customer-operated orchestration services, code servers and run storage with configured run-launcher containers
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Dagster OSS Docker Compose deployment on EC2 ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage. |
|---|---|
| Infrastructure | Servers / containers Customer-operated orchestration services, code servers and run storage with configured run-launcher containers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core Apache License 2.0 for upstream Dagster; Dagster commercial services are separate. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | Apache License 2.0 for upstream Dagster; Dagster commercial services are separate. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The OSS guide establishes a self-hosted webserver/daemon/code-location deployment, while the vendor pricing page describes SSO/SAML in Dagster+ plans. These sources do not establish a shipped external IdP login for the listed OSS distribution. Verify a version-matched ingress/authentication integration and protect its UI/GraphQL access; hybrid worker deployment alone does not self-host the Dagster+ control plane.
Dagster OSS versus commercial hosted control-plane identity; native/configured OSS federation remains unconfirmed · Source ↗ · Dagster+ plan-specific SSO, separate from OSS ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The OSS guide links a Compose example with webserver, daemon, user-code containers and PostgreSQL run storage. Runs may launch separate containers; capacity and container access need application-specific planning.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (master example (moving)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The OSS architecture specifies long-running webserver, daemon and code-location services plus instance storage and run workers, but not a universal numeric CPU/RAM/storage minimum. Code-location, job and executor demand determine capacity. The daemon and code-location replication constraints must be reviewed before treating extra webserver replicas as complete HA.
Current OSS component topology and replication constraints; numeric workload sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Dagster 1.13.30 OSS core; not a Dagster+ entitlement; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was 1.13.30, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
dagster-io/dagster core release; integration libraries use a separate version series and provider packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This listing covers fully self-hosted OSS Dagster, not the commercial hybrid control plane. Integrations, run launchers and user code can use external services. Secure network access to the OSS management services.
Community & maintenance
The upstream release stream records continuing November 2026 fixes and credits external contributors. Dagster also publishes named organization case studies; those demonstrate ecosystem adoption rather than a specific OSS deployment boundary.
Category fit
- Workflow orchestration
- Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code.
Compare within Workflow orchestration
- Apache AirflowWorkflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.
- AWS
- DigitalOcean
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- HashiCorp Nomad EnterpriseCommercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.
- AWS
- Azure
- Google Cloud
- Kestra Self-HostedSelf-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Prefect ServerSelf-hosted workflow server and Python framework for resilient task and data pipelines.
- AWS
- Azure
- Google Cloud
- Northflank
- Temporal Self-HostedOrchestrate durable application workflows with a customer-operated Temporal Service.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow orchestration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗github.com
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- OSS deployment scope ↗dagster.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Dagster OSS Docker Compose deployment on EC2 ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project explicitly identifies an AWS EC2 host for its OSS Docker Compose deployment, including webserver, daemon and code-location containers. Review current images, persistence, secrets and production hardening; this is separate from Dagster Plus and its customer-cloud agent.
- Dagster OSS Docker Compose deployment on EC2 ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Current maintenance and contributor credits ↗github.com
- Named organization case studies ↗dagster.io