boatramp

pre-1.0 · come crew it early

Launch the web from
your own shore.

One Rust binary is your web server, publishing API, and CLI. Publish static sites and functions to your own hardware, cloud, or edge — deploys are atomic and content-addressed, and every byte streams.

Read the docs View on GitHub
curl -sSf boatramp.dev/launch | sh

served by boatramp deploy 4f7943f · streaming-first · atomic

01
You own it
Server, storage, certs, compute — your shore, not a tenancy.
02
One binary, everywhere
One hull, every port — bare metal to the edge, same UX.
03
Streaming & atomic
Every byte streams; a deploy flips whole or not at all.
01 / QUICKSTART

Cast off in three commands.

$ curl -sSf boatramp.dev/launch | sh
↳ boatramp 0.2.0 → ~/.local/bin
$ boatramp serve &
↳ listening on http://127.0.0.1:8080
$ boatramp sync ./public --site my-site
↳ 214 files · sha 7f3a2c1 · streamed, 0 buffered
it's live — my-site · flipped in one atomic beat
// what just happened
content-addressed build
0 bytes buffered in memory
atomic pointer flip
prev launch still afloat
rollback → boatramp rollback
02 / CAPABILITIES · 6 OF 93

Six you'll feel on day one.

01
Atomic deploys
Content-addressed; launches whole or not at all.
sync
02
Streaming-first
Byte-for-byte store → socket; flat memory.
range: yes
03
Instant rollback
Immutable snapshots; back to shore in one flip.
rollback
04
Single binary
Server + API + CLI; bare metal to edge, same UX.
1 file
05
You own it
Your storage, TLS, compute — no tenancy, no phone-home.
self-host
06
Modern edge
HTTP/3 + auto-TLS; scale-to-zero, wakes on demand.
h3 · tls
0 files held in memory.

A 40 GB video and a 4 KB page cost the same flat memory — the tide never floods the box.

Back to shore, instantly.

Rollback is a pointer flip, not a rebuild — the previous launch is always still floating, ready in a beat.

02 · THE FULL MANIFEST Those six are just the shallows. The hull holds 93 capabilities across 13 systems — projects & multi-tenancy, edge compute, containers & microVMs, the gateway, HA clustering, auth & access, storage, observability, and an agent-native MCP control plane.
Explore all features
03 / BEYOND STATIC

Run code at the edge.

see all features →
function

Functions

One portable WASI component, many doors — run it behind a route, invoke it by name, put it on a schedule, or chain it into a workflow. SQL, KV, blob and queue bindings included.

→ functions
compute

Containers & microVMs

Pick a per-function runtime — the Wasm sandbox, an OCI container, or a Firecracker-class microVM — with snapshot/restore and scale-to-zero.

→ containers
gateway

Edge gateway

Publish private services through the edge: geo-aware load balancing (nearest region), passive + active health checks, retries, and DNS discovery.

→ gateway
secure

Own the controls

COSE/CWT tokens + Cedar policies, OIDC login, KMS/HSM signers, and per-site visitor access control at the edge.

→ auth & access
04 / PROJECTS

Many sites. One tenant boundary.

see all features →
apply.cfgone project, one file
(
  project: "acme",
  sites: [
    ( name: "www",  path: "www/dist" ),
    ( name: "blog", path: "blog/dist",
      routing: ( clean_urls: true ) ),
  ],
  functions: [
    ( name: "resize", component: "resize.wasm" ),
  ],
)
$ boatramp apply -f apply.cfg
  • A project owns many sites plus their functions and compute — same-named sites in two projects stay fully isolated.
  • Each project is a tenant boundary: kv, blob, SQL, and messaging namespaces are scoped to it — nothing bleeds across.
  • One apply.cfg reconciles the whole project in a single pass — pure upsert, never prunes, --dry-run to preview.
  • Per-project Cedar roles — admin / publisher / viewer; a token scoped to one project can't touch another.
05 / AGENT-NATIVE

Hand the helm to an agent.

see all features →
model context protocol

boatramp ships an MCP server. Point Claude or Codex at it and drive the whole control plane in plain language.

you ▸ roll docs back to the previous deployment, then tail the last 50 log lines
  • boatramp mcp over stdio for a desktop agent, or POST /mcp on serve — on by default.
  • Typed, enumerated tools — one per operation, no generic passthrough, every call legible in an audit log.
  • Runs with your token's authority — hand it a read-only token and the write tools simply 403.
  • One agent, many nodes — address them by name from mcp.toml.
06 / WHERE IT RUNS

One hull, every port.

same UX · same binary
Bare metal
boatramp serve
✓ same UX
NixOS
services.boatramp
✓ same UX
Docker / OCI
ghcr.io/boatramp/boatramp
✓ same UX
Cloudflare
boatramp cloudflare
✓ same UX
Cluster
serve --cluster-init
✓ same UX
Kubernetes
operator · Helm
✓ same UX
pre-1.0

boatramp is young and honest about it. APIs will still shift, edges are still being sanded. What's here is real and dogfooded — this site sails on it. If you like owning your stack and shaping tools early, come crew it.