CI/CD is an add-on available separately, on any plan.
CI/CD separates where you build (Development) from where the business uses it (Production). You change pipelines, transformations, dashboards, agents, notebooks, flows and clusters in Development, check them, request the send and someone else approves. Only then does Production change — and if something goes wrong, Roll back returns Production to how it was.
What you get#
- Two environments with separate data. Development has its own datasets
(
dev_<customer>_bronze,_silver,_gold); Production usesprd_<customer>_*. - A standard pipeline, always the same: change → version → validate → approval → deploy → check. See The standard pipeline.
- Real approval. Whoever requests the send never approves their own request.
- One-click rollback, with Production restored to its previous state.
- Your Git repository (optional) — GitHub or GitLab (or Azure DevOps). See Connect the repository.
- Per-person access in each environment, with ready-made profiles. See Approvers and access.
Get started in three steps#
1. Create Development
In ETL/ELT → CI/CD, Environments section, use Create development environment. Production definitions are copied; data and credentials are not.
2. Build in Development
Switch environments in the top switcher (Development | Production). A yellow bar reminds you that you are in Development.
3. Send to Production
Back in CI/CD, the list shows what changed. Use Send to production; the pipeline validates, asks for approval and deploys.