AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Open, free, and portable cloud. Elastic compute, block storage (non replicated), virtual networking, managed Postgres, and IAM services in public beta.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
LayerRail is an open cloud control plane for teams that need infrastructure with
clear ownership, budget rails, and deployment evidence. It brings compute,
networking, managed services, billing context, and operational records into one
project-centered console.檢視完整 README ↗LayerRail is an open source cloud control plane for developers and teams. Manage virtual machines, networking, PostgreSQL, Kubernetes, GitHub runners, and AI inference through a project-centered dashboard and API, with access controls, resource state, and usage close at hand.
This repository contains the API, dashboard, and provisioning workers behind LayerRail. Use the hosted platform to build, or explore the code and run the control plane yourself.
Watch the launch film and open the interactive preview →
An introduction to the API, dashboard, and project workflow. The preview uses an illustrative workspace; it contains no customer data.
| Build with | What you can do |
|---|---|
| Compute | Create Linux virtual machines and inspect their state, sizing, networking, and backups. |
| Networking | Organize private subnets, control traffic with firewalls, and route requests through load balancers. |
| PostgreSQL | Manage databases, backup and restore workflows, configuration, and monitoring. |
| Kubernetes | Manage clusters, node pools, kubeconfigs, resizing, and upgrades. |
| GitHub Actions | Connect repositories to managed runners from the same project. |
| AI inference | Explore models in the playground and call supported chat, Responses, and embedding APIs. |
| Project operations | Manage team access, personal access tokens, audit logs, usage, credits, and invoices. |
Service availability depends on the deployment's enabled features, configured providers, and model catalog. The hosted dashboard shows the options available to your project.
Create a personal access token in your project's dashboard, copy the project ID, and list its virtual machines:
export LR_TOKEN="pat-YOUR_PERSONAL_ACCESS_TOKEN"
export PROJECT_ID="YOUR_PROJECT_ID"
curl --fail-with-body \
"https://api.console.layerrail.com/project/${PROJECT_ID}/vm" \
-H "Authorization: Bearer ${LR_TOKEN}"
Requests respect your account and token permissions. The
OpenAPI specification documents infrastructure endpoints,
request bodies, and pagination. For terminal workflows, see the lr CLI.
Create a separate inference API key in your project, then make a supported Responses request:
export LAYERRAIL_AI_KEY="YOUR_INFERENCE_API_KEY"
curl --fail-with-body https://api.console.layerrail.com/v1/responses \
-H "Authorization: Bearer ${LAYERRAIL_AI_KEY}" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6.1-sol",
"input": "Explain what a cloud control plane does in one paragraph.",
"reasoning": {"effort": "low"},
"max_output_tokens": 1024,
"store": false
}'
AI requests require an available model and verified project billing. Usage is paid; model prices and supported request formats are shown in the catalog. See the GPT-6 API notes and usage billing guide.
With Git, Docker Compose, and a POSIX shell installed:
git clone https://github.com/layerrail/layerrail.git
cd layerrail
./demo/generate_env
docker compose -f demo/docker-compose.yml up --build
Open localhost:3000. The demo starts a PostgreSQL database, applies migrations, and runs the web service and background workers. On Windows, run these commands from WSL or another POSIX shell.
The demo provides a local control plane. Configure provider credentials and service prerequisites before provisioning cloud resources. Follow the getting started guide for account setup, API access, and deployment configuration.
flowchart LR
Developer[Developers and teams] --> Dashboard[Dashboard]
Developer --> API[API and CLI]
Dashboard --> Control[Control plane]
API --> Control
Control <--> State[(PostgreSQL state)]
State <--> Workers[Provisioning and monitoring workers]
Workers --> Providers[Configured providers]
Providers --> Resources[Project infrastructure]
Control --> Inference[AI provider APIs]
The Ruby control plane uses Roda, Sequel, and Rodauth. The dashboard uses server-rendered views with Tailwind CSS and a React-based AI playground. Background workers provision and reconcile infrastructure; PostgreSQL stores control-plane state.
| Explore the source | Start here |
|---|---|
| HTTP routing and API behavior | clover.rb, routes/, openapi/ |
| Dashboard and playground | views/, assets/js/playground/ |
| Domain models and database changes | model/, migrate/ |
| Provisioning and reconciliation | prog/, rhizome/ |
| Command line workflows | cli/, cli-commands/ |
| Verification |
Read CONTRIBUTING.md before opening a pull request, and DEVELOPERS.md for the development environment and test suite. We welcome focused improvements to provider integrations, reliability, documentation, and the developer experience.
LayerRail is built on the Ubicloud open source infrastructure foundation. This product fork retains the upstream AGPL-3.0 license and attribution. Preserve the original notices and meet the license's source-sharing requirements when modifying or operating the software over a network.
spec/