Provisioning
How database provisioning works on Zektor.io — from deployment to ready in under 60 seconds.
How Provisioning Works
When you create a new instance on Zektor.io, the following happens automatically:
- Resource Allocation — Dedicated RAM, CPU, and SSD storage are reserved for your instance
- Container Deployment — Your database engine is deployed in an isolated container
- Network Setup — Secure networking with TLS termination is configured
- Health Checks — The system verifies the instance is healthy and accepting connections
- Credentials Generation — Connection credentials are generated and made available in your dashboard
This entire process typically completes in under 60 seconds.
Regions
All infrastructure is hosted in EU data centers:
| Region | Location | Provider |
|---|---|---|
nbg1 | Nuremberg, Germany | Hetzner |
fsn1 | Falkenstein, Germany | Hetzner |
hel1 | Helsinki, Finland | Hetzner |
Choosing a Region
- Nuremberg and Falkenstein — Best for applications hosted in Central Europe
- Helsinki — Best for applications hosted in Northern/Eastern Europe
- Latency — Choose the region closest to your application servers for the lowest latency
Note: Data never leaves the EU regardless of which region you choose.
Instance States
| Status | Description |
|---|---|
| Provisioning | Instance is being created (typically < 60 seconds) |
| Active | Instance is running and accepting connections |
| Stopped | Instance is stopped (no billing during this state) |
| Deleting | Instance is being removed |
Cluster Sizes
Each database engine offers multiple cluster sizes (tiers). You can upgrade your cluster size at any time from the instance Settings page.
See Pricing for a full list of available tiers and their specifications.
Scaling
Currently, scaling is done by upgrading your cluster size (vertical scaling). The upgrade process will:
- Provision a new instance with the larger size
- Migrate your data to the new instance
- Update DNS to point to the new instance
- Remove the old instance
Downtime during scaling is minimal (typically a few seconds). See Scaling for detailed information about the resize process and what to expect.
Next Steps
- Getting Started — Deploy your first instance
- Connecting — Connect to your instance
- Pricing — Understand costs per tier
- Scaling — Resize your instance