Every screen your app renders, in one place
Your run finishes in CI and lands here. You open the flows, look at the screens, and write what is wrong next to the one you were looking at.
- 1Sign-up
- 2Inbox
- 3Settings
Three things you do with a run
- 1
Upload the run
sk-runner posts it over an API key. From a laptop, a CI box, or a script in another repo — the endpoint is keyed, not hosted, so it answers on every host.
- 2
Open the flows
Screens arrive grouped into the flows that produced them. Thumbnails, then fullscreen, then the next one. Screens that did not change since the last run say so.
- 3
Say what is wrong
A comment belongs to a flow, and carries the screen you had open when you wrote it. Six months later it still says which screen it was about.
Nothing is up for discussion until you promote it
A run arrives private. Comments are off — not hidden, off, refused by the server. Promoting it is what opens the discussion and tells the reviewers you picked. Builds nobody promoted and nobody commented on archive themselves after two weeks.
- BuildUploaded. Yours to look through. Nobody can comment.
- Open for reviewPromoted. Your reviewers were told. Comments are on.
- ResolvedDone with. Everything said about it stays said.
What it does not do
- No pixel-diff verdict.It shows you which screens changed and leaves the judgement to you.
- No gate in your pipeline.Uploading a run never fails a build. Review happens beside CI, not inside it.
- No per-seat pricing.Invite everyone who should look. One price for the workspace.
- No lock-in on the uploader.sk-runner is a config file and an API key. What it posts is yours.
1 000 krper month, per workspace
Ex. VAT. Invoiced through PayoutPartner. No card.
The whole price pagePoint your run at it tonight
Make a workspace, mint an API key, and post your first run. Nothing to install here.
Create a workspaceSign in