FAQ

​

How is this different from a typical staging environment?

Most staging environments only include your own application. Arga environments include external services as well through API-compatible twins. This allows staging workflows to behave more like the real world without touching production systems.

​

Does Arga require replacing my existing CI/CD?

No. You can connect your repository and add a small arga.yaml configuration file. Arga can then deploy sandboxed services around your existing CI/CD workflow.

​

Why not just write tests with mocks?

Mock-based tests work well for narrow scripted scenarios. Agents and action-taking systems can take unexpected paths, mutate state, send messages, or hit rate limits before a scripted test catches issues.

Twins provide realistic tools in a controlled environment that can be reset and replayed.

​

Is Arga primarily a validation tool?

Not primarily. Arga provides infrastructure for safe action. Validation is built on top by running the system, capturing what happened, and comparing outcomes against production data.

​

Should I replace my existing testing frameworks?

No. Tools such as Cypress and Playwright remain useful for the tests you explicitly write. Arga focuses on the gaps those tests may miss, including cross-service behavior, UI flows, and integration side effects.

​

Do sandbox runs modify production systems?

No. Runs interact with isolated API twins of services like Stripe, Slack, and Jira. Production data can be used as a comparison baseline, but sandbox runs do not write to production services.

​

What if a service I use is not supported?

Unsupported integrations are flagged and skipped gracefully. You can review supported services on the twins page or request additional integrations.