VPCs
Virtual Private Clouds provide isolated network environments for your resources.
A VPC (Virtual Private Cloud) is an isolated network environment where your infrastructure runs. Every resource you create — databases, services, storage buckets, secrets — belongs to a VPC.
Creating a VPC
Create a VPC from your workspace dashboard:
- Click Create VPC
- Enter a name
- Select a region
Available regions:
eu-central-1(default)eu-central-2eu-west-1
What's included
When you create a VPC, SMLL automatically provisions:
- Kubernetes namespace — isolated compute environment
- Private container registry — a Harbor project for your Docker images
- S3 credentials — access keys for object storage
- Resource quotas — CPU, memory, and storage limits based on your billing tier
- Default alert rules — 7 pre-configured alerts for common issues (OOM kills, high CPU, disk usage, etc.)
Resource isolation
Resources in one VPC cannot access resources in another VPC. This gives you strong isolation between environments — for example, you might use separate VPCs for staging and production.
Within a VPC, services can reach databases and other services using internal networking. Database connection strings are automatically injected as secrets.
Resource quotas
Each VPC has resource limits that depend on your billing tier:
| Resource | Free tier | Pay-as-you-go |
|---|---|---|
| CPU requests | 2 cores | 8 cores |
| CPU limits | 4 cores | 16 cores |
| Memory requests | 4 GiB | 16 GiB |
| Memory limits | 8 GiB | 32 GiB |
| Pods | 20 | 100 |
| Persistent volumes | 10 | 50 |
| Total storage | 50 GiB | 500 GiB |
Need higher limits? See Quotas.
Deleting a VPC
VPCs can only be deleted when they contain no resources (databases, services, buckets). Delete all resources first, then delete the VPC from the workspace dashboard.
Related
- Networking — how services and databases communicate within a VPC
- Resource Quotas — adjusting VPC resource limits
- Getting Started — create your first VPC