Explore
diff --git a/src/content/docs/learn/capabilities-and-comparison/feature-comparison.mdx b/src/content/docs/learn/capabilities-and-comparison/feature-comparison.mdx
index 8b47bbea..963ea07f 100644
--- a/src/content/docs/learn/capabilities-and-comparison/feature-comparison.mdx
+++ b/src/content/docs/learn/capabilities-and-comparison/feature-comparison.mdx
@@ -1,6 +1,6 @@
---
title: Feature comparison
-description: Compare features across Tiger Cloud on AWS, Tiger Cloud on Azure, and self-hosted TimescaleDB
+description: Compare features across Tiger Cloud on AWS, Tiger Cloud on Azure, self-hosted TimescaleDB, and TimescaleDB Enterprise
products: [cloud, self_hosted]
---
diff --git a/src/content/docs/learn/enterprise/enterprise-exclusive-features.mdx b/src/content/docs/learn/enterprise/enterprise-exclusive-features.mdx
new file mode 100644
index 00000000..e9b004e8
--- /dev/null
+++ b/src/content/docs/learn/enterprise/enterprise-exclusive-features.mdx
@@ -0,0 +1,10 @@
+---
+title: Key differentiators of TimescaleDB Enterprise
+description: What TimescaleDB Enterprise adds over self-hosted TimescaleDB Community Edition, and who it is for
+keywords: [timescaledb enterprise, high availability, backups, upgrades, monitoring, cloud sync]
+# products: [enterprise] — add once the "enterprise" product tag is added to content.config.ts
+---
+
+import EnterpriseExclusiveFeatureDetails from "@partials/_enterprise-exclusive-feature-details.mdx";
+
+
\ No newline at end of file
diff --git a/src/content/docs/learn/enterprise/high-availability.mdx b/src/content/docs/learn/enterprise/high-availability.mdx
new file mode 100644
index 00000000..42a6f97c
--- /dev/null
+++ b/src/content/docs/learn/enterprise/high-availability.mdx
@@ -0,0 +1,8 @@
+---
+title: About high availability
+description: How TimescaleDB Enterprise provides automatic failover for a self-managed cluster
+keywords: [timescaledb enterprise, high availability, failover]
+# products: [enterprise] — add once the "enterprise" product tag is added to content.config.ts
+---
+
+For step-by-step setup, see [Configure high availability](/deploy/enterprise/high-availability).
\ No newline at end of file
diff --git a/src/content/docs/learn/enterprise/hybrid-architectures.mdx b/src/content/docs/learn/enterprise/hybrid-architectures.mdx
new file mode 100644
index 00000000..6becc72c
--- /dev/null
+++ b/src/content/docs/learn/enterprise/hybrid-architectures.mdx
@@ -0,0 +1,12 @@
+---
+title: Hybrid architectures with Cloud Sync
+description: Why and how to combine a self-managed TimescaleDB Enterprise cluster with Tiger Cloud
+keywords: [timescaledb enterprise, cloud sync, hybrid architecture]
+# products: [enterprise] — add once the "enterprise" product tag is added to content.config.ts
+---
+
+For step-by-step setup, see [Configure Cloud Sync](/deploy/enterprise/cloud-sync).
+
+## Why hybrid instead of one or the other
+
+## The pattern
\ No newline at end of file
diff --git a/src/content/docs/learn/enterprise/index.mdx b/src/content/docs/learn/enterprise/index.mdx
new file mode 100644
index 00000000..0ae1fab1
--- /dev/null
+++ b/src/content/docs/learn/enterprise/index.mdx
@@ -0,0 +1,28 @@
+---
+title: Meet TimescaleDB Enterprise
+description: Learn about TimescaleDB Enterprise, a self-managed, commercially licensed TimescaleDB for on-premises and edge deployments
+keywords: [timescaledb enterprise, on-premises, self-managed, air-gap]
+# products: [enterprise] — add once the "enterprise" product tag is added to content.config.ts
+---
+
+import { RelatedContentCards, RelatedContentCard } from "@components/RelatedContentCards";
+import { Image } from "astro:assets";
+import imgConsole from "../../../../assets/images/learn/enterprise/enterprise-console-clusters-overview.png";
+
+## Who it's for
+
+## How it works
+
+For step-by-step guides, see [Deploy](/deploy/enterprise).
+
+## One console for everything
+
+
+
+## Learn more
+
+
+
+
+
+
\ No newline at end of file
diff --git a/src/content/docs/learn/index.mdx b/src/content/docs/learn/index.mdx
index 45a03fc4..8b0d489c 100644
--- a/src/content/docs/learn/index.mdx
+++ b/src/content/docs/learn/index.mdx
@@ -10,19 +10,37 @@ import {
} from "@components/RelatedContentCards";
import * as C from "@constants";
+## Explore by product
+
+{C.COMPANY} products are built on {C.TIMESCALE_DB}, the open-source {C.PG} extension for time-series
+and real-time analytics. You can run it yourself, or choose a product that packages the same engine
+with production operations and support.
+
+
+
+
+
+
## Explore by topic
+These cover the {C.TIMESCALE_DB} engine and data-management concepts, which work the same across
+{C.SELF_LONG}, {C.CLOUD_LONG}, TimescaleDB Enterprise, and {C.MST_LONG}. Some features noted below,
+like tiered storage, are specific to a particular product.
+
-
-
\ No newline at end of file
diff --git a/src/content/docs/learn/tiger-cloud/index.mdx b/src/content/docs/learn/tiger-cloud/index.mdx
index 042391b4..905e0846 100644
--- a/src/content/docs/learn/tiger-cloud/index.mdx
+++ b/src/content/docs/learn/tiger-cloud/index.mdx
@@ -1,5 +1,5 @@
---
-title: Tiger Cloud
+title: Meet Tiger Cloud
description: Learn about Tiger Cloud, a fully managed cloud database service built on TimescaleDB and PostgreSQL for time-series and analytics workloads
products: [cloud]
keywords: [tiger cloud, managed database, cloud database]
@@ -16,39 +16,47 @@ learnMore:
import * as C from "@constants";
import { RelatedContentCards, RelatedContentCard } from "@components/RelatedContentCards";
+import { Image } from "astro:assets";
+import imgConsole from "../../../../assets/images/get-started/quickstart/tiger-console-services-view.png";
-{C.CLOUD_LONG} runs {C.TIMESCALE_DB} on {C.PG} as a managed service. You use {C.HYPERTABLE}s, {C.HYPERCORE},
-{C.CAGG}s, and {C.HYPERFUNC} as usual, while backups, upgrades, scaling, and infrastructure are handled for you,
-along with tiered storage, {C.HA_REPLICA}s and {C.READ_REPLICA}s, and observability in {C.CONSOLE}.
+{C.CLOUD_LONG} is a fully managed cloud database service built on {C.PG} and {C.TIMESCALE_DB}. It is
+the same engine you would run yourself, operated for you, so you get {C.HYPERTABLE}s, {C.HYPERCORE},
+{C.CAGG}s, and {C.HYPERFUNC} without provisioning or maintaining any infrastructure.
-## What {C.CLOUD_LONG} adds
+## Who it's for
-On top of the core {C.TIMESCALE_DB} capabilities, {C.CLOUD_LONG} includes:
+{C.CLOUD_LONG} is for teams that want a production time-series and analytics database without
+operating it themselves:
-- **Tiered storage**: automatically move older data to low-cost object storage while keeping it queryable.
- This enables virtually unlimited data retention at a fraction of the cost of high-performance storage.
-- **{C.HA_REPLICA_CAP}s**: automatic failover replicas that keep your {C.SERVICE_SHORT} online
- if the primary instance becomes unavailable.
-- **{C.READ_REPLICA_CAP}s**: offload read-heavy workloads like dashboards, reporting, and analytics queries
- to dedicated {C.READ_REPLICA}s.
-- **Built-in observability**: {C.CONSOLE} provides query-level insights, resource monitoring, and
- alerting without additional tooling.
-- **Automated operations**: backups, {C.PG} upgrades, {C.TIMESCALE_DB} updates, and security patches
- are handled automatically.
-- **Data connectors**: ingest data from sources like S3, Kafka, and {C.PG} using built-in connectors,
- and export to Apache Iceberg for lakehouse integration.
+- **Teams that can run in a public cloud** and want backups, high availability, scaling, upgrades,
+ and observability handled for them.
+- **Teams that want to move fast**, from a first project through to production, without building
+ operational tooling along the way.
-## Available on AWS and Azure
+If your data must stay on infrastructure you operate, on-premises, at the edge, or air-gapped, see
+[TimescaleDB Enterprise](/learn/enterprise) or [{C.SELF_LONG}](/deploy/self-hosted).
-{C.CLOUD_LONG} runs on Amazon Web Services (AWS) and Microsoft Azure, with services available in
-regions across North America, Europe, Asia Pacific, and South America. See
-[supported regions](/get-started/supported-regions) for the full list of available regions by cloud provider.
+## How it works
+
+{C.CLOUD_LONG} runs your database on Amazon Web Services (AWS) or Microsoft Azure, in regions across
+North America, Europe, Asia Pacific, and South America. You work with {C.HYPERTABLE}s, {C.CAGG}s, and
+full {C.PG} as usual, while operations like backups, upgrades, scaling, high availability, and
+observability are managed for you in {C.CONSOLE}. See
+[supported regions](/get-started/supported-regions) for the full list.
+
+## One console for everything
+
+
+
+{C.CONSOLE} is the command center for {C.CLOUD_LONG}. From it you create and manage {C.SERVICE_SHORT}s,
+monitor performance, run queries, configure backups and high availability, scale compute and storage,
+and read logs and metrics.
## Learn more
+
-
diff --git a/src/partials/_cloud-exclusive-feature-details.mdx b/src/partials/_cloud-exclusive-feature-details.mdx
index 78cf0bce..c96c8a03 100644
--- a/src/partials/_cloud-exclusive-feature-details.mdx
+++ b/src/partials/_cloud-exclusive-feature-details.mdx
@@ -1,6 +1,21 @@
import * as C from "@constants";
import { Callout } from "@stainless-api/docs/components";
+{C.TDB_COMMUNITY} is the open-source {C.TIMESCALE_DB} engine you install and operate yourself.
+{C.CLOUD_LONG} runs the same engine as a fully managed service and adds the platform capabilities you
+would otherwise build and operate. This page covers what {C.CLOUD_LONG} adds. For what the product is
+and who it is for, see [Meet {C.CLOUD_LONG}](/learn/tiger-cloud).
+
+{C.CLOUD_LONG} adds:
+
+- **Tiered storage**: move older data to low-cost object storage while keeping it queryable.
+- **{C.HA_REPLICA_CAP}s**: automatic failover to a synchronized replica.
+- **{C.READ_REPLICA_CAP}s**: dedicated replicas for read-heavy workloads.
+- **Built-in observability**: query insights, metrics, and alerting in {C.CONSOLE}.
+- **Data connectors**: managed ingestion from {C.PG}, S3, and Kafka, and export to Iceberg.
+- **Managed security and compliance**: encryption, network isolation, and SOC 2 compliance.
+- **Automated operations**: managed backups, upgrades, and scaling.
+
## Tiered storage
{C.CLOUD_LONG} provides a [hierarchical storage architecture](/learn/data-lifecycle/storage/about-storage-tiers) with two tiers:
@@ -22,7 +37,7 @@ or [Azure](/deploy/tiger-cloud/tiger-cloud-azure/high-availability/high-availabi
## {C.READ_REPLICA_CAP}s
-Offload read-heavy workloads — dashboards, reporting queries, and analytics — to dedicated
+Offload read-heavy workloads such as dashboards, reporting queries, and analytics to dedicated
{C.READ_REPLICA}s. {C.READ_REPLICA_CAP}s receive streaming replication from the primary and serve
read-only queries independently, which helps avoid resource contention on the primary. Set up
{C.READ_REPLICA}s on [AWS](/deploy/tiger-cloud/tiger-cloud-aws/high-availability/read-scaling)
diff --git a/src/partials/_enterprise-exclusive-feature-details.mdx b/src/partials/_enterprise-exclusive-feature-details.mdx
new file mode 100644
index 00000000..91a5dbff
--- /dev/null
+++ b/src/partials/_enterprise-exclusive-feature-details.mdx
@@ -0,0 +1,15 @@
+For step-by-step guides, see [Deploy](/deploy/enterprise).
+
+## High availability
+
+## Automated backups
+
+## Low-downtime upgrades
+
+## Built-in monitoring
+
+## Cloud Sync
+
+## Enterprise support
+
+## Compare features across products
\ No newline at end of file
diff --git a/src/partials/_feature-comparison.mdx b/src/partials/_feature-comparison.mdx
index 989eb92d..8fe7951e 100644
--- a/src/partials/_feature-comparison.mdx
+++ b/src/partials/_feature-comparison.mdx
@@ -1,23 +1,23 @@
import * as C from "@constants";
import { Callout } from "@stainless-api/docs/components";
-This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLOUD_LONG} on Azure**, and **{C.SELF_SHORT} {C.TDB_COMMUNITY}**.
+This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLOUD_LONG} on Azure**, **{C.SELF_SHORT} {C.TDB_COMMUNITY}**, and **{C.TIMESCALE_DB} Enterprise**.
**Best-in-class {C.PG} performance**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Automatic partitioning via {C.HYPERTABLE}s for efficient indexes and faster ingest | ✅ | ✅ | ✅ |
-| {C.CAGG_CAP}s | ✅ | ✅ | ✅ |
-| Time/partition-oriented constraint exclusion for faster queries | ✅ | ✅ | ✅ |
-| Skip scans, ordered appends, custom optimizations for faster LIMIT and DISTINCT queries | ✅ | ✅ | ✅ |
-| Columnar storage for accelerated scans | ✅ | ✅ | ✅ |
-| Vectorized query execution (SIMD) | ✅ | ✅ | ✅ |
-| Specialized vector indexes for AI applications | ✅ | ✅ | ✅ |
-| Source connectors | [{C.PG}](/integrate/connectors/source/sync-from-postgres), [Amazon S3](/integrate/connectors/source/sync-from-s3), [Apache Kafka](/integrate/connectors/source/sync-from-kafka) | [{C.PG}](/integrate/connectors/source/sync-from-postgres), [Apache Kafka](/integrate/connectors/source/sync-from-kafka) | Manual |
-| Destination connectors | [Iceberg on S3 Tables](/integrate/connectors/destination/tigerlake) | ❌ | ❌ |
-| In-{C.CONSOLE_SHORT} CSV, Parquet, and text file imports | ✅ | ❌ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Automatic partitioning via {C.HYPERTABLE}s for efficient indexes and faster ingest | ✅ | ✅ | ✅ | ✅ |
+| {C.CAGG_CAP}s | ✅ | ✅ | ✅ | ✅ |
+| Time/partition-oriented constraint exclusion for faster queries | ✅ | ✅ | ✅ | ✅ |
+| Skip scans, ordered appends, custom optimizations for faster LIMIT and DISTINCT queries | ✅ | ✅ | ✅ | ✅ |
+| Columnar storage for accelerated scans | ✅ | ✅ | ✅ | ✅ |
+| Vectorized query execution (SIMD) | ✅ | ✅ | ✅ | ✅ |
+| Specialized vector indexes for AI applications | ✅ | ✅ | ✅ | ✅ |
+| Source connectors | [{C.PG}](/integrate/connectors/source/sync-from-postgres), [Amazon S3](/integrate/connectors/source/sync-from-s3), [Apache Kafka](/integrate/connectors/source/sync-from-kafka) | [{C.PG}](/integrate/connectors/source/sync-from-postgres), [Apache Kafka](/integrate/connectors/source/sync-from-kafka) | Manual | Manual |
+| Destination connectors | [Iceberg on S3 Tables](/integrate/connectors/destination/tigerlake) | ❌ | ❌ | ❌ |
+| In-{C.CONSOLE_SHORT} CSV, Parquet, and text file imports | ✅ | ❌ | ❌ | ❌ |
@@ -26,14 +26,14 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Flexible analysis with full SQL**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Complete {C.PG} ecosystem (all {C.PG} features, connectors, third-party drivers) | ✅ | ✅ | ✅ |
-| Cross-table JOINs for time-series and events with relational tables | ✅ | ✅ | ✅ |
-| Rich timestamp and timezone support | ✅ | ✅ | ✅ |
-| Flexible time-bucketing for time-oriented analysis | ✅ | ✅ | ✅ |
-| Advanced {C.HYPERFUNC} (interpolation, approximation, visualization) | ✅ | ✅ | ✅ |
-| Geospatial and vector data types | ✅ | ✅ | ✅ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Complete {C.PG} ecosystem (all {C.PG} features, connectors, third-party drivers) | ✅ | ✅ | ✅ | ✅ |
+| Cross-table JOINs for time-series and events with relational tables | ✅ | ✅ | ✅ | ✅ |
+| Rich timestamp and timezone support | ✅ | ✅ | ✅ | ✅ |
+| Flexible time-bucketing for time-oriented analysis | ✅ | ✅ | ✅ | ✅ |
+| Advanced {C.HYPERFUNC} (interpolation, approximation, visualization) | ✅ | ✅ | ✅ | ✅ |
+| Geospatial and vector data types | ✅ | ✅ | ✅ | ✅ |
@@ -42,15 +42,15 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Automated data management**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| {C.COLUMNSTORE_CAP} compression (up to 98% storage savings) | ✅ | ✅ | ✅ |
-| Data retention policies | ✅ | ✅ | ✅ |
-| Data tiering with automated policies | ✅ | ✅ | ❌ |
-| Data reordering for efficient disk scans | ✅ | ✅ | ✅ |
-| Data downsampling for efficient historical analysis | ✅ | ✅ | ✅ |
-| Background {C.JOB} scheduler and user-defined {C.JOB}s | ✅ | ✅ | ✅ |
-| Automated {C.CHUNK} interval tuning | ✅ | ✅ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| {C.COLUMNSTORE_CAP} compression (up to 98% storage savings) | ✅ | ✅ | ✅ | ✅ |
+| Data retention policies | ✅ | ✅ | ✅ | ✅ |
+| Data tiering with automated policies | ✅ | ✅ | ❌ | ❌ |
+| Data reordering for efficient disk scans | ✅ | ✅ | ✅ | ✅ |
+| Data downsampling for efficient historical analysis | ✅ | ✅ | ✅ | ✅ |
+| Background {C.JOB} scheduler and user-defined {C.JOB}s | ✅ | ✅ | ✅ | ✅ |
+| Automated {C.CHUNK} interval tuning | ✅ | ✅ | ❌ | ❌ |
@@ -59,19 +59,20 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Enterprise scalability**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Disaggregated compute and storage | ✅ | ✅ | Manual |
-| Dynamic compute resizing | ✅ | ✅ | ❌ |
-| Dynamic disk storage with usage-based pricing | ✅ | ✅ | ❌ |
-| Dynamic I/O provisioning for high-read/high-write performance | ✅ | ✅ | Manual |
-| Low-cost storage with infinite capacity | ✅ | ✅ | ❌ |
-| Transparent queries across high-performance and low-cost tiers | ✅ | ✅ | ❌ |
-| {C.READ_REPLICA_CAP}s with load balancing for seamless read scaling | ✅ | ✅ | Manual |
-| Connection pooling for connection scaling | ✅ | ✅ | Manual |
-| Automated resource-aware parameter tuning | ✅ | ✅ | ❌ |
-| Terraform for infrastructure-as-code control | ✅ | ✅ | ❌ |
-| Management interfaces ([{C.CONSOLE_SHORT}](/deploy/tiger-cloud/tiger-cloud-aws/service-management/service-overview), [REST API](/reference/tiger-cloud-rest), [{C.CLI_SHORT}](/reference/tiger-cloud/tiger-cli), [{C.MCP_SHORT}](/get-started/quickstart/mcp-cli)) | ✅ | ✅ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Disaggregated compute and storage | ✅ | ✅ | Manual | ❌ |
+| Dynamic compute resizing | ✅ | ✅ | ❌ | ❌ |
+| Dynamic disk storage with usage-based pricing | ✅ | ✅ | ❌ | ❌ |
+| Dynamic I/O provisioning for high-read/high-write performance | ✅ | ✅ | Manual | ❌ |
+| Low-cost storage with infinite capacity | ✅ | ✅ | ❌ | ❌ |
+| Transparent queries across high-performance and low-cost tiers | ✅ | ✅ | ❌ | ❌ |
+| {C.READ_REPLICA_CAP}s with load balancing for seamless read scaling | ✅ | ✅ | Manual | ✅ |
+| Connection pooling for connection scaling | ✅ | ✅ | Manual | ✅ |
+| Automated resource-aware parameter tuning | ✅ | ✅ | ❌ | ✅ |
+| Terraform for infrastructure-as-code control | ✅ | ✅ | ❌ | ❌ |
+| Optional replication to {C.CLOUD_LONG} for cross-site or cloud analytics (Cloud Sync) | ❌ | ❌ | ❌ | ✅ |
+| Management interfaces ([{C.CONSOLE_SHORT}](/deploy/tiger-cloud/tiger-cloud-aws/service-management/service-overview), [REST API](/reference/tiger-cloud-rest), [{C.CLI_SHORT}](/reference/tiger-cloud/tiger-cli), [{C.MCP_SHORT}](/get-started/quickstart/mcp-cli)) | ✅ | ✅ | ❌ | Console |
@@ -80,17 +81,17 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**High availability and reliability**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Multi-AZ deployments for high availability | ✅ | ✅ | Manual |
-| Continuous incremental backup and automated restore | ✅ | ✅ | Manual |
-| Cross-region backup and restore | ✅ | ✅ | ❌ |
-| Point-in-time recovery and forking | ✅ | ✅ | Manual |
-| Regular database and disk snapshots for fast restore | ✅ | ✅ | ❌ |
-| Rapid recovery (fast database restart, remote disk remount) | ✅ | ✅ | ❌ |
-| Memory guard protections to avoid out-of-memory crashes | ✅ | ✅ | ❌ |
-| Decoupled control/data planes for greater resilience | ✅ | ✅ | ❌ |
-| Commercial SLAs | ✅ | ✅ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Multi-node high availability with automatic failover | ✅ | ✅ | Manual | ✅ |
+| Continuous incremental backup and automated restore | ✅ | ✅ | Manual | ✅ |
+| Cross-region backup and restore | ✅ | ✅ | ❌ | ❌ |
+| Point-in-time recovery | ✅ | ✅ | Manual | ✅ |
+| Regular database and disk snapshots for fast restore | ✅ | ✅ | ❌ | ❌ |
+| Rapid recovery (fast database restart, remote disk remount) | ✅ | ✅ | ❌ | ❌ |
+| Memory guard protections to avoid out-of-memory crashes | ✅ | ✅ | ❌ | ❌ |
+| Decoupled control/data planes for greater resilience | ✅ | ✅ | ❌ | ✅ |
+| Commercial SLAs | ✅ | ✅ | ❌ | ✅ |
@@ -99,13 +100,13 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Automated upgrades and software patching**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Automated upgrades during maintenance windows | ✅ | ✅ | ❌ |
-| Phased, zero-downtime {C.TIMESCALE_DB} and {C.PG} minor upgrades | ✅ | ✅ | ❌ |
-| {C.PG} major version upgrades with forking workflow and disk snapshots | ✅ | ✅ | ❌ |
-| HA-replica-aware coordinated upgrades | ✅ | ✅ | ❌ |
-| Fleet-wide version and stability monitoring with staged roll-out/roll-back | ✅ | ✅ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Automated upgrades during maintenance windows | ✅ | ✅ | ❌ | ✅ |
+| Phased, low-downtime {C.TIMESCALE_DB} and {C.PG} minor upgrades | ✅ | ✅ | ❌ | ✅ |
+| {C.PG} major version upgrades | ✅ | ✅ | ❌ | ❌ |
+| HA-replica-aware coordinated upgrades | ✅ | ✅ | ❌ | ✅ |
+| Fleet-wide version and stability monitoring with staged roll-out/roll-back | ✅ | ✅ | ❌ | ❌ |
@@ -114,20 +115,20 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Security and compliance**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| SOC 2 Type 2, GDPR, HIPAA certified compliance | ✅ | ✅ | ❌ |
-| Data encryption at rest (disk and backup) | ✅ | ✅ | Manual |
-| Data encryption in transit | ✅ | ✅ | Manual |
-| Database SSL with fully verifiable certificate chains | ✅ | ✅ | ❌ |
-| Control plane role-based access control | ✅ | ✅ | ❌ |
-| Database role-based access control | ✅ | ✅ | ✅ |
-| Multi-factor authentication | ✅ | ✅ | ❌ |
-| Corporate SSO and SAML | ✅ | ✅ | ❌ |
-| IP allow lists | ✅ | ✅ | Manual |
-| Private connectivity to your cloud network | [AWS PrivateLink](/deploy/tiger-cloud/tiger-cloud-aws/security/aws-privatelink), [Transit Gateway](/deploy/tiger-cloud/tiger-cloud-aws/security/transit-gateway), [{C.VPC} peering](/deploy/tiger-cloud/tiger-cloud-aws/security/vpc) | [Azure Private Link](/deploy/tiger-cloud/tiger-cloud-azure/security/azure-privatelink) | ❌ |
-| Layered database privilege escalation protections | ✅ | ✅ | ❌ |
-| Secure SDLC, vulnerability scanning, third-party pen testing | ✅ | ✅ | ❌ |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| SOC 2 Type 2, GDPR, HIPAA certified compliance | ✅ | ✅ | ❌ | ❌ |
+| Data encryption at rest (disk and backup) | ✅ | ✅ | Manual | Manual |
+| Data encryption in transit | ✅ | ✅ | Manual | ✅ |
+| Database SSL with fully verifiable certificate chains | ✅ | ✅ | ❌ | ✅ |
+| Control plane role-based access control | ✅ | ✅ | ❌ | ❌ |
+| Database role-based access control | ✅ | ✅ | ✅ | ✅ |
+| Multi-factor authentication | ✅ | ✅ | ❌ | ❌ |
+| Corporate SSO and SAML | ✅ | ✅ | ❌ | ❌ |
+| IP allow lists | ✅ | ✅ | Manual | Manual |
+| Private connectivity to your cloud network | [AWS PrivateLink](/deploy/tiger-cloud/tiger-cloud-aws/security/aws-privatelink), [Transit Gateway](/deploy/tiger-cloud/tiger-cloud-aws/security/transit-gateway), [{C.VPC} peering](/deploy/tiger-cloud/tiger-cloud-aws/security/vpc) | [Azure Private Link](/deploy/tiger-cloud/tiger-cloud-azure/security/azure-privatelink) | ❌ | ✅ |
+| Layered database privilege escalation protections | ✅ | ✅ | ❌ | ❌ |
+| Secure SDLC, vulnerability scanning, third-party pen testing | ✅ | ✅ | ❌ | ✅ |
@@ -136,14 +137,14 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Deep observability**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| Operational database visibility (performance, regressions, optimization) | ✅ | ✅ | ❌ |
-| Automated query analysis and statistics | ✅ | ✅ | ❌ |
-| Per-query drill-downs (execution times, row results, plans, memory, cache) | ✅ | ✅ | ❌ |
-| In-{C.CONSOLE_SHORT} metric visualization and system logs | ✅ | ✅ | ❌ |
-| Metric exporters | [CloudWatch](/integrate/observability-alerting/cloudwatch), [Prometheus](/integrate/observability-alerting/prometheus), [Datadog](/integrate/observability-alerting/datadog) | [Azure Monitor](/integrate/observability-alerting/azure-monitor), [Prometheus](/integrate/observability-alerting/prometheus), [Datadog](/integrate/observability-alerting/datadog) | ❌ |
-| Connection monitoring and management | ✅ | ✅ | Manual |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| Operational database visibility (performance, regressions, optimization) | ✅ | ✅ | ❌ | ✅ |
+| Automated query analysis and statistics | ✅ | ✅ | ❌ | ❌ |
+| Per-query drill-downs (execution times, row results, plans, memory, cache) | ✅ | ✅ | ❌ | ❌ |
+| In-{C.CONSOLE_SHORT} metric visualization and system logs | ✅ | ✅ | ❌ | ✅ |
+| Metric exporters | [CloudWatch](/integrate/observability-alerting/cloudwatch), [Prometheus](/integrate/observability-alerting/prometheus), [Datadog](/integrate/observability-alerting/datadog) | [Azure Monitor](/integrate/observability-alerting/azure-monitor), [Prometheus](/integrate/observability-alerting/prometheus), [Datadog](/integrate/observability-alerting/datadog) | ❌ | Prometheus |
+| Connection monitoring and management | ✅ | ✅ | Manual | ✅ |
@@ -152,13 +153,13 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
**Production-grade support and operations**
-| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} |
-|---------|:------------------:|:--------------------:|:------------------------:|
-| 24/7 follow-the-sun support (APAC, EMEA, Americas) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) |
-| Production support (severity 1) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) |
-| Architectural reviews, data modeling, query optimization, migration support | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) |
-| 24/7 operational monitoring and control | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) |
-| 98%+ customer satisfaction (CSAT scores) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) |
+| Feature | {C.CLOUD_LONG} on AWS | {C.CLOUD_LONG} on Azure | {C.SELF_LONG_CAP} | {C.TIMESCALE_DB} Enterprise |
+|---------|:------------------:|:--------------------:|:------------------------:|:------------------------:|
+| 24/7 follow-the-sun support (APAC, EMEA, Americas) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) | ✅ |
+| Production support (severity 1) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) | ✅ |
+| Architectural reviews, data modeling, query optimization, migration support | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) | ✅ |
+| 24/7 operational monitoring and control | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) | ❌ |
+| 98%+ customer satisfaction (CSAT scores) | ✅ | ✅ | [Contact sales](mailto:sales@tigerdata.com) | ✅ |
@@ -168,4 +169,5 @@ This page compares the features available in **{C.CLOUD_LONG} on AWS**, **{C.CLO
- **{C.CLOUD_LONG} on AWS**: Full feature set, including AWS-specific integrations. Private connectivity through AWS PrivateLink, Transit Gateway, and {C.VPC} peering, cross-region backup and restore, an Amazon S3 source connector, an Iceberg destination connector for S3 Tables, and metric export to CloudWatch (as well as Prometheus and Datadog).
- **{C.CLOUD_LONG} on Azure**: The same core database and management platform. Private connectivity through Azure Private Link, cross-region backup and restore, and metric export to Azure Monitor (as well as Prometheus and Datadog). Some AWS-specific integrations, such as the S3 and Iceberg connectors, {C.VPC} peering, and CloudWatch, are not yet available.
- **{C.SELF_LONG_CAP}**: Full SQL and time-series capabilities. You manage backups, high availability, scaling, and observability yourself. Managed operations and enterprise support are available by [contacting sales](mailto:sales@tigerdata.com).
+- **{C.TIMESCALE_DB} Enterprise**: Self-managed, commercially licensed {C.TIMESCALE_DB} for on-premises, edge, and air-gapped infrastructure, with high availability, automated backups, low-downtime upgrades, monitoring, and commercial support driven from a console you run yourself. See [Meet {C.TIMESCALE_DB} Enterprise](/learn/enterprise).
\ No newline at end of file
diff --git a/src/styles/page-splash.css b/src/styles/page-splash.css
index 5122b438..ec6feccb 100644
--- a/src/styles/page-splash.css
+++ b/src/styles/page-splash.css
@@ -26,6 +26,14 @@
opacity: 0.1;
}
+:root[data-theme="dark"] .splash-hero-card--enterprise .splash-hero-card__bg {
+ background-color: #12261c;
+}
+
+:root[data-theme="dark"] .splash-hero-card--enterprise .splash-hero-card__bg::after {
+ opacity: 0.1;
+}
+
:root[data-theme="dark"] .splash-hero-card__title {
color: var(--stl-color-foreground);
}
@@ -288,20 +296,18 @@
.splash-hero-cards {
margin-top: 16px;
display: grid;
- grid-template-columns: var(--tiger-hero-col-width) var(--tiger-hero-col-width);
+ grid-template-columns: repeat(3, 1fr);
gap: var(--tiger-hero-gap);
}
@media (max-width: 1350px) {
.splash-hero-cards {
- grid-template-columns: 1fr 1fr;
+ grid-template-columns: 1fr;
}
}
-@media (max-width: 768px) {
- .splash-hero-cards {
- grid-template-columns: 1fr;
- }
+.splash-hero-cta {
+ margin-top: 60px;
}
.splash-hero-card {
@@ -400,6 +406,23 @@
background-position: top left;
}
+/* Enterprise card background (placeholder tint until illustration artwork exists) */
+.splash-hero-card--enterprise .splash-hero-card__bg {
+ background-color: #eafcf1;
+}
+
+.splash-hero-card--enterprise .splash-hero-card__bg::after {
+ content: "";
+ position: absolute;
+ inset: 0;
+ border-radius: 16px;
+ pointer-events: none;
+ opacity: 0.18;
+ background-image: url("data:image/svg+xml,%3Csvg viewBox='0 0 256 256' xmlns='http://www.w3.org/2000/svg'%3E%3Cfilter id='n'%3E%3CfeTurbulence type='fractalNoise' baseFrequency='0.9' numOctaves='4' stitchTiles='stitch'/%3E%3C/filter%3E%3Crect width='100%25' height='100%25' filter='url(%23n)'/%3E%3C/svg%3E");
+ background-size: 1024px 1024px;
+ background-position: top left;
+}
+
.splash-hero-card__content {
position: relative;
display: flex;