-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Ship a working tool as a single HTML file. No server, no install, no network.
openToolbox is a template for small internal tools that need to travel — by email, USB stick or shared drive — and run by double-click on a locked-down corporate laptop. The file is the application and the database at the same time. Saving writes a new HTML file with the data embedded in it.
It's built for one workflow in particular:
"Build me a tool for tracking supplier audits, based on openToolbox."
Point an AI assistant at the repository and it has
everything it needs — the framework, and AGENTS.md telling it exactly what to ask and which file
to change.
Single file · database in the file · optional AES-256-GCM encryption · optional AI assistant · brandable (colours, logo, name) · bilingual interface (English, German) · light & dark mode.
| Page | What's in it |
|---|---|
| Getting Started | Clone, build, open — the whole workflow in five minutes |
| Building Your Own Tool | The SCHEMA shape in src/domain.js, worked example, what an AI assistant needs to know |
| Architecture | Project layout, how the file-as-database persistence works, the build pipeline |
| AI Assistant | Dialect negotiation, context modes, how proposed changes are validated and applied |
| Interface Languages | The English/German toggle, and how to add a third language |
| Branding | Colours, logo, product name, the SVG sanitiser, exporting a configuration |
| Security and Encryption | AES-256-GCM details, what encryption does and doesn't protect |
| Testing | What the smoke test actually exercises, how to extend it |
| Limits and Troubleshooting | What this is not, and the failure modes worth knowing before they surprise you |
| Contributing | Ground rules for changes, what needs a test, how to report a problem |
Three constraints that keep coming up in regulated and corporate environments:
- Hosting a small tool means a server, a URL, an operations owner and usually a security review.
- Installing anything requires admin rights the user does not have.
- The data must not leave the machine.
A single HTML file sidesteps all three. It's also honest about what it is: the user can read the entire source, and there is no service that can quietly change under them.
Apache License 2.0. Source files carry an SPDX-License-Identifier header. Dependencies: Preact
(MIT), Vite (MIT), Playwright for tests only (Apache 2.0). The built file loads nothing at runtime.