Hosted Storybook with a stable per-branch URL

When UI Verify captures a build it keeps the built Storybook and re-serves it, so the exact Storybook behind any build stays browsable: open a story, run its play function, flip its controls, not just look at the captured screenshot. Each build gets its own URL, and each branch gets a stable one that always points at its latest build.

The hosted Storybook is a live render: opening a story runs its play function and real DOM, exactly as your local Storybook would. The screenshot UI Verify diffs on your pull request is the frozen capture, taken with capture-time determinism (a pinned clock, settled animations). So the hosted view is for exploring and sharing, and the diff on the pull request is the exact reviewed pixels. See how visual testing works and set up Storybook visual testing.

A per-build URL, https://<build-id>.storybook.uiverify.ai, serves that one build forever and never changes, so it is the permalink to link from a specific pull request. A per-branch URL, https://<branch>--<project-id>.storybook.uiverify.ai, is the stable reference: it always serves the branch's latest build, so a link to main--<project-id> follows main as new builds land. A build that failed while its upload was being processed, such as an empty or broken upload, is skipped, so the link keeps serving the last Storybook that worked.

Open your project's API settings (Manage, then API key). Next to your project API key, UI Verify shows the stable live-Storybook URL for your default branch, ready to copy. It appears once your default branch has a build with a Storybook to serve, so the link never points at nothing.

For a public project both URLs open to anyone with no login, so the link is shareable. For a private project a signed-in member opens it from the build page with Open Storybook; the bundle is not open to anonymous requests.

UI Verify runs the visual regression for you: uiverify upload captures every story and flags the changed ones on your pull request. For the functional side, your stories' play functions and interaction assertions, run them as Vitest tests with Storybook's Vitest addon. It runs your stories in a headless browser straight from source, with no Storybook server to build or host, so it is far faster than pointing a test-runner at a remote URL. See Storybook's Vitest addon guide.