Field notes / Architecture

Two workloads.
Two simple homes.

October 21, 2026 · VaneDeploy editorial

Deployment guides and an AI search engine have different needs. A guide can be served as an HTML file. A search instance needs a running application, persistent data, and access to search and model services.

The content layer

VaneDeploy builds plain HTML, CSS, and JavaScript. Cloudflare Pages can serve those files. The configuration builder runs in the visitor’s browser; generating a Compose file does not call a model.

The application layer

The Vane container runs on your server with a data volume. A reverse proxy terminates HTTPS and forwards requests to its local port. Keeping this service separate means content deployments do not restart the search application.

The boundary matters

The demo page links to or embeds the application. It is not an authentication layer, a billing limit, or a privacy boundary. Apply those controls at the application host before enabling the embed.

Start without the extra parts

Launch useful documentation first. Add a private instance, test a complete search, and measure resource use. Only then decide whether to offer a public demo and how to limit it.

Cloudflare static-site deployment reference ↗