BCS-2 vs scanservjs
BCS-2
imageware.descanservjs
github.comSide by side
| Figure | BCS-2 | scanservjs |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Document Scanning Software | 7.8 (#11) | 7.6 (#17) |
| Integrations | The software supports scanners with a suitable 64-bit TWAIN driver and offers selected scanner and digital-camera integrations. | Files can be handled through filesystem scripts or custom actions; the integration guide mentions paperless-ng and Dropbox examples. |
| Purpose | BCS-2 is professional scanning and workflow software for digitising documents, books, records and other source materials. | scanservjs is a web interface for sharing one or more SANE scanners on a network. |
| Support | For customers with a maintenance and support package, the hotline is available on weekdays from 9:00 to 17:00; the maker also accepts support requests by email. | The maker's documentation links to troubleshooting guidance and invites community help with translations. |
Plans
In their own words
scanservjs
scanservjs lets people access and share SANE-compatible scanners over a network through a web browser. Its controls cover source selection, cropping, resolution, filters and configurable defaults. Scans can be saved as TIF, JPG, PNG, PDF or TXT, with Tesseract OCR for text output. It handles multipage jobs and collation for double-sided scans; batches can run through a document feeder or pause for manual page changes.
The software is free and open source. It requires SANE and a Linux host or virtual machine, with installation documentation for Debian, Arch and Docker. Docker images are listed for amd64, arm64 and armv7. An API explorer and OpenAPI documentation are available at /api-docs. Scanned files are saved in a flat directory for download, and Docker deployments need a mapped volume to retain files when a container is recreated. Filesystem scripts and custom actions can support other workflows, while custom naming, folder structures and cloud or NAS storage are left to users.