See what happened. Find what matters.
When a build fails, read the build log. When the app misbehaves, read the runtime log. Use the dashboard or adios logs, and share the output with your AI agent to help it find the problem.
Free to start, no card. Always-on hosting from $10/month.
IN PRACTICE
Trace a dashboard release from source to traffic.
Run adios up, then adios logs --build to see why it failed. After it ships, use adios logs --runtime --follow to watch the running app.
adios up
adios logs dashboard --build
adios logs dashboard --runtime
adios apps builds dashboard
adios ingress listHOW IT WORKS
Trace the same release from source to live traffic.
- 01
Deploy from Adios or the CLI.
- 02
Open build or runtime logs in the dashboard, or run adios logs --build or --runtime.
- 03
Check the deployment status. A healthy earlier release can keep serving while a new build fails.
WHY IT BELONGS HERE
A log line without its deploy context only tells half the story.
When build output, process logs, and release history live in different tools, finding what broke takes guesswork.
Open the log for the stage you are debugging
Build logs cover install and compilation. Runtime logs cover the running process.
Narrow the output
Use --build-id for one build, or --region and --replica when several instances run.
Use the dashboard or terminal
Logs and Observability views in the dashboard match the adios logs commands.
What’s included
- ✓ Build logs and runtime logs
- ✓ HTTP and error log views in the CLI
- ✓ Filter by build ID, region, or replica
- ✓ Observability views in the dashboard
PLANS AND LIMITS
Build and runtime logs are included on every plan.
- Observability views show the telemetry available for that workload and time range.
- A missing sample is not a zero.
CONNECTED CAPABILITIES
Keep building.
Deployments
Keep build, start, health, region, and resource settings beside the source. Each release stays tied to its logs and health state.
Explore →02 /Workflows and automation
Define cron jobs, webhooks, approvals, and ordered steps in YAML, then inspect the status and output of every run.
Explore →03 /CLI and local development
Deploy the current directory, inspect logs, manage resources, and sync with a workspace without leaving your terminal.
Explore →YOUR NEXT DEPLOY STARTS HERE
Works on localhost? Ship it tonight.
Connect your AI, say “deploy this,” and share the link. Upgrade for production from $10/month.