What BehindGate is, and the core concepts: workspaces, sites, apps, and releases.

What BehindGate is

BehindGate hosts your static sites and puts them behind your workforce identity, so only the people you allow can reach them. New sites are private by default, and you control who signs in.

Core concepts

These four nouns describe how everything in BehindGate fits together.

Workspace

A workspace holds your sites, apps, and team. It is the top-level container for everything you manage in the dashboard. When you create one, you give it a name (for example, Acme); the name is the display name shown across the dashboard.

Site

A site is one hosted property with a single address and its own sign-in rules. Each site has:

• An address — a BehindGate subdomain, reachable instantly and secured automatically. (Custom domains are not yet available.)
• A sign-in method — an email allowlist (any of a set of allowed domains and/or individual addresses) or single sign-on (SSO). A site stays private until sign-in is configured.
• Apps mounted at paths under it.

By default, every app on a site is gated. A separate per-site setting, Allow public apps, controls whether any app on the site may be made reachable without sign-in. It is off by default as a safeguard.

App

An app is a static site mounted at a path under a site. Each app has a path prefix — for example, / for the root app, or /admin for another. Multiple apps can live on one site at different paths.

An app is private unless you make it public, and an app can only be made public when the site allows it. Until you publish a release, an app responds with a Not Found page.

Release

A release is a single uploaded build of an app's content. You create a release by uploading a built static-site folder or a .zip (the contents of your dist/ folder), then publish it to make it live. Each app keeps a history of releases, so you can publish a new one or roll back to the previous one.

Next steps

• Create a site — name your site, choose its address, set up sign-in, and optionally deploy the root app.
• Deploy with the CLI — upload and publish a release for an app.