Versioned site artifacts passing through a release gate to an edge publishing relay

EVS Sitesproduct preview

Publish agent output as a governed site.

Sites turns browser-ready agent output into a private URL with immutable versions and rollback. Later phases attach provenance, access policy, traces, and scoped calls back into Everstack.

Join the Sites previewSee the rollout
  • Static first
  • Private first
  • Immutable versions
  • Runtime routes planned
Sites5 sites
quarterly-reviewv12
support-handbookv7
pipeline-dashboardv31
migration-reportv3

quarterly-review.evs.run

ActiveStatic routingIndexable

Live version

v12

Files

148

Storage

6.2 MB

Published

4m ago

Phased rollout

Ship the publishing contract before expanding the runtime.

Each phase has a clear boundary. Static delivery works without an application process. Governance belongs in the Everstack control plane. Runtime calls arrive only when they can be scoped, authenticated, and traced end to end.

01In development

Static serving foundation

Turn browser-ready output into a private, versioned surface without pretending a server process exists.

  • Tenant-scoped blobs
  • Immutable manifests
  • Private preview links
  • Activation + rollback
02Next

Governed agent surfaces

Carry the source task, owner, access policy, approval state, retention, and audit history with the URL.

  • Everstack identity
  • Task provenance
  • Access policies
  • Audit + retention
03Planned

Scoped runtime routes

Let an approved frontend route call one Everstack agent or function without turning the static plane into a general runtime.

  • Scoped /api routes
  • Agent + function targets
  • End-to-end traces
  • BYOC serving adapter

Phase one contract

One contract. Four explicit transitions.

The foundation is intentionally small: hash files, seal a manifest, verify its blobs, then activate one version. Every transition is recoverable, and none requires an application runtime.

hash

Address every file by content

Tenant-scoped hashes make unchanged assets reusable without making one tenant's files visible to another.

manifest

Seal an immutable version

Paths, content types, sizes, hashes, the entrypoint, and SPA behaviour are explicit and validated.

verify

Refuse incomplete publishes

A version cannot activate until every referenced blob exists and matches the manifest's declared size.

activate

Move one route, or move it back

Activation points the hostname at one sealed version. Rollback is the same operation with an older version.

Where Sites fits

A governed publishing surface for agent-created work.

General web platforms remain the right choice for broad application hosting. Sites is for browser-ready output whose source task, version, access policy, and optional route back into Everstack need to remain connected.

Use Cloudflare

You are deploying a web application.

Choose the broad platform when you need CDN, edge compute, DNS, security, storage, and a general runtime you will operate directly.

Use EVS Sites

An agent produced a surface that must stay governed.

The target experience keeps the source task, owner, access policy, version, audit trail, and an optional scoped route back to Everstack together.

Questions

The short version, before you commit.

These product surfaces are intentionally direct: a small source model, an observable execution path, and infrastructure boundaries you can explain.

What exists today?

EVS Sites is a product preview, not a generally available hosting service. The phase-one publishing foundation is in development: content-addressed assets, immutable manifests, private preview access, activation, and rollback.

What will phase one publish?

Browser-ready output only: static sites, single-page apps, reports, dashboards, documents, and other files an agent has already built. It will not execute server bundles or provide SSR.

Does it require a particular agent framework?

No. The intended contract is an HTTP API plus an agent skill, so Codex, Claude Code, Cursor, CI jobs, or any harness capable of HTTP requests can use it.

Is EVS Sites another Cloudflare?

No. Cloudflare is a broad web platform and remains the better choice for general websites, CDN, and edge compute. Sites is being built for agent-created surfaces that need provenance, governed access, traces, and a scoped path back into an Everstack runtime.

Where does the Everstack runtime fit?

It does not sit in the static serving path. A later phase will let approved routes call an Everstack agent or function with the site's identity, policy, and trace context attached.