Teradata VantageCloud

Use it when

• You run one of the large Teradata estates; VantageCloud Enterprise carries the same architecture to the cloud without redesign, and Lake is the modernization path.
• Mixed enterprise workloads need explicit control; TASM workload groups, priority classes, and service-level goals police thousands of concurrent requests deliberately.
• In-database analytics (ClearScape ML, time series, path analysis) should run where the data is.
• On-premises must remain an option alongside AWS, Azure, and Google Cloud.

Think twice when

• You are greenfield; consumption pricing against a committed multi-year term enters well above pay-as-you-go warehouses, and the platform assumes enterprise scale.
• The team lacks Teradata skills; primary-index design and workload management are deliberate crafts, not defaults.
• Elastic zero-ops economics is the goal; Snowflake and BigQuery are built around it, Teradata is built around control.

How it runs

VantageCloud Lake runs object-storage-backed MPP with compute clusters scaling independently per workload; Enterprise runs the classic coupled architecture in the cloud or on-premises (IntelliFlex). Billing is Teradata Units against a committed term. Iceberg and Delta are readable and writable through Glue, HMS, or Unity catalogs.