Deployment
Lookout sites are static bundles with no server-side runtime required, so deploying it is straightforward and fits into whatever deployment architecture your organization already uses.
Hosting the bundle
Because there’s no backend to run, you have a lot of flexibility in where the site lives:
- A lightweight web server like nginx, serving the bundle directly from disk
- Object storage + CDN (S3/CloudFront, GCS, Azure Blob)
- Static hosting platforms like GitHub Pages
- Your existing internal web infrastructure
Access control
Access is controlled at the infrastructure layer, however your organization handles this:
- Login-protected: put it behind your existing auth layer, such as a reverse proxy with basic auth, an SSO/OAuth gateway, or an identity-aware proxy (e.g. Cloudflare Access, Google IAP). Contact us at lookout@fathom.info if you had any trouble setting up your Lookout site with authentication.
- Network-restricted: limit access via VPN or IP allowlisting if the content shouldn’t leave your network at all.
Because the output is just static files, deployment usually reduces to a single step in your existing pipeline: build the bundle, then sync or copy it to your hosting target (e.g. aws s3 sync, rsync, or a platform-specific deploy CLI). This makes it easy to trigger deploys automatically on merge, on a schedule, or as part of a broader release process.