Questions, answered.

No. Record a flow in Chrome or write the steps in plain English.

Sakiori looks for each element where it was recorded, then by its name and label, and then by what it does on the page, and checks that the step still produces what the recording saw happen. If it’s confident, it repairs the step and asks you to confirm. If it isn’t, it stops and shows you its best guess.

That’s what it’s designed to avoid. It continues only when the step also produces what the recording saw happen, such as “Item created” appearing. A dead button or a server error stops the run and is reported with a likely cause.

From the evidence of the run: whether the element was found, which network requests failed, what text did or didn’t appear, and how the page changed. When the evidence doesn’t point clearly to one cause, it’s marked “needs your call” rather than guessed.

Yes. Add each environment once (Staging, a feature build, a redesign) and run tests or whole suites on several at once.

Chain tests with “Starts from” so a login runs once at the start. Use {{unique}} for fresh data on every run, and “Remember … as {{name}}” to reuse values the app generates.

Tests run in Chromium. The recorder is a Chrome extension.

Not yet. Sakiori currently runs locally. A hosted version with team accounts is on the roadmap.

Not yet. Scheduled runs and CI/CD integration are on the roadmap, not in the product today.

Pricing isn’t set yet. Early-access teams are onboarded one at a time.