---
title: The public site, downloads and docs routes
description: What the public pages of Venom Cloud serve without a sign-in - the site, stable download links, the cloud status page and the docs in HTML, markdown and llms.txt.
section: cloud
order: 92
audience: [user, agent, builder]
sources: [services/nodejs-cloud/app/(marketing), services/nodejs-cloud/app/download, services/nodejs-cloud/app/docs, "services/nodejs-cloud/app/docs-md/[...path]/route.ts", services/nodejs-cloud/lib/cli-release.ts, services/nodejs-cloud/lib/daemon-release.ts, services/nodejs-cloud/lib/latest-release.ts]
features: [cloud.site, cloud.download, cloud.docs, cloud.docs-md, cloud.page-docs]
---

Besides the console and the API, a Venom Cloud deployment serves a small public site. None of these pages needs a sign-in, none sets a tracking cookie or loads a third-party script, and the download links log nothing.

## Site pages {#site}

| Path | What |
|---|---|
| `/` | The home page: the position in one line, the four ways in, every product, and short sections on sovereignty and the mesh. |
| `/workspace` | For teams replacing per-seat tools: every workspace product, what each replaces, and pricing per organisation. |
| `/sovereign` | For teams that need their data on their side: self-hosting, your cloud, air-gapped, and the security of Venom Cloud. `/security` redirects here. |
| `/mesh` | For teams running their own models: one endpoint over your GPUs and providers, routing, logs and the venom CLI. |
| `/host` | For people with spare GPUs: hosting on the public mesh, its checks, and how credits are counted (payouts are not built yet). |
| `/pricing` | Plans, what each of the four audiences pays for, and what each plan includes. |
| `/compare` | The workspace next to the tools it replaces, then Venom next to Claude Code, Qwen Code, and Ollama or vLLM run alone, with measured speedups; every number has a footnote. |
| `/cli` | The venom CLI: install commands and a download per platform. |
| `/daemon` | The desktop daemon: downloads per platform, including the macOS app. |
| `/router` | How routing works in the orchestrator and in Venom Cloud, with the algorithms and measured numbers. |
| `/status` | The cloud's own status from its request log: availability and p50 latency of the API, the router, daemons and each provider over 24 hours and 7 days, and the live daemon count. Aggregates only, cached five minutes. |
| `/privacy`, `/terms` | Legal pages. |
| `/sitemap.xml` | The site's pages for search engines; the docs have their own at `/docs/sitemap.xml`. |

An organisation's own public status page is `/status/{slug}`; see [Settings](/docs/cloud/console-settings.md#status-page).

## Download links {#downloads}

Stable links that always point at the release the site offers: the newest published release on the public releases repository, never below the version the deployment was built with.

| Path | Redirects to |
|---|---|
| `/download/{platform}` | The venom CLI archive for a platform: `macos-arm64`, `macos-x64`, `linux-x64`, `linux-arm64`, `windows-x64` (beta). |
| `/download/sha256sums` | The CLI release's `SHA256SUMS`. |
| `/download/daemon/{platform}` | The daemon archive for the same platform ids, or the macOS app zip: `macos-arm64-app`, `macos-x64-app`. |
| `/download/daemon/sha256sums` | The daemon release's `SHA256SUMS`. |

Each answers `302` with a five-minute cache; an unknown name answers `404` in plain text. Check what you download:

```bash
curl -fsSLO https://cloud.usevenom.dev/download/linux-x64
curl -fsSL https://cloud.usevenom.dev/download/sha256sums -o SHA256SUMS
```

The newest release is found by reading the redirect of the releases repository's "latest" page (no API token), cached five minutes per instance with a two-second timeout; if that fails the built-in version is used. Outside production (`next dev`, tests) only the built-in version is used, so a local cloud makes no call for it.

## Docs routes {#docs}

These docs are built from markdown at deploy time and served by the cloud.

| Path | What |
|---|---|
| `/docs` | Every section. |
| `/docs/{section}` | A section's overview. |
| `/docs/{section}/{slug}` | One page. |
| `/docs/{section}.md`, `/docs/{section}/{slug}.md` | The page's markdown with frontmatter, links made absolute. Served from the internal `/docs-md` route, which is not public under its own path. |
| `/docs/llms.txt` | The [llmstxt.org](https://llmstxt.org) index: one line per page with its markdown URL and description, by section. |
| `/docs/llms-full.txt` | Every page's markdown in reading order. |
| `/docs/search.json` | The index the search box reads in your browser; no search service is called. |
| `/docs/sitemap.xml` | Every docs URL. |
| `/docs/api/*` | The generated API references. |

For an agent, fetch the index and then the pages it needs as markdown:

```bash
curl -s https://cloud.usevenom.dev/docs/llms.txt
curl -s https://cloud.usevenom.dev/docs/cloud/console-settings.md
```

All of these are static: they are prerendered at build time, and any other path under them is a 404.

## Related

- [Install venom](/docs/getting-started/install.md) for the install script that uses these downloads.
- [Self-hosting Venom Cloud](/docs/cloud/self-hosting.md): the same site is served by your own deployment.
