Isolated OCI containers with persistent storage

Web APIs & Webhooks

Receive inbound HTTP traffic and webhooks from Stripe, Telegram, or GitHub. The HTTPS gateway terminates TLS automatically and routes traffic to your container port.

• Automatic TLS & Subdomain

  Every container can receive a permanent <id>.msrv.space domain with automated certificate management.

• Outbound Access via NAT

  Inbound ports remain private while containers reach external APIs and registries via eBPF Outbound NAT.

• Security & Isolation

  Containers run in secure, isolated sandboxes separate from the host system.

Telegram Bots & Stateful Services

Run bots via webhooks or long polling. Data, local caches, and embedded databases persist on durable NVMe storage.

• Persistent Storage

  User sessions, caches, and local databases (like SQLite) persist on replicated NVMe storage.

• Shared Private VPC

  Reach PostgreSQL and other services directly over your private VPC subnet without public routing.

• Fast Restarts

  Data and local state remain intact across container restarts and updates.

Background Tasks & Media Processing

Batch image processing, report generation, web scrapers, and file conversion pipelines. Use standard images containing ffmpeg, imagemagick, or Python workers.

• Standard OCI Images

  Pull pre-built images from Docker Hub and GitHub Packages or use your own custom registries.

• Dedicated Resources

  Allocate dedicated vCPUs and memory for intensive transcoding and data processing workloads.

• Simple Management

  Create, inspect, configure, and manage containers via the web console or REST API.

> capabilities

Container Capabilities

The simplicity of standard OCI containers with persistent storage and private networking.

• Docker Hub & GHCR

  Import any standard OCI image from public or private container registries.

• Persistent Storage

  Persist filesystem modifications on durable, replicated NVMe block storage.

• HTTPS Gateway

  Built-in TLS endpoint at <id>.msrv.space without configuring reverse proxies.

• Private VPC Network

  Internal IP addresses and direct routing to PostgreSQL and virtual machines.

• Secure Isolation

  Strong workload isolation protecting your container environments.

• Databases in Same VPC

  Connect directly to PostgreSQL and other databases within your private network without public exposure.

  Databases →