Titan

Terraform's Snowflake provider requires broad administrator privileges and stores account topology in external state files that drift over time. Titan replaces remote state backends with declarative Python and YAML definitions that query live Snowflake metadata directly and switch roles dynamically to enforce least privilege. It enables DevOps engineers and data platform teams to version, review, and automate their data warehouse resources through git-driven continuous delivery.

Where Titan fits

Data platform engineers managing Snowflake frequently struggle between two extremes: general-purpose orchestrators like Terraform that require maintaining sensitive remote state backends, and imperative migration runners like Schemachange that depend on manual SQL scripts. Terraform treats Snowflake like cloud infrastructure, binding a single administrative role per provider block. That limitation forces organizations to grant broad administrative rights to CI pipelines or maintain fragile multi-provider setups. Titan executes against live account state without storing intermediate state files, eliminating the risk of secrets leaking through external state storage.

Where tools like Permifrost only manage users and role hierarchies, Titan models the complete resource graph: warehouses, databases, schemas, stages, integrations, and fine-grained grants. Its dynamic role-switching inspects each planned mutation and assumes the minimum required role—such as USERADMIN or SYSADMIN—rather than defaulting to ACCOUNTADMIN. For teams prioritizing access governance, this architecture maintains strict role boundaries across production without breaking automated pipelines.

What it does well

• Declarative Python resource API: Define Snowflake objects as Python dataclasses, using loops, conditionals, and standard type checkers to catch configuration errors before deployment.
• Stateless reconciliation: Blueprints inspect live Snowflake metadata directly, eliminating state synchronization conflicts and stale-state drift.
• Dynamic privilege switching: Detects which role is required for each resource mutation and switches context on the fly, avoiding superuser roles in automation.
• Sync mode with resource pruning: Enforces an exact desired state on schemas or databases by automatically dropping unmanaged resources created outside git.
• Export CLI for legacy accounts: Generates YAML configuration files from existing Snowflake environments to bootstrap version-controlled infrastructure without manual transcription.