Why Dedicated Infrastructure

Most cloud providers run managed services on shared pools. Multi-tenant clusters where your database shares resources with hundreds of other customers. It's cheaper to operate. But it comes with real problems:

  • Noisy neighbors. Someone else's query spike affects your latency.
  • Unpredictable jitter. Performance varies based on cluster load, not your workload.
  • Security blast radius. A vulnerability in one tenant's config can expose the whole pool.
  • No customization. You can't tune settings because you don't own the instance.

We took a different approach. Same managed experience, but on dedicated infrastructure. Your database runs on its own VM, with its own storage, in your own VPC. You get full isolation, predictable performance, and the ability to customize configs when you need to.

It's managed services done right.

How Our Managed Services Work

These invariants apply to every managed service. PostgreSQL, MySQL, Redis. Same model.

Dedicated VM Per Service

Your database isn't a shared tenant. It's a real VM running in your account, with the compute class you choose.

Lives in Your VPC

Same private network, same firewall rules, same visibility. No special tunnels or hidden endpoints.

Same Storage Classes

Value, Standard, Premium. Same IOPS guarantees as regular volumes. You pick the performance tier.

Same Network Classes

Baseline, Standard, Edge. Same bandwidth limits and traffic packages as your VMs.

Same Limits and Guarantees

No magic. Same performance model, same pricing primitives. Predictable behavior across all services.

One Managed Model. Multiple Services.

All managed services share the same architecture. Different software on top.

Same VM lifecycle
Same storage engine
Same network isolation
Same monitoring & backups
Same CLI & API

Which Service For You?

Quick guide based on your use case

Redis

In-memory cache. Sub-millisecond latency.

Best for: Sessions, cache, queues
  • Session storage
  • Rate limiting
  • Real-time leaderboards
from ~€5 /mo

MySQL

Classic RDBMS. WordPress, legacy apps.

Best for: CMS, legacy, PHP apps
  • WordPress / Drupal
  • Laravel / Symfony
  • Existing MySQL schemas
from ~€10 /mo

MongoDB

Document store. Flexible schema, JSON-native.

Best for: Node.js, flexible data
  • Rapid prototyping
  • Event logging
  • Product catalogs
from ~€10 /mo

Not sure? PostgreSQL is the safe default — it handles 90% of use cases. Add Redis when you need caching.

All managed services run on dedicated VMs in your VPC. See full pricing →

Recommended Configurations

Typical setups for different environments

Dev / Test

VMburst-m
Storageessential 50GB
Networkbaseline
~€10-15/mo

Affordable, can burst when needed. Good for CI/CD, staging, local dev.

High Performance

VMmemory-l
Storagepremium 500GB
Networkstandard
~€150-200/mo

Max memory for large datasets. 50K IOPS for analytics/OLTP.

Available Services

Databases

  • PostgreSQL Most Popular Available
  • MySQL Available
  • MongoDB Available
  • Redis Available
  • Elasticsearch Available

Messaging & Storage

  • S3 Storage Available
  • NATS Available
  • Docker Registry Available

Security & Access

  • Vault Available
  • VPN Gateway Available
  • Containers Available

We Handle vs You Control

Clear division of responsibility. You own the infrastructure, we handle the ops.

We Handle

  • Automated backups
  • Automatic failover
  • Security updates
  • Monitoring & alerting
  • Minor version upgrades

You Control

  • VM class & size
  • Storage class & size
  • Network class
  • Access & firewall rules
  • Major version upgrades

What This Is NOT

Not a shared PaaS

Your database runs on a dedicated VM. Not a multi-tenant cluster with noisy neighbors.

Not serverless

You choose the resources. You see the VM. You SSH in when needed.

Not opaque pricing

VM cost + storage cost + management fee. Same primitives, same rates, clear math.

Not vendor-locked

Standard PostgreSQL, standard MySQL, standard Redis. No proprietary extensions.

CLI-First

Managed services are part of the same platform. Same CLI, same API.

$ scamp managed create postgres \
    --name prod-db \
    --version 16 \
    --vm-class dedicated-m \
    --storage-class standard \
    --storage-size 100 \
    --network-class standard \
    --vpc prod-vpc

Creating managed PostgreSQL 'prod-db'...
VM:      dedicated-m (2 vCPU, 4 GB RAM)
Storage: 100 GB standard (10,000 IOPS)
Network: standard (1 Gbit, 20 TB included)
VPC:     prod-vpc
Status:  provisioning

$ scamp managed list

NAME      TYPE       VERSION  STATUS   VM CLASS     IP
prod-db   postgres   16       running  dedicated-m  10.0.1.50
cache     redis      7.2      running  burst-s      10.0.1.51

$ scamp managed connect prod-db
psql (16.1)
Type "help" for help.
prod-db=#

Ready to deploy?

Launch a managed service in minutes. Full control, zero ops.

Join Early Access

No credit card. No sales calls. Cancel anytime.