Deployment

Spin up DataForge in a new environment, or stand up a self-managed instance.

Quick start (Standard / SaaS)

• Cloud Quickstarts — Terraform-driven setup, ready in ~15 minutes on AWS or Azure

Private Enterprise deployment

Full self-managed installs with detailed Terraform, networking, and Databricks configuration:

• Private Deployment — AWS
• Private Deployment — Azure

Shared deployment tasks

These articles apply to either cloud:

• External API — create machine credentials, request M2M tokens, and use the /m2m/* routes
• Resetting Databricks Service Account
• Updating Terraform to use Databricks Service Principal
• Viewing Source Data

The dataforge Unity Catalog

Every DataForge deployment needs a dataforge catalog in Databricks to host its refining stages and hub tables — on DataForge-hosted and self-managed environments alike:

• Creating the catalog in an AWS workspace
• Creating the catalog in an Azure workspace