Use In Cloud

Cloud is where Glubean becomes shared and historical.

Your checks still run on your laptop or CI runner. Cloud stores uploaded runs, traces, metrics, and alerts. It does not execute your code.

What you get after --upload

• a run timeline your team can inspect
• a dashboard for the latest pass or fail state
• analytics for pass rate, latency, and flakiness
• notifications when important runs fail
• centralized redaction and retention controls

Start with these pages

1. Upload Your First Run
2. Tokens
3. Dashboard
4. Analytics
5. Notifications

One key mental model

run locally or in CI  ->  add --upload  ->  inspect the run in Cloud

A run is one execution of glubean run --upload, regardless of how many tests it contains.