> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/overview.md). # Overview Argos is a visual testing platform that catches visual regressions before they reach production. Your tests capture screenshots, Argos compares them against a baseline, and you review the changes on your pull requests. It works with the tools you already use — Playwright, Storybook, Cypress, Vitest, or any pipeline that produces screenshots. ### How it works
Diagram of the Argos workflow, from capturing screenshots in CI to approving changes on the pull request
1. **Your tests capture** screenshots in CI. 2. **Your CI uploads** the screenshots to Argos. 3. **Argos compares** them against the [baseline build](/docs/learn/platform-fundamentals/baseline-build.md). 4. **You review** visual diffs on the pull request. 5. **You approve** expected changes or reject regressions. 6. **Argos updates** the pull request check, so you can merge with confidence. ### When to use Argos Use Argos when visual changes affect product quality or release confidence: * **UI regressions**: Catch broken layouts, CSS changes, and missing images, icons, or fonts. * **Design systems**: Track component changes across themes, browsers, and viewports. * **Product variants**: Validate white-labeled interfaces, translations, and localized layouts. * **AI-generated UI**: Visually validate generated changes before merging them. ### Open source and self-hosting Argos is open source: the whole platform — backend, frontend, and the screenshot comparison engine — is developed in the open in the MIT-licensed [argos-ci/argos](https://github.com/argos-ci/argos) repository. There is no closed-source component behind the diff service. Argos is operated as a managed cloud service, and that is the supported way to run it. Self-hosting is not officially supported or documented: the production setup targets AWS and depends on PostgreSQL, RabbitMQ, Redis, S3, and DynamoDB, plus integrations such as the GitHub App and Stripe — you would be on your own to deploy and operate them. If your organization has strict hosting or compliance requirements, [contact us](https://argos-ci.com/contact) about the Enterprise plan. ### Get started Ready to add Argos to your project? Pick your framework in the [Quickstart](/docs/quickstart.md) — you'll upload your first build and see it on a pull request in a few minutes. ### Explore more Once Argos is set up, go deeper: * [Core concepts](/docs/learn/platform-fundamentals.md) – How Argos compares screenshots and picks a baseline * [Review workflow](/docs/learn/review-workflow.md) – Review builds in the dashboard and on your pull requests * [Stabilize screenshots](/docs/learn/reliability-and-flakiness/flaky-tests.md) – Keep your visual tests free of flakiness * [Integrations](/docs/learn/integrations.md) – Connect GitHub, GitLab, and Slack --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://argos-ci.com/docs/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.