Service Infrastructure

Environments

Isolated sets of services your application depends on. Databases, caches, APIs—all running and accessible.

Compatible With

Docker Compose

If it runs in Docker, it runs here.

# compose.yaml
services:
  api:
    image: my-api:latest
    ports: ["8080:8080"]
  db:
    image: postgres:16
  redis:
    image: redis:alpine

Each environment runs in its own network namespace. No cross-contamination between staging and production.

Connect from any workspace to access services by name. No complex networking setup required.

Fork environments to get your own isolated copy with the same services and data. Perfect for experimentation.

Route service traffic to your workspace for debugging. Test with real requests without deploying.

Use Cases

Shared Staging

Team-wide environment for integration testing

Personal Copies

Clone for isolated feature development

PR Previews

Spin up environments per pull request

Load Testing

Isolated environments for performance tests

Make an environment visible to other developers. They can connect their workspaces and access the same services with the same data.

Fork an environment to get your own copy with the same configuration. Test changes without affecting others.

Learn More