Frequently Asked Questions

Everything you need to know about Aegis Replay

Data & Privacy

What data is stored?
Aegis Replay stores your test recordings, execution results, and audit evidence. With BYOK (Bring Your Own Key) enabled, all data is encrypted with your keys and stored locally in your browser or your own infrastructure. Without BYOK, cloud-synced data is encrypted at rest and in transit on our servers.
Does Aegis Replay send data to servers?
By default, Aegis Replay operates locally in your browser. Data is only sent to our servers if you explicitly enable cloud sync features. With BYOK enabled, even cloud-synced data is encrypted with your keys before leaving your browser - we cannot read it. Enterprise customers can deploy fully on-premise with no external data transmission.

Technical Questions

What is a SHA-256 audit chain?
A SHA-256 audit chain is a cryptographic record of test execution. Each test step generates a SHA-256 hash that includes the previous step's hash, creating an immutable chain. Any modification to earlier steps would change subsequent hashes, making tampering immediately detectable. This provides verifiable proof that test evidence has not been altered.
How does BYOK work?
BYOK (Bring Your Own Key) lets you control encryption for your test data. You generate or provide your own encryption keys, which are stored securely in your browser or key management system. All data is encrypted/decrypted client-side using your keys. Aegis Replay never has access to your unencrypted data or your encryption keys.
Can I export evidence?
Yes. Aegis Replay exports complete evidence bundles containing: HTML report (human-readable), JSON data (machine-readable), screenshots, DOM snapshots, and the cryptographic audit chain. Evidence packages can be exported as ZIP files for offline storage or sharing with auditors. All exports include verification tools.
Can I run in CI?
Yes. Professional and Enterprise plans include CI/CD integration. We provide GitHub Actions support, with GitLab CI, Jenkins, and Azure DevOps coming soon. Tests run headlessly with full audit trail generation. CI pipelines can be configured for fail-closed policy gating - blocking deployments when verification fails.

Additional Questions

What browsers do you support?
Our Chrome extension works with Chrome and Chromium-based browsers (Edge, Brave). For CI/CD execution, we support Chrome, Firefox, Safari, and Edge through Puppeteer and Playwright runners. Enterprise customers can request additional browser support.
How do self-healing selectors work?
When a selector breaks, our AI analyzes multiple attributes of the element (id, class, text, position, aria labels) and finds the best alternative. It prioritizes stable selectors like data-testid attributes and falls back through increasingly generic selectors. The healing happens automatically during test execution.
What is BYOK and why does it matter?
BYOK (Bring Your Own Key) means you control the encryption keys for your test data. Your data is encrypted before it ever leaves your infrastructure, and we never have access to the decryption keys. This is essential for industries handling sensitive data like healthcare, finance, and government.
Can we do a security review before purchasing?
Absolutely. Enterprise customers can conduct security reviews, penetration testing, and code audits before purchasing. We also provide detailed security whitepapers and architecture documentation. Contact aegisdev189@gmail.com to start the process.

Still Have Questions?

Our team is ready to help you get started.

Contact Support Talk to Sales