Repository navigation
Release v0.7.0
Released: 2026-10-24 · Branch: main · Previous: v0.6.1 (2026-10-24).
The first release after lake.live's launch, gathered in #1158.
A new home page, Quickstart, takes a dropped dataset to search and model answers on your own
website. A browser key is the public credential that website holds. Orama can give credits
and run coupon codes for ads. Signing out no longer revokes API keys. A white-labelled Lake
gets its customer's domain, sign-in and brand. lake migrate and lake manifest let
the image apply its own schema. Plus security fixes and three memory bugs found by AddressSanitizer.
Four migrations (0100 to 0103), all additive. The schema reaches the control database before
the image rolls (Before it rolls).
Features
| PR | Change |
|---|---|
| #1157 | Quickstart, the new home page at / (Ask Orama moves to /ask; old links redirect). Drop a CSV or JSONL file: it becomes a dataset, a published search index, website code (plain page, React, curl) with a live search box, then Train a Model trains and publishes a model whose answers show beside each result. start_quickstart, quickstart_status, train_quickstart and quickstart_snippets on REST, MCP and the agent documents (Start Here). Each step calls the existing capabilities as the person, so permissions, the balance gate, audit and metering are theirs; progress is kept in the workspace Zetta (../api/quickstart.md, #1128) |
| #1177 | Browser keys (lbk.<id>.<secret>): the credential a website's page holds. Bound to one workspace, one index and optionally one model; only search_index and predict on those; only from its listed origins (CORS answers those alone); a per-minute limit shared by every replica (600 by default). Not tied to any session: it lasts until revoked or its expiry. create_browser_key, list_browser_keys, revoke_browser_key; the Quickstart makes one in one click; Search Index gets Website Keys. Migration 0102_browser_keys, hashes only (../api/browser-keys.md, #1152) |
| #1155 | Credits from Orama. An instance administrator (or the Lake's admin token) gives an account a credit and revokes what is left of it: grant_balance_credit, revoke_balance_credit, console Give credit. Spent before paid money, earliest expiry first; never unlocks the overdraft; when it expires or is revoked only its unused part stops counting. One email, audited centrally. Migration 0100_balance_grants (../api/billing.md#credits-from-orama, #1134) |
| #1165 | Coupon codes for ads. create_coupon, list_coupons (redemptions, first top-ups and spend per campaign), disable_coupon, redeem_coupon; Administration → Coupons. A redemption is an ordinary credit from Orama. lake.live/?code=… carries the code through the region picker and sign-up. One redemption per account and per email (kept as a hash), new accounts only by default, failures rate-limited. Each region creates its own codes (#1159). Migration 0101_coupons (../api/billing.md#coupon-codes, #1156) |
| #1147 | lake migrate applies the schema built into the image (one transaction, an advisory lock, JSON report, exit codes) and lake manifest prints what the image needs from the operator: the schema, its Stripe webhook events and products, and every environment variable it reads. server_info lists the Stripe events. With orama-operator#965 a lake release is only an image change (../deployment/operator-interface.md, #1119) |
| #1167 | Sign-in on a white-labelled Lake's own domain: LAKE_HOST_ALIASES (browser pages on the Orama host redirect to the customer's), LAKE_CONTROL_HOST, and LAKE_SIGN_IN_SSO_PROVIDER, which makes the customer's identity provider the only way in, refusing Lake's other sign-in methods in its own pool. All off until set (../deployment/white-label-sign-in.md, #1136) |
| #1174 | A white-labelled Lake shows its customer's brand (LAKE_BRAND_* or LAKE_BRAND_FILE): the console, sign-in, lake's own pages, every email, llms.txt, the skill (/skills/<short_name>/SKILL.md), MCP initialize, tools/list, OpenAPI and server_info. Unset, lake.live is byte-for-byte unchanged. The brand's terms and privacy links win over LAKE_TERMS_URL / LAKE_PRIVACY_URL (../serving/brand.md, #1135, #1137) |
| #1171 | Terms and privacy links under every sign-up and sign-in form, Clerk's and Lake's own (LAKE_TERMS_URL, LAKE_PRIVACY_URL; default Orama's published pages; off for none; a malformed URL stops lake). viewer.legal (liquid-bridge#15) |
| #1139 | The lake.live plan cards list "Your own domain, white-labelled (available on request)" on Private Warehouse, Dedicated Cluster and On-Prem (#1129) |
| #1130 | The apex lake.live answers llms.txt, llms-full.txt and the skill with every region's MCP server and guides, instead of the picker's HTML (#1110) |
Security and identity
| PR | Change |
|---|---|
| #1173 | Signing out ends only that browser. A Clerk sign-out used to revoke every session, API key and device of the account. Lake now binds each browser session to its Clerk session (the default session token's signed sid), and a session event ends only the browser it names. No sign-out ends a key, including keys made in that browser. A new Sign out everywhere (sign_out_everywhere, Sessions page) ends everything for your own account. Bans, locks, deletion and revoke_user_sessions still end everything. Migration 0103_clerk_session_binding (#1163, #1172) |
| #1138 | Under Clerk, Lake's own password sign-up and sign-in in the lake pool are refused (403), by the same rule that makes viewer say password_sign_up: false; it was possible to skip Clerk's sign-up control (#1098, the provisioning step of LSR-011) |
| #1133 | An unknown email takes as long to reject as a wrong password (a dummy Argon2id check), so response times no longer show which emails have accounts (#1101) |
| #1131 | Per-client limits believe X-Real-IP / X-Forwarded-For only from trusted proxies (LAKE_TRUSTED_PROXY_CIDRS; unset: loopback and the private ranges, so nothing changes before the operator sets it) (#1083) |
| #1169 | A proxy listener (LAKE_PROXY_PORT): client-address headers are believed only on the port the ingress alone can reach, and the main port then trusts no one by default. Off until the operator sets it (orama-operator#961) (#1132) |
Fixes
| PR | Change |
|---|---|
| #1178 | Three memory bugs from the AddressSanitizer run: a segfault at start with no control store (#1168), a heap-use-after-free in the memory store's SCIM group upsert (#1175), and a container read after unlock in the search job thread (#1176) |
| #1162 | The tools/e2e/ browser scripts drive the React console (Clerk ticket, first top-up on Stripe's test Checkout, the workspace), so the dev → testing gate's browser half runs again (#1099) |
| #1160 | Docs: lake.live's complete price list as Steve approved it (23 rates, effective 2026-11). Not published by this release: set_price_list on each region is a separate step |
Before it rolls
- The schema through
0103reaches each control database before the image. Either
orama-operator#965 (the operator runslake migratefrom this image, the first that has it), or an
operator release that vendorsdb/schema.sqlthrough0103withclerk_session_binding_guard
selected. A v0.7.0 pod on the v0.6 schema fails Clerk sign-in, grants, coupons and browser keys. - No new required setting. Every new variable (
LAKE_PROXY_PORT,LAKE_TRUSTED_PROXY_CIDRS,
LAKE_TERMS_URL,LAKE_PRIVACY_URL,LAKE_HOST_ALIASES,LAKE_CONTROL_HOST,
LAKE_SIGN_IN_SSO_PROVIDER,LAKE_BRAND_*) defaults to today's behaviour;lake manifest
declares them all. - After the image: orama-operator#961 (the proxy port) and #963 (a customer's domain and brand)
roll only once every Lake runs v0.7.0. - Behaviour to know: revoking a device no longer ends keys made in a browser on it; use
Sign out everywhere to end every credential.
Known issues
- Security, open: 76 issues labelled
securityremain open in lake, from the pre-launch review
and its companions. LSR-200 (#1006, hosted code
spoofing forwarding headers) is closed once orama-operator#961 routes the ingress to #1169's proxy
port. LSR-011's existing linked rows (#920) are
not fixed here: #1138 stops new ones. - Found on dev by the e2e scripts, not fixed here: a workspace cannot reach the account's own
Postgres service (#1151), Scan my workspace
suggests nothing (#1153), a TiDB service never
becomes Ready (#1161). - A flaky timing test under load (#1150).
- Follow-ups: coupon codes in every region at once (#1159),
SSO just-in-time managed keys (#1166), the rest
of the console's copy under a brand (#1170).
Under SSO-only sign-in the pages show the provider button without the terms line. - The price list is approved but not published; lake.live still charges only model tokens until
set_price_listruns on each region. - Those of v0.6.1: auto top-up needs each Stripe key's PaymentIntents
permission (#1123, #1124).
Verification
On the release branch (dev at 72b6e26e plus the version and the two fixes below), macOS arm64,
Release, against zetta v0.5.0 (e11c02f5) and liquid at liquid-bridge's pin, PostgreSQL 17,
LAKE_TEST_SKIP_STALE_SWEEP=1, a live Zetta v0.5.0 node (LAKE_TEST_ZETTA_URL, LAKE_TEST_ZETTA_BINARY),
ctest -j6 (252 s):
| Check | Result |
|---|---|
| Build | every target builds and links |
| Full suite | 1,602 tests: 1,589 passed, 0 failed, 12 skipped, 1 disabled |
| Live Zetta | ran and passed: WorkspaceStoreZetta.*, WorkspaceRecordsZetta.*, QuickstartZetta.ADatasetBecomesSearchAndModelAnswersOnARealEngine (upload, index, search, train, predict on a real engine) and the agent-to-Zetta HttpResponseIsolation cases |
| Skipped | the Agent Factory and agent HttpResponseIsolation cases' PostgreSQL variants (memory-only by design, ×8), the Hugging Face Python client, a stdio MCP runner, a browser (InstanceOrigin), and BrowserKeys.AnExpiredKeyIsToldItExpired on the memory store (expiry is the PostgreSQL store's); SearchBenchmark is disabled by design |
| Web app | npm ci && npm run build and ./tools/ui/test-token-gates.sh pass |
| Linux | the image build from the tag is the Linux build; the full suite on the cluster BuildKit lane was still running at the tag, and its result is recorded on lake#1158 and added here |
Found by this run and fixed on the release branch (both from rebase resolutions merged during the
review, each noted on its PR):
9dd9daec:tool_referencelost itsbranddeclaration in #1174's rebase;devdid not compile.a77f045e: #1177's rebase left the central audit table out of order, socreate_browser_keyand
list_browser_keyswere unclassified (AuditRouting.EveryRegisteredCapabilityIsClassified).
Not yet run: the image on any cluster (it rolls after the schema, Before it rolls),
the testing e2e gate, a live Stripe grant or coupon redemption, and tools/e2e/quickstart.mjs on lake-dev.