> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wazoo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Self-host

> Host Worlds locally or via Docker

Worlds self-hosting is available through the respective GitHub repositories. Use
the repository README and package docs for the component you are deploying. For
how hosted Worlds work, see [Worlds](/worlds/index).

## Current status

Self-hosting is not part of the private beta. The supported path depends on
which Worlds components you run:

* [`worlds-api`](https://github.com/wazootech/worlds-api): the self-hostable
  Worlds data-plane service (search, SPARQL, import, export).
* [`worlds-sdk-ts`](https://github.com/wazootech/worlds-sdk-ts): local and
  embedded Worlds SDK usage.
* [`worlds-client-ts`](https://github.com/wazootech/worlds-client-ts): generated
  data-plane HTTP client for the hosted or self-hosted Worlds API.
* [`worlds-libsql`](https://github.com/wazootech/worlds-libsql): durable
  SQLite-compatible storage through LibSQL/Turso-style backends.
* [`worlds-postgres`](https://github.com/wazootech/worlds-postgres): durable
  PostgreSQL-backed storage.

Private networking patterns such as Docker Compose, Tailscale, or Cloudflare
Tunnel depend on your deployment environment and should be configured alongside
the repository-specific setup.

## Deployment responsibilities

When you self-host, you own:

* Worlds data services and storage.
* Network ingress and access control.
* Token issuance and rotation.
* Backups, monitoring, and incident response.

Do not assume a compliance posture from these docs alone. Treat each self-hosted
deployment as an architecture review for your environment.