DOS Browser vs dosbox-automation
DOS Browser
dos.zonedosbox-automation
dosbox-automation.orgSide by side
| Figure | DOS Browser | dosbox-automation |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Android | Yes | — |
| API | — | Yes |
| Plans published | 2 | 0 |
| Spec score · MS-DOS Emulators | 8.0 (#7) | 7.9 (#10) |
| Purpose | DOS Browser is a browser with hardware acceleration for DOS games. | dosbox-automation is a DOSBox Staging fork that lets launchers, test harnesses, and scripts launch, drive, and inspect DOS applications and games. |
Plans
In their own words
dosbox-automation
dosbox-automation is a free DOSBox Staging fork for automating the launch, control, and inspection of DOS applications and games. Its HTTP REST API uses bearer-token authentication and includes Swagger UI, while a sandboxed Lua engine can drive execution and input with frame-accurate timing. It can record and replay keyboard and mouse input, capture frames and video, read text in text modes, and inspect memory and CPU registers. TOML recipes can automate installations, including disk swaps, through the API and Lua engine. The project includes DOSBox Staging functionality, added fixes and hardening, and a FluidR3 General MIDI soundfont enabled by default. Official builds are available for Windows and Linux; the Linux build is statically linked and targets x86_64. There are no official macOS builds, and compiling from source is described as untested. The webserver is disabled by default. When enabled, it binds to localhost by default, requires a bearer token, restricts mounted paths, and runs Lua without filesystem or process access. Windows 9x is not supported.