Core Concepts

Services

A service is a managed database instance. It includes the database engine, storage, compute, TLS certificate, DNS record, and optional replicas — all provisioned and maintained automatically.

Each service has:

• A primary node handling reads and writes
• Optional read replicas for horizontal scaling or HA
• A DNS hostname for connecting (e.g. my-db.db.foundrydb.com)
• Automated backups on a configurable schedule

Plans

Plans define the compute allocation (CPU and memory). Storage is configured separately.

Plan	CPU	Memory
tier-1	1 vCPU	2 GB
tier-2	2 vCPU	4 GB
tier-4	4 vCPU	8 GB
tier-8	8 vCPU	16 GB
tier-16	16 vCPU	32 GB

Storage tiers: standard (HDD) or maxiops (NVMe SSD).

Zones

Services are deployed to a specific cloud zone. Available zones:

• se-sto1 — Stockholm, Sweden

Connection

Every service is accessible via a public DNS hostname over TLS. Example connection strings:

# PostgreSQL
postgresql://user:pass@my-pg.db.foundrydb.com:5432/defaultdb?sslmode=verify-full

# MySQL
mysql://user:pass@my-mysql.db.foundrydb.com:3306/defaultdb

# MongoDB
mongodb://user:pass@my-mongo.db.foundrydb.com:27017/defaultdb?tls=true

# Valkey
rediss://user:pass@my-valkey.db.foundrydb.com:6380

# Kafka bootstrap
my-kafka.db.foundrydb.com:9093

Network Access

By default services reject all connections. Use allowed_cidrs to whitelist your IP ranges:

curl -u admin:password -X PATCH https://api.foundrydb.com/managed-services/{id} \
  -H "Content-Type: application/json" \
  -d '{"allowed_cidrs": ["203.0.113.10/32"]}'

Backups

All services include automated backups. Depending on the engine:

• PostgreSQL — WAL archiving for point-in-time recovery to any second
• MySQL — binlog archiving for PITR
• MongoDB — oplog archiving for PITR
• Valkey — RDB snapshots + AOF
• Kafka — topic data snapshots