# Deploy aardvark

`vark build` writes a plain static site to `build/` — no server required. Host that
directory on any static host, or run it yourself with the bundled `vark serve`. This section
collects everything about shipping aardvark to production.




Install the CLI first — see [Installation](/getting-started/installation/) — then come back to ship what you've built.






Hand the static `build/` directory to any host — Cloudflare Pages, Netlify, Vercel, GitHub Pages, S3 — or ship aardvark itself as one compiled binary.




`build`, `dev`, `serve`, `link-check`, and the rest — and the exact flags each command takes.




`sitemap.xml`, `robots.txt`, `_redirects`, `_headers`, per-page Markdown, the search index, and the whole-site PDF.



## Run a live server

Need an origin process — for the MCP endpoint, `Accept: text/markdown` negotiation, or a
CDN to sit in front of? That's `vark serve`. It lives under **AI Features** because the
same process also exposes your docs to agents over MCP.



The hardened `vark serve` process — static plus a live MCP server — packaged as a Docker image behind a CDN. Documented under [AI Features](/ai/).