Developer portal
for Vibecoders.

Coding agents ship fast. Someone needs to watch what they deployed, where it runs, and what it costs.

Relight Portal is a centralized gateway that gives DevOps and admins visibility over AI-generated workloads.

$ docker run -p 3000:3000 getrelight/portal Copied!
Relight Portal
Relight
Dashboard
Apps
Costs
Providers
Team
Apps
12
Databases
4
Providers
3
This cycle
$18.40
Recent deployments
pto-bot v0.4.2 GCP live
invoice-scanner v1.1.0 AWS live
meeting-recap v0.2.5 Azure sleeping
expense-tldr v0.1.8 GCP live

Features

No cloud credentials on dev machines

Cloud access lives on the portal, not on team members' laptops. Developers and coding agents deploy using scoped API tokens. They never see AWS keys, GCP service accounts, or Azure credentials.

Centralized gateway for Relight CLI

The CLI connects to the portal with one command. After that, every deploy routes through it - image push, registry auth, cloud deployment. One place to look instead of three cloud consoles.

Cost visibility across providers

Syncs billing data from GCP, AWS, Azure, Cloudflare, and DigitalOcean every hour. Breaks down costs by service and resource. Set daily or monthly budget alerts per cloud connection.

Fully self-hosted

Single Docker container on your infrastructure. No telemetry, no SaaS dependency, no data leaving your network. Talks only to your cloud providers. SQLite by default, Postgres or MySQL if you need it.

Cloud-native identity

Supports Azure Managed Identity, GCP Workload Identity, and AWS IAM roles. No secrets to rotate - the portal authenticates through the platform.

Team access with SSO

OIDC login with Entra ID, Google, Okta, or any compliant provider. Scoped API tokens with IP allowlists for CI/CD. Multi-tenant isolation when you need it.

Connect CLI to the Portal

Without the portal, the CLI talks to cloud providers directly using credentials on your machine. With the portal, you point the CLI at it once and everything routes through.

# Connect once
$ relight portals add https://portal.internal
Token: rl_abc...
--> Connected to portal at portal.internal
# Deploy as usual - the CLI routes through the portal
$ relight deploy myapp .
Building image...
Pushing to portal.internal/myapp:v1...
Portal deploying to Cloud Run (us-east1)...
--> Live at https://myapp-abc123.run.app

The developer builds locally, pushes to the portal's Docker registry, and the portal handles the rest - authenticating with the cloud, pushing layers to the real registry, and triggering the deployment. Same relight deploy command, no cloud credentials needed.