Use case · docs and changelogs

Screenshots of your own product, from CI.

Take the pictures in your documentation on every release, from the pipeline, so they are never a version behind the thing they document.

Start free See the parameters

from CI

docs and changelogs Docs and changelogs Retake every screenshot in your docs on each release, so none is ever a version behind.

the problem

Documentation screenshots rot silently.

Documentation screenshots rot silently. Nobody notices that the button moved three releases ago until a customer does, and re-taking them by hand is exactly the chore that gets skipped.

the answer

One call per image, on every release.

One call per image in CI, against your staging URL, with the same parameters every time. Commit what comes back, or serve it from us.

// the call
{
  "url": "https://staging.example.com/dashboard",
  "preset": "macbook-air",
  "hide_selectors": ".intercom-launcher, #cookie-banner"
}

1 call per image

A domain-restricted API key means the token in your CI can only ever be pointed at your own hosts.