Limits & Quotas
Platform limits, resource quotas, and connection limits for Zektor.io managed database instances.
Overview
This page documents the limits and quotas that apply to Zektor.io instances. These limits are designed to ensure reliable performance and fair resource allocation across the platform.
Instance Limits
| Resource | Limit |
|---|---|
| Instances per account | No hard limit |
| Branches per PostgreSQL instance | No hard limit |
| Regions available | 3 (Falkenstein, Nuremberg, Helsinki) |
PostgreSQL Limits
Tiers
| Tier | RAM | vCPU | Included storage | Monthly egress |
|---|---|---|---|---|
| AKPG-5 | 512MB | 0.25 | 5GB | 10GB |
| AKPG-10 | 1GB | 0.5 | 5GB | 100GB |
| AKPG-20 | 2GB | 1 | 5GB | 100GB |
| AKPG-40 | 4GB | 2 | 5GB | 100GB |
| AKPG-80 | 8GB | 4 | 10GB | 200GB |
| AKPG-160 | 16GB | 8 | 20GB | 400GB |
| AKPG-320 | 32GB | 16 | 40GB | 800GB |
All PostgreSQL tiers run on shared vCPU. See Pricing for monthly costs.
Connection limits
max_connections is not configured per tier — every instance uses the PostgreSQL default of 100 connections regardless of size. If you need more concurrent connections than that, use a connection pooler in your application, or contact us.
Storage limits
Each tier includes the storage shown above. Storage beyond the included amount is billed at €0.15/GB per month.
Automatic storage scaling is opt-in per instance and disabled by default. When you enable it, you must also set an auto-scaling limit above your current size — scaling does nothing until you do. Once configured:
| Behaviour | Value |
|---|---|
| Grows when usage exceeds | 80% |
| Shrinks when usage falls below | 60% |
| Step size | 5GB |
| Maximum auto-scaling limit | 1000GB (1TB) |
Shrinking never goes below the instance's configured minimum disk size, and can be disabled independently by setting the instance to scale up only.
Database limits
| Resource | Limit |
|---|---|
| Maximum databases per instance | Unlimited (PostgreSQL default) |
| Maximum table size | Limited by available storage |
| Maximum row size | 1.6TB (PostgreSQL default) |
| Statement timeout | None by default (statement_timeout = 0) |
| PostgreSQL versions | 16, 17, 18 (available on every tier) |
pg_stat_statements is enabled on every instance, with statement tracking set to all and a 5000-statement ceiling.
Valkey Limits
Tiers
| Tier | RAM | vCPU | Monthly egress |
|---|---|---|---|
| AKVK-1 | 128MB | 0.125 | 100GB |
| AKVK-5 | 512MB | 0.5 | 100GB |
| AKVK-10 | 1GB | 1 | 200GB |
| AKVK-20 | 2GB | 2 | 400GB |
| AKVK-40 | 4GB | 4 | 800GB |
| AKVK-80 | 8GB | 8 | 1.6TB |
Connection limits
maxclients is not configured per tier — instances use the Valkey default of 10,000 clients, subject to the container's file-descriptor limit.
Memory and eviction
maxmemory is set to the tier's RAM, with the allkeys-lru eviction policy: once an instance is full, the least recently used keys are evicted to make room for new writes. Persistence uses appendonly yes.
Data limits
| Resource | Limit |
|---|---|
| Maximum key size | 512MB (Valkey default) |
| Maximum value size | 512MB (Valkey default) |
| Maximum number of keys | Limited by available RAM |
| Valkey versions | 8, 9 (available on every tier) |
Backup Limits
| Resource | Limit |
|---|---|
| Backup schedules per instance | No hard limit |
| Manual backups per instance | No hard limit |
| Minimum backup retention | 1 day |
| Maximum backup retention | No hard limit |
| PITR recovery window | From oldest backup to 2 minutes ago |
Network Limits
| Resource | Limit |
|---|---|
| Egress | Monthly allowance per tier (see tables above) |
| TLS version | TLS 1.2+ required |
Egress is monitored against your tier's allowance. Exceeding it does not currently throttle your instance or incur an overage charge, but sustained overages may be reviewed.
Need Higher Limits?
If your use case requires limits beyond what's listed here, contact us. We can accommodate custom configurations for enterprise deployments.