Skip to main content
By the end of this page you will know who is involved when someone uses an app built on gavAI, what happens between a browser request and a rendered page, and how to read every other section of the docs as capability-first — what the platform does — rather than vendor-first. Treat this as the orientation page for the rest of the concept docs.

​
The three parties

Every interaction on gavAI involves three distinct parties. Confusing them is the most common source of misreadings in the rest of the docs. The crucial point: end-users never see gavAI. The platform is invisible to them by design. A workspace owner’s domain, branding, and identity are what the end-user experiences. gavAI sits behind it.

​
One request, start to finish

When an end-user visits a workspace’s domain — say, shop.acmebakery.com — six things happen. The path is the same for every request. The numbered version: The page body is never logged. Our metrics only carry request counts, timings, and error codes — never the content of what was rendered.

​
The publish path runs in parallel

While end-users are reading pages, the workspace owner is editing them. Their path is shorter: Two paths, one storage record per page. The architecture is symmetric on read and write.

​
Same content, three views

A useful mental check for how the isolation works: take a single piece of content — Acme’s homepage headline, “Fresh bread, daily.” — and look at how each party experiences it. The same piece of content. Three shapes. Operators see metadata — size, timestamp, hash — not bodies for ad-hoc reads. See Multi-tenant isolation for the architectural guarantees that back this.

​
We describe roles, not vendors

The platform exposes a fixed set of architectural roles: edge runtime, object storage, primary database, end-user identity, transactional email, payments, secret store, AI gateway, and so on. Each role is a stable contract. The vendor that fills a role today is an implementation choice. This matters for two reasons: If we swap a vendor, you get a 30-day notice and a right to object before the change goes live. The current list of vendors is published at Subprocessors.

​
What gavAI never does

A short, exhaustive list — these are commitments, not aspirations: See Multi-tenant isolation for the technical details and Scopes for the access boundaries.

​
Where to go next