The alpha you can run today

The first RenderCache alpha is available as a Linux amd64 archive with SHA-256 checksums and matching engine source. It keeps the runtime small in one specific sense: one Go service executable manages the reverse proxy, disk store, warm queue, receipts and protected admin app. Chrome is still a separate process and dependency. The Dockerfile installs Chromium for container deployments.

The release pipeline checked the actual rendering path, rather than stopping at compilation. Race-enabled tests use real Chrome. The container check warms a page under a non-root user with restricted resources and filesystems, using an explicit sandbox opt-out inside an isolated test network. The nginx example is exercised against the executable, and the archive is rebuilt deterministically before its extracted binary is tested.

Those checks establish a starting point for evaluation. They do not establish production readiness or prove Chrome’s sandbox works on every host. The alpha supports one process per local data directory, uses in-memory queue state, provides explicit quota rejection and offline prune, and leaves browser memory and process enforcement to the operating environment.

The engine is Apache 2.0. Download the verified alpha, run a public page through it, and use the issue tracker to report reproducible findings without private content or credentials.