All guides › By use case
By use caseHosted runs: Kaloko checks your pages every morning
Kaloko opens the pages of a read-only scenario on its own browsers every day or week, in every language and viewport, and shares the run as if you had walked it.
The marketing site changes three times a week and none of those changes go through your pull requests. A CI job could walk it every night, but nobody wants to maintain one for a site they do not deploy. Hosted runs do the walking on Kaloko's side.
The problem
Scheduled checks need a machine that runs them: a CI job, a server, a laptop that stays on. For a handful of public pages that is more work than the pages themselves, so the check never gets set up and a broken page is found by a visitor.
What changes with Kaloko
On Business and Enterprise, Kaloko opens the pages of a read-only scenario on its own browsers, every day or week at the hour you choose, takes full-page screenshots in every locale and viewport, checks what can be checked from the page and shares the run under your name. Business includes 2,000 loaded pages a month, Enterprise 10,000.
How it works
- Write a read-only scenario
steps that open a page.
kaloko draft https://example.com https://example.com/pricingdrafts one from the pages themselves. - Schedule it
kaloko schedule add --scenario qa/flows/public.yml --env production --every day --at 5(the hour is UTC).--every week --weekday monruns it weekly. - Pages behind a gate
HTTP Basic credentials from the environment are sent once and stored encrypted. For signed-in pages, a person saves a session with
kaloko auth saveand the schedule uses it with--account. - Manage it
kaloko schedule listshows the next and last run and the pages used this month;run,pause,resumeandremovetake the schedule id. Settings → Integrations shows the same. - Read the result
the run appears like any other, with the comparison against the baseline. Selector, text, title and meta criteria are decided; criteria that need the full walk say "not evaluated" with the reason.
Skills and prompts
Schedule a daily Kaloko check of our public pages at 5 UTC on production, read-only, and tell me how many pages it uses a month.Expected outcome: a validated read-only scenario, one kaloko schedule add, and an estimate of pages per month from locales × viewports × steps.
Our checkout needs clicks. Give me a GitHub Actions workflow that walks it every Monday instead.Expected outcome: kaloko schedule export github --scenario qa/flows/checkout.yml --env staging --every week writes the workflow and names the secrets it needs.
What you get
- A run every morning without a CI job, with screenshots in every language and viewport.
- Deterministic checks of titles, descriptions, selectors and texts on each page.
- The same canvas, comparison and comments as any run.
FAQ
What can hosted runs not do?
Click or type: steps that do more than open a page are left out and named. Native apps, local or private addresses, credentials sent as headers and base URLs per locale also need the full walk, which kaloko schedule export github runs on the same schedule.
What counts against the page budget?
Every page loaded: each step in each locale and viewport. A scenario of 10 pages in 2 languages on desktop and mobile loads 40 pages per run.
Is production safe?
Hosted runs only open pages and read them. Nothing is clicked, submitted or created.