Free preview URLs for every pull request
Run argos deploy on your Storybook or any static build. Every pull request gets an immutable URL, a branch URL that follows it, and production lands on a domain you own. Nothing to host, and your agents run the same command.
One command, one live URL
Point the CLI at a static directory. Argos uploads the files it hasn't seen, serves the build on its own URL, and reports the status back to the pull request.
A preview URL on every pull request
argos deploy ./storybook-static uploads your build and prints an immutable URL. Share it with a reviewer, a designer, or an agent: it always points at that exact build.
Preview and production, decided by your branch
Pull requests get preview deployments. A push to your production branch, or --prod, promotes the build to the production domain the moment it is ready. Earlier builds stay reachable on their own URLs.
Any static directory
Storybook, a Vite build, a Next.js export, plain HTML. If it builds to a directory of files, argos deploy serves it.
Near-instant re-deploys
The CLI hashes every file and uploads only what Argos doesn't already have. Re-deploying an unchanged build is near-instant.
Learn moreNever expires
Deployments are permanent, immutable records. They don't age out, and they don't count toward your screenshot quota.
Learn moreLinks that hold up
Each deployment gets URLs with different promises: one that never moves, one that follows the branch, and a production domain, Argos's or yours.
Four URLs, one deployment
The deployment URL always points at one build. The branch URL updates on every push. The production domain, and your custom domain if you add one, serve the latest promoted build. All of them are listed in the Deployments tab.
Your own domain, one CNAME
Add storybook.acme.com in the project settings, point a CNAME at cname.argos-ci.live, and Argos issues the certificate. Once active, the links Argos posts to GitHub use your domain. Included in paid plans.
Access protection
Public, or Standard: previews require an Argos login while production stays open, on every plan. Team plans can require a login for all deployments, production included.
Learn moreEvery build, browsable
The Deployments tab lists every build across branches and commits with its URLs, and marks the one currently serving production.
Learn moreBranch URLs for review checklists
Put the branch URL in your pull request template. A reviewer bookmarks one link and always opens the latest build on that branch.
Learn moreWired into the pull request
Run argos deploy in the workflow you already have. Argos links the deployment to the pull request, lists its URLs in the comment, and sets a commit status you can require.
One comment, deployment and diff together
Run deploy and upload on the same commit and Argos posts a single pull request comment: the deployment on top, the visual build results underneath. One place to open the preview and see what changed.
Deploy and test in the same workflow
Build once, test it, deploy it: three steps in a GitHub Actions job. Pull request runs create previews, pushes to main create production deployments, and the same commands work on any CI.
A status you can require
Every deployment sets an argos-deploy/<project> commit status: pending while it uploads, success when it is ready. Require it in branch protection.
Any CI provider
Nothing GitHub-specific. Set ARGOS_TOKEN, run the command, and Argos picks up the commit, branch, and pull request from your CI's environment variables.
No secret on GitHub Actions
Grant id-token: write and the CLI authenticates with OIDC; on pull requests from forks it falls back to tokenless. Nothing to provision or rotate.
Your agent deploys its own preview
The deploy command is plain CLI. An agent that changed a component ships the Storybook to a URL and puts the link in its pull request, with the same token, OIDC, or tokenless authentication as argos upload.
npm i --save-dev @argos-ci/cli
argos deploy ./storybook-static
argos deploy ./storybook-static --prod
argos project deployments --project acme/storybook --json
argos project domain get --project acme/storybookCLI
argos deploy works wherever the agent has a terminal. argos project deployments --json lists what shipped, most recent first.
MCP server
Connect mcp.argos-ci.com and your assistant reads a project's deployments and updates its settings, within the scopes you grant.
Agent skill
npx skills add https://argos-ci.com installs argos-cli: the commands, flags, and authentication rules, for Claude Code, Codex, or Cursor.
“Every pull request gets a live preview of our components now. The team reviews the real thing before merging, with zero infrastructure on our side.”
Frequently asked questions
One platform, from pull request to merge
A preview is the first step. Argos then diffs what changed in it, gives your team and your agents one place to approve it, and keeps the tests behind it stable.
Supercharge your product quality
See every change your team and your agents make. Review with confidence, and merge faster.