Your teams ship apps with AI faster than anyone can track by hand. Someone still has to know what got deployed, where it runs, and what it costs.
Relight Portal is where they look: one dashboard for every deployment across your clouds - and the place cloud credentials live instead of laptops.
| 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 |
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.
The CLI connects to the portal with one command. After that, every deploy runs through it - image push, registry auth, cloud deployment. One place to look instead of three cloud consoles.
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.
Single Docker container on your infrastructure. It sends no telemetry and talks only to your cloud providers, so nothing leaves your network. Uses Postgres for storage.
Supports Azure Managed Identity, GCP Workload Identity, and AWS IAM roles. No secrets to rotate - the portal authenticates through the platform.
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.
Point the CLI at the portal once. From then on every deploy runs through it, and the cloud credentials stay on the portal instead of on the machine.
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.