Dovra — 1.1.0

Dovra — 1.1.0

Dovra is a Chromium-based browser built for AI agents and automation workflows. Version 1.1.0. The underlying Chromium technical version is 153.0.8010.48. Published by DOVRA SOFTWARE LTD.

What changed since 1.0.0

• Native control bar. A control bar rendered outside the page DOM. It survives cross-navigation, iframe changes, DPI scaling, and fullscreen transitions without injecting scripts or modifying page content.
• Agent input authorization. Physical keyboard and mouse input can be intercepted at the window level. Input dispatched through the Chrome DevTools Protocol (CDP) is recognized and permitted. A takeover button lets a human reclaim control; a generation gate prevents accidental input during automated sequences.

Downloads

Release files are distributed from https://dl.dovra.dev/1.1.0/; the GitHub release entry carries links only.

• Dovra-1.1.0-win-x64-portable.zip: complete browser, launcher and offline notices (179,436,315 bytes, SHA-256 375d275cfdcf22a1e1d4bc2e984717df323ade364463195a8c3c1cc87701aec9).
• SHA256SUMS.txt: SHA-256 checksums for all files of this batch.
• Component source, relinking and LGPL modification archives: listed in SOURCE-MATERIALS.md.

GitHub's automatic repository source ZIP/tarball contains repository files, not the compiled browser or the full Chromium source tree.

Capabilities

• Separate task sessions. Use named browser profiles to keep a task's data together. Return to a profile to continue a session, or choose another profile for a separate test.
• Configurable environments. Choose language, time zone, and hardware parameters for your test. Save the settings with your results so you can review what the browser used.
• Native control bar. A toolbar that does not touch the page DOM. It remains visible across navigation, iframe changes, DPI scaling, and fullscreen.
• Agent input authorization. Intercept physical input at the window level; permit CDP-dispatched input; a takeover button and generation gate give human control when needed.
• Playwright support. Connect and drive pages with Playwright through the Chrome DevTools Protocol (CDP). Compatibility depends on the build and the APIs your workflow uses.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

Native control bar and agent input authorization (automated acceptance, 5/5 pass): The control bar UI is present and does not pollute the page DOM. CDP insertText and dispatchDragEvent authorization input passes under agent mode. Clipboard paste is intercepted under agent mode. The generation gate does not false-trigger (CDP input is normal without takeover).

Code is in place but pending manual validation: IME composition input, TSF password learning gate, OS drag-and-drop, context-menu commands, and accessibility (AX) actions.

Signing status: dovra_browser.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned), pending Azure Trusted Signing. A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use Dovra for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this build; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: legal@dovra.dev

Dovra — 1.0.0

Dovra — 1.0.0

Dovra is a Chromium-based browser built for AI agents and automation workflows. Version 1.0.0. The underlying Chromium technical version is 153.0.8010.48. Published by DOVRA SOFTWARE LTD.

What changed since the last Beta

• Explicit identity. The toolkit can set time zone, language, CPU cores, and screen parameters as one named set (identity.mode = explicit). Six consistency checks pass; positive and negative test runs report 5 pass / 0 fail.
• Diagnostics documentation. README, REFERENCE.zh-CN, and FEATURES now describe the diagnostics capability surface. These remain unsupported for production workflows.
• Company and legal. Dovra is now provided by DOVRA SOFTWARE LTD, a private company limited by shares registered in England and Wales (company number 17493263). The terms of use and privacy notice identify the Company as provider and data controller. Governing law is England and Wales, with mandatory consumer protections preserved. The website footer and business correspondence carry the company registration details required by section 82 of the Companies Act 2006.
• Release signing. Release builds are pending Azure Trusted Signing. Builds remain unsigned by a commercial certificate authority at this time.

Downloads

Release files are distributed from https://dl.dovra.dev/1.0.0/; the GitHub release entry carries links only.

• Dovra-1.0.0-win-x64-portable.zip: complete browser, launcher and offline notices (179438340 bytes, SHA-256 f73aebade9328ea93d39746497a716486648616e5a87a05f3cd492d70d144747).
• Dovra-Toolkit-1.0.0.zip: optional companion toolkit; no browser included (110381 bytes, SHA-256 ae3429ca305e8fe4b59dd185c45d9127781dfcbab23a20692c8a39d85ea9f1e4).
• SHA256SUMS.txt: SHA-256 checksums for all files of this batch.
• Component source, relinking and LGPL modification archives: listed in SOURCE-MATERIALS.md.

GitHub's automatic repository source ZIP/tarball contains repository files, not the compiled browser or the full Chromium source tree.

Capabilities

• Separate task sessions. Use named browser profiles to keep a task's data together. Return to a profile to continue a session, or choose another profile for a separate test.
• Configurable environments. Choose language, time zone, and hardware parameters for your test. Save the settings with your results so you can review what the browser used.
• Companion toolkit. Read rendered page content, links, and interactive elements. Use defined actions to navigate, click, fill forms, and extract results.
• Playwright support. Connect and drive pages with Playwright through the Chrome DevTools Protocol (CDP). Compatibility depends on the build and the APIs your workflow uses.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

The packaged runtime passes acceptance checks: the credits page renders, LICENSE, NOTICE and TERMS.md are present in bin/, and a 60-second idle run made no request to any external host. The toolkit test suite passes. The post-release detection suite reports no newly failing item relative to beta-20260925-4.

Signing status: dovra_browser.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned), pending Azure Trusted Signing. A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use Dovra for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this build; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: dovra.dev@gmail.com

Dovra Beta — beta-20260925-4

Dovra Beta — beta-20260925-4

Free experimental Windows x64 portable build with an English interface. This is a Beta, not a stable release or a formal Dovra product version. The underlying Chromium technical version is 153.0.8010.48.

What changed since beta-20260924

• Browser — WebRTC name lookups. In the default WebRTC IP handling of this build (which sends no UDP), WebRTC no longer resolves any host name itself: the names of TURN servers that use TCP (transport=tcp) or TLS (turns:) are handed to the connection layer, which sends them to the proxy when one is set, and remote candidates whose address is a host name (including mDNS .local names) are not resolved at all, with or without a proxy, so a peer is reachable only through its relay or IP-address candidates (a peer offering only host-name candidates and no relay cannot be reached). The earlier build looked these names up with the local DNS resolver or with multicast DNS even with a proxy set. The change is confined to the WebRTC integration of the renderer (third_party/blink/renderer/platform/p2p/port_allocator.cc with its header, and third_party/blink/renderer/modules/peerconnection/peer_connection_dependency_factory.cc; BSD-licensed Chromium code); the LGPL-licensed Blink files and their modifications are the same as in beta-20260924.
• Toolkit. Dovra-Toolkit-beta-20260925-4.zip contains the toolkit changes published as the toolkit-only batches beta-20260925, beta-20260925-2 and beta-20260925-3 (the dovra integration command line: launch contract, identity blueprints, checkpoints). New in this batch: dovra recognises this browser build and offers proxies on it (network.mode = proxy with http or socks5); with the beta-20260924 browser, proxies remain refused.
• Release files are distributed from https://dl.dovra.dev/beta-20260925-4/; the GitHub release entry carries links only.
• The Chromium engine (153.0.8010.48), the rest of the patch set, the seed-derived variation module and the bundled component set are unchanged from beta-20260924.

Downloads

• Dovra-Beta-20260925-4-win-x64.zip: complete browser, launcher and offline notices (179476296 bytes, SHA-256 55d0f0d1e3d2d5b4ebee1dfcbd2124e016ac38ffe5fe5c8726f36ed6cf09a9fc).
• Dovra-Toolkit-beta-20260925-4.zip: optional companion toolkit; no browser included (SHA-256 977cc7f97ab057d453ad18dc77e1759891b063b8828b041641cc8ca76c638409).
• SHA256SUMS.txt: SHA-256 checksums for all files of this batch.
• Component source, relinking and LGPL modification archives: listed in SOURCE-MATERIALS.md.

GitHub's automatic repository source ZIP/tarball contains repository files, not the compiled browser or the full Chromium source tree.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

Checks run on this batch

• Without a seed, the page-observable build features (tests/probe-dump.js, 70 groups) and the open-source FingerprintJS components (tests/probe-fpjs.js, 41 components) of the packaged runtime were compared item by item against the beta-20260924 binary: the FingerprintJS components are identical; in the build features only the network downlink estimate and the timer-precision samples differ, and both also vary between two runs of the same binary.
• With --fingerprint=123456789 and --fingerprint=987654321 (tests/probe-seeded-noise.js) every recorded value equals the beta-20260924 run of the same seed.
• Proxy mode, HTTP and SOCKS5 proxy on this machine, DNS traffic captured at the network adapter while pages used freshly generated host names: no local DNS query for the page, its subresources, a STUN server, or TURN servers over UDP, TCP (transport=tcp) and TLS (turns:); the TURN server names appeared in the requests received by the proxy. Remote candidates added by the page with a host name (UDP and TCP) and with an mDNS .local name caused no DNS query and no multicast DNS packet (the capture covered port 5353 as well); on an intermediate build without this part of the change, the same page produced both. A lookup made outside the browser during the same capture was recorded, confirming the capture saw DNS traffic.
• WebTransport (HTTP/3 over UDP) to a UDP listener on the local network: 0 packets arrived with a proxy set, 6 without a proxy.
• With an unreachable proxy, navigation fails with ERR_PROXY_CONNECTION_FAILED; no direct TCP connection, no UDP and no DNS query for any of the names above were observed.
• Without a proxy, page and TURN server names are resolved by the browser's network service as before; remote candidate host names are not resolved in this build's default WebRTC IP handling with or without a proxy.
• The toolkit's test suite passes all 61 checks on this build, none skipped, including the live proxy tests (proxy http, proxy socks5: pages and downloads reach the proxy by host name, no other TCP connection from any browser process, no WebRTC UDP to an IP-literal STUN server).
• Packaged runtime (tests/t11-acceptance.js): the credits page renders, LICENSE, NOTICE and TERMS.md are present in bin/, and a 60-second idle run made no request to any external host.
• The post-release detection suite (tests/post-release.js, 55 signals, recommended profile) reported 33 passes on the packaged runtime, the same as beta-20260924, and no newly failing item; every remaining item was already attributed on earlier batches (maxTouchPoints reported by the host machine; the Intl default locale following the en-US interface language of this package; host and site-side items tracked separately).

Carried over from the beta-20260916 build of the same engine

The following checks were performed on the beta-20260916 build (same engine and configuration; the Microsoft SDK runtime components present in that build are no longer shipped) and were not repeated for this batch. Accepted tests: English built-in pages and the engine version were checked; the version, Settings, credits and GPU pages were visually reviewed. Targeted checks covered eight credits entries with complete licence text and expanded display, Canvas output, a WebGL 2 draw/readback, short local PCM and FLAC playback, and test localStorage retained after a graceful close and reopen. These were browser checks, not a test of the packaged launcher or a clean-machine installation.

The tested CDP endpoint listened only on 127.0.0.1, rejected the tested foreign Host requests and foreign/null WebSocket Origin handshakes, and permitted the trusted local client. A foreign-Origin HTTP request returned 200 without an Access-Control-Allow-Origin response header; it was not rejected at the HTTP layer. Local programs can still control the browser through CDP. This is not authentication or protection from local malware.

The reviewed idle NetLog fields recorded WPAD activity and no external destination host. This finite observation is not a zero-network or zero-telemetry guarantee. WebGL success does not verify all WebGPU, GPU, codec or sandbox paths. Nonfatal SharedImageManager::ProduceSkia mailbox messages were observed; the sampled drawing and playback checks completed.

Signing status: dovra_browser.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned). A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use this build for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this candidate; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: dovra.dev@gmail.com

Dovra Beta — beta-20260925-3

Dovra Beta — beta-20260925-3

Toolkit-only batch, the third of 25 September 2026. The browser is unchanged: use the browser package of batch beta-20260924 (Chromium technical version 153.0.8010.48). This is a Beta, not a stable release or a formal Dovra product version.

What changed since beta-20260925-2

• Fix: every dovra command printed a Node.js ExperimentalWarning about SQLite on stderr (the capability check loaded the module to see whether it exists). It now only checks for it. Output on stdout, exit codes and behavior are unchanged.
• Proxies are still not available, and a configuration with network.mode = proxy is still refused with UNSUPPORTED_CAPABILITY. The capability report now says why and what was measured (network.proxy.http / network.proxy.socks5: checkedByTestSuite, measuredOnce, knownLeaks, notTested), and cli/README.md has a new Network section:
  • measured: page and download traffic reaches the proxy by host name; no browser process connects anywhere but the proxy; WebRTC sends no UDP to an IP-literal STUN server; no local DNS lookup for names used by page navigation, subresources, prefetch, preconnect, STUN and UDP TURN;
  • open: a page that lists a WebRTC TURN server with transport=tcp or a turns: server makes the browser resolve that server name with the local DNS resolver. No setting closes this; proxies become available after a browser change that is verified for it;
  • not tested yet: WebTransport / QUIC.
• The toolkit test suite gains configuration checks for proxy values and two live proxy tests that run once proxies are supported (they are reported as skipped until then).

Downloads

• Dovra-Toolkit-beta-20260925-3.zip: companion toolkit; no browser included (222052 bytes, SHA-256 70d76bf1fc53d3e6a398bd39cb9a0d6acbab11c0daca32cb5e441d092f1aa5bf).
• SHA256SUMS.txt: SHA-256 checksum of this batch's file.
• Browser (unchanged): Dovra-Beta-20260924-win-x64.zip (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0), with its component source, relinking and LGPL modification archives under https://dl.dovra.dev/beta-20260924/ as listed in SOURCE-MATERIALS.md.

Verified scope

Tested environment: Windows Server 2022 x64 (OS build 20348), Node.js 24.12, playwright-core 1.63.0, browser files of batch beta-20260924 (chrome.dll SHA-256 411c27ab…3991, chrome.exe e409e52a…93fd).

• The toolkit's test suite passed 59 checks with 2 skipped (the live proxy tests, while proxies are unsupported), in the workspace and from the extracted toolkit archive.
• An independent review covered the proxy work (three rounds: the first found the WebRTC TURN name lookup, the second required keeping proxies unsupported until it is fixed, the third confirmed that).
• Everything stated for beta-20260925-2 still applies, including: moving a checkpoint between two different Windows machines has not been verified.

Use Dovra for your own applications, authorized tests and automation permitted by the service you access. See the use principles.

Dovra Beta — beta-20260925-2

Dovra Beta — beta-20260925-2

Toolkit-only batch, the second of 25 September 2026. The browser is unchanged: use the browser package of batch beta-20260924 (Chromium technical version 153.0.8010.48). This is a Beta, not a stable release or a formal Dovra product version.

What changed since beta-20260925

The dovra integration command line (cli/) gains two capabilities that were listed as unavailable in beta-20260925.

• Per-profile identity (identity.mode = blueprint). A profile can carry a consistent region and device definition from the toolkit's profiles/ catalog (dovra identity catalog lists them). It is resolved once, on the profile's first launch, and frozen into the profile folder; later launches reuse it unchanged, and dovra config resolve previews it beforehand.
  • Applied: time zone, interface and content languages, Accept-Language, hardwareConcurrency with the matching platform version, and the device screen size in headless mode. GPU strings, deviceMemory, maxTouchPoints, WebRTC, geolocation and canvas/audio variation stay at host values; receipts list what is applied and what stays at host values.
  • Changing an identity is a separate step (dovra identity reconfigure, refused while the profile is open). A configuration that does not match the frozen identity is refused with IDENTITY_MISMATCH.
  • The frozen file holds typed values only, never browser switches, and is validated on every launch; a file that does not match the expected structure is refused before any browser starts.
  • Known limit: the browser package ships an English interface only, so the default Intl locale stays en-US even when the region's language differs.
• Checkpoints (recoverable site data). dovra close --checkpoint <new file> closes the instance normally and writes its cookies (including partitioned cookies and session cookies), localStorage, IndexedDB and open tabs with their sessionStorage to a new file. A new profile imports it with "checkpoint": { "importFrom": "<file>" } before it reports ready.
  • Data moves through the browser's own storage interfaces. No profile files and no encryption keys are copied; the receiving browser stores the data again under its own machine's and user's protection.
  • Reading and writing site storage happens in a hidden headless browser whose requests are answered locally or refused; it does not load the sites.
  • Import is all or nothing: the file is validated as untrusted input, written in a staging folder and moved into place only after a clean close; on any failure no profile is created (CHECKPOINT_INCOMPLETE or CONFIG_INVALID).
  • Not included: history, bookmarks and settings (no interface for a logical export in this build); cache, service workers, passwords, autofill, payment data and extensions by design. Device-bound credentials cannot move between devices.
  • The checkpoint file is plain text containing sign-in cookies and is created readable only by the current Windows user. Encrypt it before storing or sending it.
  • IndexedDB in checkpoints needs Node.js 22.5 or later.
• dovra capabilities reports each checkpoint item as supported or unsupported with a reason, and states the verified scope in machine-readable form (verifiedScope / unverifiedScope).
• Still defined but not available, and refused with UNSUPPORTED_CAPABILITY: explicit identity values, proxies, a standard diagnostics mode, ephemeral profile copies, extensions.

Downloads

• Dovra-Toolkit-beta-20260925-2.zip: companion toolkit; no browser included (214998 bytes, SHA-256 f4ace424c401abdd1ae0dbf48efac6c4404b418bfa36e128d389f10e95a4719a).
• SHA256SUMS.txt: SHA-256 checksum of this batch's file.
• Browser (unchanged): Dovra-Beta-20260924-win-x64.zip (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0), with its component source, relinking and LGPL modification archives under https://dl.dovra.dev/beta-20260924/ as listed in SOURCE-MATERIALS.md.

Verified scope

Tested environment: Windows Server 2022 x64 (OS build 20348), Node.js 24.12, playwright-core 1.63.0, browser files of batch beta-20260924 (chrome.dll SHA-256 411c27ab…3991, chrome.exe e409e52a…93fd).

• The toolkit's test suite (node cli/test/run-tests.js --browser-dir <browser package> --playwright <playwright-core>) passed 58 checks against that browser, including, for this batch:
  • blueprint: catalog listing and invalid values, preview equals the frozen identity, page-observed values equal the frozen values, restart reuses the identity byte for byte, reconfigure revisions, determinism, and ten ways of tampering with the frozen file (all refused before a browser starts);
  • checkpoints: export, import into a new profile, read-back of every item, clean close and restart with persistent data intact; a modified file, malformed files, over-limit files, a failure midway (rolled back, nothing created), expired cookies (not restored), import into a profile that already has data (refused), an existing output file (never overwritten), and clean-up after a supervisor that stopped during an import.
• The suite was also run from the extracted toolkit archive itself.
• An independent review was performed before release (identity: two rounds, the first found a blocking issue — frozen files could inject browser switches — fixed before release; checkpoints: three rounds; the second found a blocking issue — clean-up after an interrupted import could remove another folder's import in progress — fixed before release).
• Not verified: moving a checkpoint between two different Windows machines or two Windows users (checked only between two profiles on one machine), clean Windows 10/11 client machines, other Node.js versions.

Known limitation carried over from the browser: Playwright page.setContent() times out because this build does not report console events; use page.goto() or page.evaluate().

Use Dovra for your own applications, authorized tests and automation permitted by the service you access. See the use principles.

Dovra Beta — beta-20260925

Dovra Beta — beta-20260925

Toolkit-only batch. The browser is unchanged: use the browser package of batch beta-20260924 (Chromium technical version 153.0.8010.48). This is a Beta, not a stable release or a formal Dovra product version.

What changed since beta-20260924

• The companion toolkit adds cli/, the dovra integration command line. A program that manages browser environments can validate a JSON launch configuration (dovra config validate / resolve), ask what the exact browser build supports (dovra capabilities), start one instance per profile and wait for the browser's own handshake (dovra launch), query it (dovra status), and close it with a definite result (dovra close; dovra kill is a separate, recorded forced termination).
  • The configuration is organised by purpose — profile, identity, network, instance, control — and accepts no raw browser switches. Unknown fields, duplicate keys and out-of-range values are rejected with a JSON Pointer to the field.
  • Every command prints one JSON object; decisions are made on stable error codes and exit codes (listed in cli/README.md).
  • The browser opens no debugging port. Control goes through a loopback endpoint that requires a capability issued by dovra; connections carrying a web Origin header are refused; issuing a new capability disconnects the previous controller. Other programs running as the same Windows user are outside this protection.
  • Retrying launch with the same idempotency key returns the original instance instead of starting a second one.
  • Defined but not available in this version, and refused with UNSUPPORTED_CAPABILITY rather than accepted without effect: device/region blueprints, proxies, a standard diagnostics mode, native storage export/import, restoring the last session, ephemeral profile copies, extensions.
  • It is a Node.js program (Node.js 18 or later), not a standalone executable. Capabilities are keyed to the SHA-256 of the browser files; this version knows the beta-20260924 browser.
• skills/dovra-browser/scripts/launch.js no longer falls back silently to bare settings when a profile preset cannot be resolved, and no longer rewrites profile-id characters (two different ids could share one data folder); it now stops with an error in both cases.

Downloads

• Dovra-Toolkit-beta-20260925.zip: companion toolkit with the integration command line; no browser included (168599 bytes, SHA-256 0cb94960df0466f7337c94bd80fb6a8fee6b1b0da62389dfc09e5be2f3c801b5).
• SHA256SUMS.txt: SHA-256 checksum of this batch's file.
• Browser (unchanged): Dovra-Beta-20260924-win-x64.zip (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0), with its component source, relinking and LGPL modification archives under https://dl.dovra.dev/beta-20260924/ as listed in SOURCE-MATERIALS.md.

Verified scope

Tested environment: Windows Server 2022 x64 (OS build 20348), Node.js 24.12, playwright-core 1.63.0, browser files of batch beta-20260924 (chrome.dll SHA-256 411c27ab…3991, chrome.exe e409e52a…93fd).

• The toolkit's own test suite (node cli/test/run-tests.js --browser-dir <browser package> --playwright <playwright-core>) passed 38 checks against that browser: strict configuration and path rules (including a junction in the profile path, device names, UNC paths, and spaces, commas and CJK characters), unknown builds, headless and windowed launches, Playwright connectOverCDP through the control endpoint, capability, Origin and Host rejection, one controller at a time, idempotent retries including two simultaneous launches with one key, a second launch on a busy profile, a browser started outside dovra on the same folder, normal close, forced termination, an externally terminated browser (reported as crashed) and a lost supervisor process (reported as lost).
• The suite was also run from the extracted toolkit archive itself (same SHA-256 as the download), and dovra capabilities, launch with a start URL and close (clean exit, saved) were run against the extracted Dovra-Beta-20260924-win-x64.zip package layout.
• Closing an instance that crashed or was terminated is reported as CLOSED_UNSAVED rather than success.
• An independent review of the command line was performed before release (three rounds; the first found a blocking issue in how the command line authenticates to its per-instance supervisor, fixed before release).
• Not exercised: the startup-timeout path (the handshake completed in about half a second on the test machine), clean Windows 10/11 client machines, other Node.js versions.

Known limitation carried over from the browser: Playwright page.setContent() times out because this build does not report console events; use page.goto() or page.evaluate().

Use Dovra for your own applications, authorized tests and automation permitted by the service you access. See the use principles.

Dovra Beta — beta-20260924

Dovra Beta — beta-20260924

Free experimental Windows x64 portable build with an English interface. This is a Beta, not a stable release or a formal Dovra product version. The underlying Chromium technical version is 153.0.8010.48.

What changed since beta-20260923

• The package no longer contains the Microsoft SDK runtime files d3dcompiler_47.dll and dxil.dll, nor the DirectX Shader Compiler dxcompiler.dll that was built for them. WebGL uses the d3dcompiler_47.dll that ships with Windows 10 and later; WebGPU on Direct3D 12 is now built to compile shaders with FXC, so the adapter no longer reports the subgroups feature. There are therefore no Microsoft runtime terms to accept: dovra_browser.exe is a small entry point that only starts bin\chrome.exe with default arguments and shows no dialog, the toolkit performs no acceptance check, and MICROSOFT-RUNTIME-TERMS.md, the SDK licence copies and the runtime-terms manifest are no longer part of the package.
• The ungoogled-chromium first-run page (chrome://ungoogled-first-run) is no longer built in; a first start opens the new-tab page.
• Release files are distributed from https://dl.dovra.dev/beta-20260924/; the GitHub release entry carries links only.
• The Chromium engine (153.0.8010.48), the fingerprint patch set and the seed-derived variation module are unchanged from beta-20260923.

Downloads

• Dovra-Beta-20260924-win-x64.zip: complete browser, launcher and offline notices (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0).
• Dovra-Toolkit-beta-20260924.zip: optional companion toolkit; no browser included (SHA-256 962cbc37017ee815e82dfed8ef74d931729b26a4a97a87b657b3db0bfd0d6be0).
• SHA256SUMS.txt: SHA-256 checksums for all files of this batch.
• Component source, relinking and LGPL modification archives: listed in SOURCE-MATERIALS.md.

GitHub's automatic repository source ZIP/tarball contains repository files, not the compiled browser or the full Chromium source tree.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

Checks run on this batch

• Without a seed, the page-observable build features (tests/probe-dump.js, 70 groups) and the open-source FingerprintJS components (tests/probe-fpjs.js, 41 components) of the packaged runtime were compared item by item against the beta-20260923 binary; apart from the network downlink and RTT estimates, the only difference is the WebGPU adapter feature list, which no longer contains subgroups (FXC shader path).
• Graphics runtime without the Microsoft SDK files (tests/probe-gpu-runtime.js): the WebGL renderer string and the pixel hash of a 64×64 shader-drawn triangle are identical to beta-20260923 (the d3dcompiler_47.dll shipped with Windows is used); WebGPU adapter and device creation and a compute dispatch succeed without any command-line flag, with 16 adapter features (17 before).
• With --fingerprint=123456789 and --fingerprint=987654321 (tests/probe-seeded-noise.js) every recorded value equals the beta-20260923 run of the same seed, so the seed-derived variation of layout rectangles, text metrics and canvas readback is unchanged.
• First start (tests/probe-first-run.js and a direct start of bin\chrome.exe without arguments on a fresh profile): only the new-tab page opens; chrome://ungoogled-first-run is no longer a valid URL.
• dovra_browser.exe (thin entry point, 6,144 bytes): started from a three-file layout, it launched bin\chrome.exe with --fingerprint-brand=chrome, --lang=en-US and the default %LOCALAPPDATA%\Dovra\Beta\BrowserData profile, passed an explicit --user-data-dir and other arguments through unchanged, and exited immediately without showing a dialog.
• The post-release detection suite (tests/post-release.js, 55 signals, recommended profile) reported 33 passes on the packaged runtime and no newly failing item; every remaining item was already attributed on beta-20260923 (maxTouchPoints reported by the host machine; the Intl default locale following the en-US interface language of this package; host and site-side items tracked separately).

Carried over from the beta-20260916 build of the same engine

The following checks were performed on the beta-20260916 build (same engine and configuration; the Microsoft SDK runtime components present in that build are no longer shipped) and were not repeated for this batch. Accepted tests: English built-in pages and the engine version were checked; the version, Settings, credits and GPU pages were visually reviewed. Targeted checks covered eight credits entries with complete licence text and expanded display, Canvas output, a WebGL 2 draw/readback, short local PCM and FLAC playback, and test localStorage retained after a graceful close and reopen. These were browser checks, not a test of the packaged launcher or a clean-machine installation.

The tested CDP endpoint listened only on 127.0.0.1, rejected the tested foreign Host requests and foreign/null WebSocket Origin handshakes, and permitted the trusted local client. A foreign-Origin HTTP request returned 200 without an Access-Control-Allow-Origin response header; it was not rejected at the HTTP layer. Local programs can still control the browser through CDP. This is not authentication or protection from local malware.

The reviewed idle NetLog fields recorded WPAD activity and no external destination host. This finite observation is not a zero-network or zero-telemetry guarantee. WebGL success does not verify all WebGPU, GPU, codec or sandbox paths. Nonfatal SharedImageManager::ProduceSkia mailbox messages were observed; the sampled drawing and playback checks completed.

Signing status: dovra_browser.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned). A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use this build for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this candidate; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: dovra.dev@gmail.com

Dovra Beta — beta-20260923

Dovra Beta — beta-20260923

Free experimental Windows x64 portable build with an English interface. This is a Beta, not a stable release or a formal Dovra product version. The underlying Chromium technical version is 153.0.8010.48.

What changed since beta-20260916

• The seed-derived variation of canvas pixel readback, canvas text metrics and layout rectangles (--fingerprint=<seed>) was reimplemented in a single module written for this project, replacing the previously included Bromite-derived implementation. Without a seed these APIs return the unmodified Chromium values.
• The launcher is now dovra_browser.exe; the offline Microsoft runtime terms are shown again on first start.
• Files are distributed from https://dl.dovra.dev/beta-20260923/. This release entry carries no attachments.

Downloads

• Dovra-Beta-20260923-win-x64.zip: complete browser, launcher and offline notices (192205066 bytes, SHA-256 8e2027410718bf7eacf99b42a4e7519b59ca08d4d1e87b352ea1fd0a6bf30573).
• Dovra-Toolkit-beta-20260923.zip: optional companion toolkit; no browser included (SHA-256 18e8e6b3e88c88ce8f032d4528442c92a0024fa848cd099022f8372e4ffbf618).
• SHA256SUMS.txt: SHA-256 checksums for all files of this batch.
• Component source, relinking and LGPL modification archives: listed in SOURCE-MATERIALS.md.

GitHub's automatic repository source ZIP/tarball contains repository files, not the compiled browser or the full Chromium source tree.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

Checks run on this batch

• Without a seed, the page-observable build features (tests/probe-dump.js, 70 groups) and the open-source FingerprintJS components (tests/probe-fpjs.js, 41 components) of the packaged runtime were compared item by item against the beta-20260916 binary; only the network downlink estimate differed.
• With --fingerprint=123456789 and --fingerprint=987654321 (tests/probe-seeded-noise.js, two page loads per start): getBoundingClientRect() equals the union of getClientRects(); Element and Range rectangles carry the same factor; a same-origin iframe reports the same coordinates; values repeat exactly across reloads; the factor is within 1 ± 1e-4 and differs between the two seeds. measureText() width and actual bounding box carry one factor, fontBoundingBox* is unchanged, a Worker OffscreenCanvas returns the same width as the main thread, and the empty string measures 0. getImageData() of a region equals the same region of a full read, two toDataURL() calls are identical, decoding the PNG and reading it back differs only by single-unit steps in the perturbed channels, WebGL readPixels() is stable across two reads, and all readback values differ between the two seeds and from the no-seed run.
• --disable-spoofing=canvas removed only the canvas readback variation; --disable-spoofing=all reproduced the no-seed values exactly.
• The post-release detection suite (tests/post-release.js, 55 signals, recommended profile) reported 32 passes on the packaged runtime. Every remaining item was already attributed in earlier batches or reproduces identically on the beta-20260916 binary with the same profile (maxTouchPoints reported by the host machine; the Intl default locale following the en-US interface language of this package); none is introduced by this batch.

Carried over from the beta-20260916 build of the same engine

The following checks were performed on the beta-20260916 build (same engine, configuration and component set) and were not repeated for this batch. Accepted tests: English built-in pages and the engine version were checked; the version, Settings, credits and GPU pages were visually reviewed. Targeted checks covered eight credits entries with complete licence text and expanded display, Canvas output, a WebGL 2 draw/readback, short local PCM and FLAC playback, and test localStorage retained after a graceful close and reopen. These were browser checks, not a test of the packaged launcher's first-use terms dialog or a clean-machine installation.

The tested CDP endpoint listened only on 127.0.0.1, rejected the tested foreign Host requests and foreign/null WebSocket Origin handshakes, and permitted the trusted local client. A foreign-Origin HTTP request returned 200 without an Access-Control-Allow-Origin response header; it was not rejected at the HTTP layer. Local programs can still control the browser through CDP. This is not authentication or protection from local malware.

The reviewed idle NetLog fields recorded WPAD activity and no external destination host. This finite observation is not a zero-network or zero-telemetry guarantee. WebGL success does not verify all WebGPU, DXIL, GPU, codec or sandbox paths. Nonfatal SharedImageManager::ProduceSkia mailbox messages were observed; the sampled drawing and playback checks completed.

Signing status: dovra_browser.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned). A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use this build for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this candidate; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: dovra.dev@gmail.com

Dovra Beta — beta-20260916

Dovra Beta — beta-20260916

Free experimental Windows x64 portable build with an English interface. This is a Beta, not a stable release or a formal Dovra product version. The underlying Chromium technical version is 153.0.8010.48.

Superseded — files no longer hosted

This batch has been retired. Its attachments (the browser package, the companion toolkit, the component source archives and the relinking archives) are no longer hosted here.

For the current release see https://github.com/dovra-dev/DovraBrowser/releases/latest ; downloads are served from https://dl.dovra.dev/ .

The notes below are kept as a record of what this batch was and how it was verified.

Verified scope

Tested environment: Windows Server 2022 x64, OS build 20348.5139; NVIDIA GeForce GTX 650 / ANGLE Direct3D 11.

Accepted tests: English built-in pages and the engine version were checked; the version, Settings, credits and GPU pages were visually reviewed. Targeted checks covered eight credits entries with complete licence text and expanded display, Canvas output, a WebGL 2 draw/readback, short local PCM and FLAC playback, and test localStorage retained after a graceful close and reopen. These were browser checks, not a test of the packaged launcher's first-use terms dialog or a clean-machine installation.

The tested CDP endpoint listened only on 127.0.0.1, rejected the tested foreign Host requests and foreign/null WebSocket Origin handshakes, and permitted the trusted local client. A foreign-Origin HTTP request returned 200 without an Access-Control-Allow-Origin response header; it was not rejected at the HTTP layer. Local programs can still control the browser through CDP. This is not authentication or protection from local malware.

The reviewed idle NetLog fields recorded WPAD activity and no external destination host. This finite observation is not a zero-network or zero-telemetry guarantee. WebGL success does not verify all WebGPU, DXIL, GPU, codec or sandbox paths. Nonfatal SharedImageManager::ProduceSkia mailbox messages were observed; the sampled drawing and playback checks completed.

Signing status: Start-Dovra.exe, bin/chrome.exe and bin/chrome.dll are unsigned (NotSigned). A checksum identifies bytes; it is not a trusted publisher signature.

The test scope is finite. Windows 10/11 client systems, a standard-user installation, every GPU, every media format and every website are not claimed to have been tested. Site compatibility, preserved login state and uninterrupted operation are not guaranteed.

Use and limitations

Use this build for lawful workflows and authorized testing. Keep backups and a separate browser for important browsing. Configurable browser parameters do not grant access or guarantee anonymity.

The build does not provide a Dovra automatic updater. Google Safe Browsing is disabled in this candidate; do not rely on it for remote phishing or malware checks. The privacy notice explains the reviewed background-service settings and their limits. No universal zero-network or zero-telemetry guarantee is made.

Read the offline terms when starting the package. Project terms do not replace component licences or remove applicable open-source modification and relinking rights. The companion toolkit has a separate MIT licensing scope.

Project: https://dovra.dev/ · Support: dovra.dev@gmail.com