Product
The OpenDOPS CLI
One CLI for standardizing data engineering project structure — structure, metadata, checks, and CI, generated for you. OpenDOPS owns structure; native tools own execution.
Project scaffolding
Generate standardized repos and projects in one command — Databricks bundle monorepos, notebook projects, and dbt projects today, more domains next.
Adopt existing projects
Already building? dops adopt brings an existing dbt or Databricks project under management — inferring metadata from what's on disk, without moving or rewriting a single file.
Conflict-aware upgrades
Pull blueprint improvements into existing projects with dops upgrade. A per-project lock classifies every file as safe-update or conflict, so your local edits are never clobbered.
Branch-isolated sandboxes
A runtime DEV_<branch>_ prefix isolates feature-branch deployments — applied to resource names, workspace paths, or dbt schemas, never committed to config.
Provenance & versioning
Every deploy is stamped with its version and git commit — as resource tags, a dbt query-comment, or a workspace marker — so you always know what's running where.
Generated CI/CD
Ready-made GitHub Actions that call your native CLI directly: validate, sandbox deploy & cleanup, and dev / staging / prod promotion.
Structural checks
check and doctor verify conventions, targets, and metadata with clear, actionable diagnostics — and never call out to your data platform.
Policy & governance
Encode org standards once in .dops/policy.yaml — required owner, allowed blueprints, targets, naming — and check enforces them everywhere, with a pre-commit hook.
Changed-project detection
Map a git diff to exactly the affected projects — with --format github-json for CI matrices.
The core principle
OpenDOPS owns structure. Your native tools own execution.
It scaffolds, validates, and standardizes project structure across your data stack — and never replaces your native CLIs, provisions infrastructure, manages Terraform, or stores secrets.
Built for the modern data engineering stack
OpenDOPS owns structure
- Scaffolds standardized repos and projects per domain — or adopts existing ones
- Generates project config, a src/ Python package, and tests
- Writes .dops metadata and CI/CD workflows
- Runs structural checks, enforces org policy, and detects changed projects
- Upgrades projects to newer blueprints without clobbering local edits
- Stamps deploy provenance and tracks the version live in each environment
- Generates stable sandbox / dev / staging / prod conventions
Native tools own execution
OpenDOPS deliberately does not:
- ✕Replace your native CLIs or hide their behavior
- ✕Validate, deploy, run, or destroy resources
- ✕Provision workspaces, warehouses, schemas, or cloud resources
- ✕Manage Terraform or store secrets
- ✕Mutate project config for feature branches
Ship standardized data engineering projects.
Install the dops CLI and scaffold your first
standardized project in under a minute.