STACKIT PostgreSQL Flex

STACKIT PostgreSQL Flex provides fully managed open-source PostgreSQL instances with automated backups, extensions, and high availability across availability zones.

Service Overview

• Enterprise-Ready SQL: High availability across 3 Availability Zones with automated failover handling.
• Compliance & Security: GDPR-compliant and BSI C5 certified operation with AES-256 at-rest encryption.
• DevOps Friendly: Complete Infrastructure as Code support via official Terraform and Pulumi providers.

Technical Details

• Options: Single Instance and 3-Node Replica Sets across multiple Availability Zones.
• Tooling Support: Compatible with standard DBA tools like pgAdmin, DBeaver, and psql CLI.
• Recovery Features: Automated backups with Point-In-Time Recovery (PITR) and instance cloning capabilities.

Flavors and Performance Classes

The values below come from the STACKIT documentation and update themselves.

From the STACKIT docsFlavors and performance classes › FlavorsSource updated 06.07.2026 · copied 05.10.2026

Swipe sideways to see the whole table

Description	ID	CPU	RAM	max_connections	shared_buffers	work_mem	maintenance_work_mem	effective_cache_size
Small, Compute optimized	2.4	2	4 GB	95	950 MB	14 MB	380 MB	2660 MB
Small, Memory optimized	2.16	2	16 GB	385	3950 MB	14 MB	1580 MB	11060 MB
Medium, Compute optimized	4.8	4	8 GB	195	1950 MB	14 MB	780 MB	5460 MB
Medium, Memory optimized	4.32	4	32 GB	785	7950 MB	14 MB	3180 MB	22260 MB
Large, Processor optimized	8.16	8	16 GB	385	3950 MB	14 MB	1580 MB	11060 MB
X-Large, Compute optimized	16.32	16	32 GB	785	7950 MB	14 MB	3180 MB	22260 MB
X-Large, Memory optimized	16.128	16	128 GB	3170	31950 MB	14 MB	12780 MB	89460 MB

Notes

• CPU and RAM is always per node.
• The system uses up to 15 connections for internal essential processes such as backup, monitoring, etc. These connections will be counted towards the max_connections limit.

What is this?

This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.

From the STACKIT docsFlavors and performance classes › Performance ClassesSource updated 06.07.2026 · copied 05.10.2026

Swipe sideways to see the whole table

Description	ID	Max. IOPS	Max. throughput (MB/s)
Performance class 2	premium-perf2-stackit	1000	100
Performance class 4	premium-perf4-stackit	2000	150
Performance class 6	premium-perf6-stackit	5000	200
Performance class 8	premium-perf8-stackit	10000	250
Performance class 10	premium-perf10-stackit	15000	300
Performance class 12	premium-perf12-stackit	20000	350

Currently, we offer three types of instances. For each type there is a different set of flavors available.

What is this?

This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.

From the STACKIT docsArchitecture › BackupSource updated 19.03.2026 · copied 05.10.2026

You manage backups at the instance level, which includes all users and databases. Because the transaction logs are activated by default, you can use them to achieve point-in-time recovery across all available snapshots.

With instance cloning, you can replicate your existing PostgreSQL Flex instance to another instance within the same project for testing, staging, or data recovery workflows. Recovery to the existing instance is not possible yet.

What is this?

This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.

Limitations & Constraints

• Immutable Storage IOPS: Storage performance profiles cannot be modified after creation; disk size can only grow.
• No Logical Replication: Logical publishing and subscribing modes are currently unsupported.
• No Custom S3 Backups: Backups are managed internally by STACKIT and cannot be exported directly to custom S3 buckets.

STACKIT documentation docs.stackit.cloud STACKIT PostgreSQL Flex Documentation Open the documentation