Concepts¶
Tenancy¶
Every account is an isolated tenant. The system scopes all resources (computers, services, containers, databases, static apps, API keys) to the owning user. Every API query filters by that owner. A tenant cannot access another tenant's resources.
Computers (runners / nodes)¶
A computer is a machine you have enrolled. The runner agent on it dials out to the control plane over an authenticated WebSocket tunnel. The host needs no inbound connectivity. A computer reports its OS/CPU/RAM. It advertises the apps it is serving. It streams logs back.
- Status starts
pending. It becomesconnectedon the first heartbeat. - Capabilities declare what a computer may host (static apps, services, containers, databases — with optional per-type limits).
- You can enable terminal access per-node (an authenticated web shell).
Pools¶
A pool is a named group of computers. Pools are an organizational grouping today. Workload placement is by explicit computer selection. A resource runs on the node assigned to it.
Regions¶
A computer can report a region (e.g. af-south-1). Regions are metadata
for grouping and display.
Workload types¶
| Type | What it is | Reached via |
|---|---|---|
| Static app | A zip of static files, served by the runner | HTTP proxy (subdomain) |
| Service | A long-running container image | HTTP proxy (subdomain) |
| Container | A standalone container on a port | HTTP proxy (subdomain) |
| Database | Managed Postgres/MySQL/Redis | Database proxy (standard port) |
Public host format¶
Hosted apps use this address:
<slug>.althostproxy.com
e.g. blog-a1b2c3.althostproxy.com
The slug is auto-generated and immutable. The tunnel resolves the slug to the runner that serves the app. See Architecture.