---
title: Sites and deploys
description: Understand site identity, deploy history, runtime access, templates, quotas, and usage.
audience: everyone
status: current
last_updated: 2026-09-02
order: 10
related:
  - /v/docs/getting-started/quickstart.md
  - /v/docs/ui/building-an-image.md
---

A site is the durable product record at the center of Olibato. Deploys may
replace its active application version, and its runtime may sleep or move, while
the site slug and permanent host remain unchanged.

## Site, slug, and namespace

Each account chooses a personal namespace during signup. Organizations use their
organization slug as a namespace. A site has a unique slug within its namespace:

```text
<site>.<namespace>.serverl3ss.com
```

For example, site `web1` in namespace `mike` is
`web1.mike.serverl3ss.com`. The namespace and site slug are immutable DNS
identities. A site name is display text and may change. Custom domains are
additional verified hosts for the same site.

## Deploys and versions

A deploy combines a source input with a validated `deploy.yaml` manifest. Source
may be a container image, connected GitHub repository, committed local archive,
or app template. Build events and evidence belong to that deploy.

A successful deploy produces an immutable version. The site points at one active
version, so a later deploy can change application code or topology without
creating a new site. The isolated runtime uses that version and retains its own
writable state. Suspending, waking, restarting, or moving the runtime does not
change the permanent host.

## App templates

App templates are supported recipes for common open-source services. Each
template declares its parameters, license, source image, service topology, and
default access. Installing one renders a manifest and sends it through the same
validation, security, deploy, and version process as other sources. Templates do
not bypass runtime isolation or quota checks.

## Access control

HTTP sites are either **public** or **authenticated**. Authenticated access is
enforced before a sleeping workload wakes. Private TCP services use temporary,
source-IP grants with explicit expiry; application-level database credentials
still apply.

Custom domains inherit the site's access setting. Olibato verifies ownership and
traffic DNS before routing a custom hostname and periodically checks ownership
while it remains active.

## Quotas and usage

Quotas bound sites, custom domains, services, compute, memory, retained storage,
and monthly wake time for a namespace. Creating a site or starting a deploy may
be rejected before work begins when a hard limit is reached.

Usage is measured per site and rolled up to the namespace. The dashboard and API
report request count, wake minutes, and retained storage for the current period.
Usage records are append-only, so deleting a site does not erase its audit trail.