Skip to main content
LayerRail gives startups, developers, and teams a clear way to run cloud infrastructure without hiding every operational detail behind a black box. The console is organized around projects. A project contains the infrastructure for one product, customer environment, team, or workload.

Services

Virtual machines

General purpose compute for apps, services, workers, and custom infrastructure.

Managed PostgreSQL

PostgreSQL instances with connection details, networking controls, and operational visibility.

Managed Kubernetes

Kubernetes clusters for container workloads and team deployment flows.

Networking

Private subnets, firewalls, public IPs, service hostnames, and load balancers.

GitHub runners

On-demand runner infrastructure for GitHub Actions workflows.

AI inference

Project-scoped model endpoints, API keys, and a playground for testing prompts.

Console model

LayerRail uses a few core objects across the platform:
ObjectPurpose
AccountYour identity and login methods.
ProjectA boundary for resources, billing, access, and audit logs.
LocationThe region where infrastructure is provisioned.
ResourceA VM, database, cluster, subnet, firewall, load balancer, or runner.
API tokenA personal access token used to call the LayerRail API.

Where to start

1

Create or open a project

Sign in to the LayerRail console and open the project where you want to work.
2

Choose a first service

Start with Virtual machines if you need direct compute, Managed PostgreSQL if you need a database, or Kubernetes if you are deploying containers.
3

Add networking

Use private subnets, firewalls, and load balancers when the service needs controlled access or a public endpoint.
4

Automate later

When the workflow is stable, create a personal access token and move repeated actions into scripts or CI.
LayerRail currently focuses on practical cloud primitives: compute, PostgreSQL, Kubernetes, networking, runners, and inference. App deployment documentation will be added as that product surface is finalized.