Observability
Watch a build stream, then follow the running service. Every environment has its own logs and metrics, in the same place you shipped it.
The build log as it streams, runtime logs for production, then its metrics — one view, no tool switch.
From build to running service.
When you ship, the build log streams live so you can see what happened if something fails. Once the service is running, its logs and metrics are one click away from the same view. You do not switch tools to find out how a deploy is doing.
When you push, the build log streams as it runs, so you see what happened the moment something fails.
▸ pnpm build — 27s
Once the deploy is out, its logs and metrics are one click away from the same view. No second tool.
revision lc-042 · 1 instance
Runtime logs stream from the running service, filtered to the environment you are looking at.
env: production
Requests, latency, instances, and errors for the service, without setting up a monitoring stack first.
p95 61 ms · 1 error
Production and every preview, kept separate.
Each environment has its own logs and its own metrics. Pick the one you are looking at and you see only what it did — a preview never muddies the production picture.
What you get with every environment.
Watch a build as it runs and read the full log from the deploy record afterwards.
Stream logs from the running service, filtered to the environment you are looking at.
See how a service is doing at a glance, without setting up a monitoring stack first.
Production and every preview have their own logs and metrics, kept separate.
Observability lives in the same console you deploy from, next to the environment it belongs to.
Every deploy keeps its build log with its commit, author, duration, and status, so you can go back to it.
Connect a repository, push, and watch it go live. Start free on the Free plan.