
# Dagster OSS

Data orchestration platform for developing, scheduling and observing data-asset workflows.

Canonical page: https://launchinyourcloud.com/directory/dagster/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Dagster OSS

Data orchestration platform for developing, scheduling and observing data-asset workflows.

- Listing: https://launchinyourcloud.com/directory/dagster/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Dagster; Dagster commercial services are separate.
- Licensing model: open-source
- Installation: Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage.
- Architecture: Customer-operated orchestration services, code servers and run storage with configured run-launcher containers
- Operations: Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.
- Product website: https://dagster.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

- workflow-orchestration: Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md (checked 2026-11-12). 


### Cloud deployment evidence

- Dagster OSS Docker Compose deployment on EC2 (aws): https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-10.

- Current maintenance and contributor credits: https://github.com/dagster-io/dagster/releases

- Named organization case studies: https://dagster.io/customers

### Sources

- Official installation and runtime: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md

- Upstream project and capabilities: https://github.com/dagster-io/dagster

- Current upstream license: https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE

- OSS deployment scope: https://dagster.io/docs/deployment/oss

### Licensing sources

- https://raw.githubusercontent.com/dagster-io/dagster/master/LICENSE

### Infrastructure sources

- https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. 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. Scope: Dagster OSS versus commercial hosted control-plane identity; native/configured OSS federation remains unconfirmed. Source: https://docs.dagster.io/deployment/oss/oss-deployment-architecture (reviewed 2026-11-20). Supporting source: Dagster+ plan-specific SSO, separate from OSS — https://dagster.io/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/dagster-io/dagster/blob/master/docs/docs/deployment/oss/deployment-options/docker.md (reviewed 2026-11-14). Deployment artifact: https://github.com/dagster-io/dagster/tree/master/examples/deploy_docker. Artifact reference: master example (moving).

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Current OSS component topology and replication constraints; numeric workload sizing remains unconfirmed. Source: https://docs.dagster.io/deployment/oss/oss-deployment-architecture (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Dagster 1.13.30 OSS core; not a Dagster+ entitlement; software terms only, excluding infrastructure and operations. Source: https://github.com/dagster-io/dagster/blob/1.13.30/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: dagster-io/dagster core release; integration libraries use a separate version series and provider packages may differ. Source: https://github.com/dagster-io/dagster/releases/tag/1.13.30 (reviewed 2026-11-14).






