ZEKTOR.IO Docs

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:

  1. Resource Allocation — Dedicated RAM, CPU, and SSD storage are reserved for your instance
  2. Container Deployment — Your database engine is deployed in an isolated container
  3. Network Setup — Secure networking with TLS termination is configured
  4. Health Checks — The system verifies the instance is healthy and accepting connections
  5. 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:

RegionLocationProvider
nbg1Nuremberg, GermanyHetzner
fsn1Falkenstein, GermanyHetzner
hel1Helsinki, FinlandHetzner

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

StatusDescription
ProvisioningInstance is being created (typically < 60 seconds)
ActiveInstance is running and accepting connections
StoppedInstance is stopped (no billing during this state)
DeletingInstance 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:

  1. Provision a new instance with the larger size
  2. Migrate your data to the new instance
  3. Update DNS to point to the new instance
  4. 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

On this page