Company / About

An open cloud built for accountability

LayerRail exists because launching infrastructure got easy, but explaining it never did.

Why we build LayerRail.

Modern teams can launch cloud resources in seconds. But the story around those resources falls apart just as fast: ownership drifts, costs surprise, and when finance or an operations team asks what ran where and why, the answer becomes spreadsheet archaeology.

LayerRail keeps infrastructure explainable after deployment. Virtual machines, private networking, managed PostgreSQL and Kubernetes, GitHub runners, storage, and AI inference run from one project-centered console — with usage and pricing records kept beside the resources they describe.

The console is open source, so teams can inspect the rules that govern their infrastructure and keep a practical exit path.

Resources and receipts together

Who created a resource, where it runs, what it costs, which project owns it — the answers live next to the resources themselves, not scattered across billing portals and dashboards.

Open by default

The LayerRail console and control plane are open source under AGPL-3.0, built on the Ubicloud foundation. You can audit them, self-host them, and keep a real exit path.

Budgets on rails

Per-minute billing capped at 672 hours per monthly invoice window, project budget controls, and usage records keep cost reviews explainable.

Evidence, not archaeology

Keep infrastructure context together. Deployment passports and reporting-ready exports are on the roadmap; current resource and usage records remain visible in the console.

5
Regions: East US, East US 2, Central US, UK South, South Africa North
AGPL-3.0
Open source console and control plane
Per minute
Billing for duration-based cloud resources
Metered
Paid AI inference with separate usage invoices

Build your next layer.

Run compute, networking, and managed services from one project-centered console.

Start building ↗