Ambient website
The public marketing site for Ambient,
the open-source video engine for AI agents. Deployed to GitHub Pages.
site/ Astro site — landing + blog + docs (served at /)
replay/ Read-only "Replay Gallery" — animated playback of real Ambient
sessions, styled like the Studio console (served at /replay/)
install/ The one-line installer, published at /install.sh
Develop
# Landing + blog + docs
cd site && npm install && npm run dev
# Replay gallery (the "Watch it work" demos)
cd replay && npm install && npm run dev
Deploy
.github/workflows/pages.yml builds site/, builds replay/, folds
replay/dist into site/dist/replay/, copies install/install.sh, and
publishes site/dist to GitHub Pages on every push to main.
One-time setup
- Repo → Settings → Pages → Source = GitHub Actions.
- Repo variables (Settings → Secrets and variables → Actions → Variables),
all optional:
REPLAY_MEDIA_BASE — the R2 bucket's public base (r2.dev URL or custom
domain) so replay media + artifacts resolve durably. Without it, the replay
falls back to the 7-day presigned URLs baked into the fixtures (preview only).BASE_PATH — set to /<repo> only if serving as a project page at
<org>.github.io/<repo>/. Leave unset for an apex domain or an org
*.github.io page (defaults to /).SITE_URL — canonical URL for RSS/OG (defaults to the proposed domain).
- Custom domain (when registered): set the repo variable
SITE_DOMAIN
(e.g. goambient.ai) — the workflow writes the CNAME automatically. Then
point DNS at GitHub Pages (apex A/AAAA + www CNAME → the org's
github.io) and enable Enforce HTTPS. Until then, the site serves on the
default *.github.io URL.
Replay fixtures
The replay fixtures (replay/src/fixtures/*.json) are generated by
scripts/capture_replay.py in the engine repo (it needs ambient.utils.s3).
To refresh or add a demo, run it there pointed at this repo:
# in the ambient engine repo, with the local engine running on :8080
REPLAY_FIXTURE_DIR=/path/to/ambient-website/replay/src/fixtures \
uv run python scripts/capture_replay.py --no-source
