Support contract

Lakebed is a public alpha. It is not production-ready. This page defines the current supported scope, not a 1.0 release announcement.

Offer and limits

Lakebed is free-only. Anonymous and claimed deploys use the current default limits. Claiming adds ownership, hosted server env, and outbound server-side fetch. It does not raise resource limits. There is no paid upgrade. Custom domains are not included. Lakebed app subdomains are included. Existing account exceptions do not establish a paid plan or a higher public limit.

CLI platforms

The CLI requires Node.js 22.18 or later. CI tests these combinations:

The checks cover package installation, scaffold creation, capsule builds, and local SDK tests. Other operating systems and architectures can work but are not tested. Node 20 is not supported. Node runs the CLI. Capsule code does not gain access to Node built-ins or arbitrary npm packages.

The browser client requires JavaScript, WebSockets, Fetch, and browser storage. Automated browser checks use Chromium. No browser-version support range for Firefox or Safari is established by those checks.

Public app API

The app contract consists of the documented capsule schema, server handlers, database API v1, client APIs, storage APIs, and CLI commands. See the API reference, capsule API, database, auth, and storage. Client code uses the bundled Preact modules. Server code uses lakebed/server and relative capsule modules. Generated files, private package paths, bundle structure, and undocumented transport messages are not app APIs. Error text can change. Use documented error codes and structured CLI output where available.

SDK and artifact compatibility

Alpha versions can change app APIs. Pin an SDK version when you need repeatable builds. The previous published stable baseline is lakebed@0.0.39. A compatibility fixture built with that exact package runs against the candidate hosted runtime. The check covers the stored server artifact and browser bundle: guest and signed-in auth, queries, mutations, reactive results, and reload. It does not prove that a new SDK works with an older hosted runtime, or that every historical artifact still runs.

Old signed-in bundles remain supported only through the announced migration window. Rebuild and redeploy with the replacement SDK when that migration is announced. Old bundles do not gain new auth behavior without a rebuild. There is no published retirement date yet. An app that requires new runtime behavior also requires a runtime that supports it. The 1.0 compatibility window is not active during alpha.

Optimistic updates

Optimistic updates are not part of the current hosted alpha support contract. The published lakebed@0.0.39 SDK supports predictions when the hosted runtime enables them and can describe the query and mutation.

Unsupported operations wait for the server. Server results remain authoritative, and a rejected mutation removes its prediction. createClient({ optimistic: false }) disables predictions throughout the page. This option does not change server transactions or permissions. A new SDK alone does not enable predictions on an older runtime.

Persistence and deletion

Local database rows and uploaded files reset when lakebed dev restarts. Hosted rows and files persist separately from the browser session. The alpha does not provide a published backup or recovery guarantee. Database export reads pages from separate snapshots. It is not a point-in-time backup. deploy restore resumes an archived app. It does not recover lost or deleted data.

Unclaimed deploys expire at the time printed by the CLI. Claimed deploys do not have that expiry. Archive and termination retain data. Termination prevents future updates and cannot be reversed. Neither operation is a permanent data-deletion request. There is no public CLI command for permanent hosting-account deletion. A complete hosting deletion process, backup expiry, and retained-record periods are not yet published.

Support and policies

Lakebed Auth terms and privacy policy cover the sign-in broker. They list support@ping.gg for Auth support and privacy requests. That does not establish a hosting support SLA or deletion deadline. Deleting Lakebed Auth data does not delete hosted apps or a developer hosting account.

Hosted apps are subject to the hosting acceptable-use policy. Use the abuse report route for abusive hosted content. The hosting support route, full hosting terms and hosting-specific privacy scope, and retention commitments are not yet published.