FAQs

What is a software simulation?

CodeYam's software simulations are the captured artifacts of running every part of a software application in a sandbox environment with semantically-aware, AI-generated, mock data.

These artifacts are in the form of screenshots, interactive webpages, and data logs. They demonstrate exactly how each part of the software behaves under different data scenarios.

The artifacts can be used to validate any changes to the software, for sharing and demoing with others, and as robust acceptance test suite to ensure nothing has changed unexpectedly.

How are software simulations created?

What problem does CodeYam solve?

How does CodeYam integrate in my existing workflow?

How is CodeYam different from a staging environment?

How is CodeYam different from Playwright / Selenium / Cypress / Puppeteer?

What languages and frameworks does CodeYam support?

Does my software have to be architected in a specific way?

How does CodeYam facilitate collaboration?

How does CodeYam manage data privacy and security concerns?

How much effort is it to integrate CodeYam?

Does CodeYam require access to my code and/or database?

CURIOUS ABOUT CODEYAM?

We support TypeScript, React, Next.js, Remix (more soon)

Integration: GitHub App (post-commit), CLI tool (pre-commit, coming soon)

Security: Simulations run in isolated environments