Deploy to your cloud

Don't rent a cloud. Loam it. Loams runs in an account you own: your laptop, your homelab, or a VM in your own cloud. Ostrium runs no data plane, and the engine is never on the public internet.

This section says what works today, in 0.1.1, on each cloud, and labels the rest. Everything here is the same release: the compose bundle attached to the v0.1.1 GitHub release, its images on ghcr.io/ostrium-labs, and your own Tailscale tailnet as the only way in.

What works todayCopy Anchor Link

One Linux VM running the compose stack. That is the only install path in 0.1.1, on every cloud. The VM runs the light default stack, and the engine can keep its data in that cloud's object store. The stack and the tailnet are covered in Self-hosting over Tailscale; the pages below add what is specific to each cloud.

Every "today" cell is Available in 0.1.1, as one node with the limits below; every "planned" cell is designed and not built. Vercel never hosts the data plane: it runs apps and agents, and the engine runs on one of the other clouds or your own machine.

The stack on one VMCopy Anchor Link

docker compose up -d in the bundle's release/ directory starts the light default:

• the engine (loams) on its embedded stores: the metastore on openraft and redb, Loams Live on redb, Durable on SQLite, Git and Graph, with the bucket a local folder unless you point LOAMS_BUCKET at an object store;
• Loams House, linked to the engine;
• Loams Postgres: its storage broker, pageserver, safekeeper and one compute, with their remote storage in local folders;
• agentd, the agent daemon;
• the tailscale sidecar, the stack's only door.

Loams House runs on chDB today. It is ClickHouse-compatible analytics on chDB, the embedded ClickHouse library, inside the loams-fabric image, and it is experimental. A Rust engine of our own for the House is designed (design 75) but not built.

It needs about 10 GB of free disk and 2 GB of free memory, and it idles near 1 GB, measured on 0.1.0's images. Profiles add more, set in .env as COMPOSE_PROFILES before the first start:

A stack's data stays on the stores it started on: the engine refuses to switch stores on existing data. Choose the profiles on the first start.

VM sizesCopy Anchor Link

The default fits a small VM. Leave room for the operating system on top of the stack's 2 GB.

The cost calculator prices these sizes side by side on each cloud, with the bucket, requests and egress. Loams itself is free.

Use Ubuntu 24.04 LTS on x86-64. Two reasons:

• The House's workers need Landlock with TCP rules, from Linux 6.7, and refuse to boot without it. Ubuntu 24.04 ships a 6.8 kernel. Distributions on 6.1, such as Debian 12 and Amazon Linux 2023's default kernel, are too old for the House (verify for your image).
• The loams, loams-fabric, loams-agentd and loams-pg-control images are built for amd64 and arm64, but the patched TiDB image is amd64 only, and the pinned Loams Postgres images on arm64 are not yet confirmed. x86-64 avoids both.

Never publicCopy Anchor Link

No step in this section opens a port to the internet.

• People reach the engine over your tailnet, at https://loams.<tailnet>.ts.net, through the stack's tailscale sidecar. The VM needs outbound internet only.
• Shell access goes through the cloud's own console or identity-aware tunnel, or over the tailnet once the VM is on it. Create every VM with no inbound firewall rules.
• Machines on the tailnet, such as CI runners, use an API key (LOAMS_AUTH_MODE=tailscale,apikey), because Tailscale gives no user identity for tagged devices.
• Callers off the tailnet, such as a serverless function, have no supported path in 0.1.1. The gateway's edge listener, reached over a private link or Cloudflare Tunnel with every request authenticated first, is Planned (design 69).

The consoleCopy Anchor Link

IdentityCopy Anchor Link

UpgradesCopy Anchor Link

0.1.1 changes the default stack; reinstall. A 0.1.1 stack starts from the 0.1.1 bundle with a fresh .env. A 0.1.0 stack keeps its data only if you add COMPOSE_PROFILES=tikv,rustfs to its .env before upgrading, because 0.1.0 ran on TiKV and RustFS.

From then on, loams upgrade upgrades a stack with the tikv profile in place, with a snapshot first. It refuses a stack on the default embedded stores for now; upgrade one of those by hand: back up the volumes, docker compose stop, set LOAMS_VERSION in .env, then docker compose up -d. See upgrades.

What is plannedCopy Anchor Link

These are designed and approved, not built. None of them ships in 0.1.1.

Design 78 sets the order the deploy targets arrive in: TiDB X for development state, then Cloudflare, Vercel, AWS, Google Cloud and Azure, with AWS, Google Cloud and Azure as the production targets. The plan says production goes into your company's own cloud account, and development runs on your own devices.