Build a Windows-on-Chrome-120 user or a macOS user in Japan, per profile.
Deterministic profiles mean the same identity every launch, so issues recur.
Each profile keeps its own cookies, storage and test account, fully apart.
Record a journey once and replay it across your environment matrix.
Every OS, locale and kernel as a deterministic profile
Cross an OS identity with a pinned Chromium kernel and a locale, and you have one cell of your test matrix. Each cell is a profile that launches the same way every time, so the bug you found stays found.
OS x locale x kernel, one profile per cell
Combine an OS identity, a pinned kernel from Chrome 86 to the current majors, and per-profile locale, timezone and geolocation. Surfaces report values consistent with the chosen OS, all from your Mac.
Deterministic, so bugs reproduce
A profile presents the same identity every launch, with noise surfaces stable for that profile rather than re-randomized each session. An environment-dependent defect recurs instead of appearing at random.
Sweep the matrix in one run
Record a regression journey once and replay it across many profiles at once with fleet commands, or drive profiles from your existing Selenium, Puppeteer and Playwright scripts, or an MCP-compatible agent.
Every cell of the matrix stays fully apart, so one test session never bleeds into the next and each environment behaves like a clean, separate user.
Bugs hide in environments you cannot recreate
A defect that only shows up on a German locale or an older Chrome is hard to catch from one default browser. Oculr turns each environment into a deterministic profile you can launch again and again.
Build the exact environments your users have
Each profile combines an OS identity with a pinned Chromium kernel and per-profile locale, timezone and geolocation, so you can test a Windows user on Chrome 120 in Germany or a macOS user on the current major in Japan. Surfaces report values consistent with the chosen OS, all from your Mac.
- OS identity plus a pinned kernel, from Chrome 86 to current
- Per-profile locale, timezone and geolocation
- Identity and environment configuration on real Chromium
Deterministic profiles, so bugs reproduce
A profile presents the same identity every launch, with noise surfaces stable for that profile instead of re-randomized each session. Combined with isolated cookies, storage and a test account per profile, an environment-dependent bug recurs reliably rather than appearing at random.
- The same identity every launch
- Isolated cookies, storage and test account per profile
- Stable per-profile fingerprint, not re-randomized each run
Automate regression across the matrix
Record a regression journey once and replay it on a profile with variables, or run it across many profiles at once with fleet commands to sweep your whole environment matrix. Or drive profiles from your existing Selenium, Puppeteer and Playwright scripts, or from an MCP-compatible agent.
- Record once, replay with record-and-replay workflows
- Fleet runs across your environment matrix
- Selenium, Puppeteer, Playwright or MCP all attach
Frequently asked questions
What does cross-environment browser testing mean here?+
Testing your site against the environments your users actually have: a Windows user on Chrome 120 in Germany, a macOS user on the current major in Japan, and so on. Each environment is a profile combining an OS identity, a pinned browser kernel, and locale, timezone and geolocation settings.
How does Oculr present different OS and browser versions?+
Each profile sets its OS identity (Windows, macOS or Linux) and pins an exact Chromium kernel, from Chrome 86 to the current majors, so the user agent and client hints match the real engine. Surfaces report values consistent with the chosen OS. Note that font and GPU pixel realism on cross-OS profiles have documented limits, so this is identity and environment configuration, not pixel-perfect device emulation.
Will the same environment reproduce the same bug?+
That is the point of deterministic profiles. A profile presents the same identity every launch, with noise surfaces stable for that profile rather than re-randomized each session, so a bug that depends on a given environment recurs instead of appearing at random.
Can I automate regression runs?+
Yes. Record a journey once and replay it on a profile with variables, or run it across many profiles at once with fleet commands to cover your environment matrix. You can also drive profiles from existing Selenium, Puppeteer and Playwright scripts, or from an MCP-compatible agent.
Is this a device farm?+
No. Oculr presents configured OS and browser identities on real Chromium from one machine. It is identity and environment configuration, not a fleet of physical devices, so use it for environment-dependent web testing rather than hardware-level device validation.
Test as your users really are
Spin up your first two profiles free, build two of your trickiest environments, and reproduce that locale-only bug on demand today.
No credit card required · Cancel anytime