Repository navigation
2026-11-16. The open-source release: lake is public under the MIT licence, the security fixes from the pre-launch review, and lake running on liquid v0.3.0. Tracking issue: lake#1344.
Built against liquid v0.3.0 (66b5bb9) and zetta v0.5.0 (e11c02f5), the commits lake-platform pins. Not run on the dev environment before the cut (Steve's decision): the image waits for the operator changes under Before it rolls.
What it includes
Open source
- MIT
LICENSEandCOPYRIGHT(OramaSearch, Inc.), anSPDX-License-Identifier: MITline in every source file lake wrote (tools/spdx-headers.py),THIRD_PARTY_LICENSESand an SBOM (sbom.spdx.json,sbom.cdx.json),CONTRIBUTING.mdwith the CLA, andCODE_OF_CONDUCT.md(#1321). SECURITY.md: report privately, to security@orama.com or through GitHub's private vulnerability reporting, which is on (#1290).- The README is the public front door, linking Orama Lake (#1356). Internal material is out of the tree: runbooks, pricing documents, people, hosts, clusters, private links, review finding ids and quoted decisions (#1317, #1320 and a final sweep);
tools/release/public-scan.shchecks it, and the gate page isdocs/open-source/(#1335). Submodules are fetched over HTTPS (#1359). - Neutral defaults: no Orama sender, support address, legal links or order sheet unless configured (
LAKE_RESEND_FROM,LAKE_SUPPORT_EMAIL,LAKE_TERMS_URL,LAKE_PRIVACY_URL,LAKE_ORDER_SHEET) (#1320). The schema seeds no model prices. The hosted CI workflows are commented out (#1336).
Security fixes (each with its test; the findings are closed)
- Sign-in and sessions: cross-site sign-in posts refused;
__Host-session cookies behind TLS; a Clerk token issued to another product is not exchanged; a new Clerk subject is never linked to an existing account by email; a rotated-away TAAP key stops signing in (#1279, #1282, #1286, #1296, #1300). - Agents: a person's service launch is called with its own token, never the Lake's (#1276); task, launch and schedule credentials act only in their own account and workspace, through the workspace a call names, its route and the object it names, a public repository of another workspace included (#1286, #1292, #1296, #1356); a delegated turn never holds more than the asking agent; task credentials can be passed by reference and bus credentials bound to one workspace (#1304); a dataset-confined launch's query carries its work area to the engine (#1306).
- Repositories and drives: visibility needs
admin(#1337); Drive history authorizes the node at every revision; Drive, methodology, model and store writes follow branch rules (#1287, #1288); repository reads honour restricted folders; share-link expiry is a real RFC 3339 UTC time (#1339). - Platform: custom domains are claimed with a DNS TXT proof before the operator routes them, and a tenant cannot claim one of the Lake's own names (#1284, #1295); a service cannot be routed to another customer's workspace (#1302); an app binds only its own workspace's services (#1289); app token rotation is a generation the operator acknowledges (#1304).
- PKI, MCP, registry, secrets, orders, billing: ACME needs an account binding and a real HTTP-01 check (#1283); MCP tool access and IPv6 address checks (#1277, #1279); OCI uploads continue only in their repository; a sealed delivery checks the mount's workspace; order forms mail an address only a confirmation until it is confirmed; unauthenticated payment notices are counted, not each audited; a deleted workspace's unbilled usage is kept for its bill (#1278, #1280, #1296); unknown HTTP methods are counted as
other(#1340); signed links use a derived key; the SQL guard parses like the engine and the GitHub import reads only the caller's staging folder (#1281).
Liquid v0.3.0
- One sync server per repository, so liquid's staged uploads meet their authorized push (#1351).
- Agent session keys meet liquid's
delegation/1rules:mint_agent_session_keytakes a requiredrepository_id, Lake is issuer and dispatcher, every key expires within 15 minutes, and never-expiring keys are refused (#1358). - A pod seals its liquid identity with a passphrase file (
LIQUID_IDENTITY_PASSPHRASE_FILE), and lake stops at start, naming the variables, when it has none (#1355).
Other
server_infosays which liquid clients this Lake supports (#1330); a change, review or comment shows who signed it by name (#1331); a key is called an API token, with a liquid and liquify preset (#1333); TiDB and Cassandra credentials name a database or keyspace (#1305).- Fixes found by the release suite (#1345, #1347–#1350, #1357):
devbuilds again; a freed Content-Security-Policy string on every web app page; a dangling view that confined every dataset work area to nothing; the registry dropping methodology run and deployment user names; the order email claim statement that never parsed on PostgreSQL; contract, docs and fixture updates.
Migrations
0106_domain_claims, 0107_order_email_confirmation, 0108_retained_usage, 0109_principal_ids, 0110_taap_chain_heads, 0111_service_workspace_routing, 0112_app_token_generation, 0113_agent_session_repositories. The newest guard is agent_session_repositories_guard.
Before it rolls
- The operator vendors the schema and selects
agent_session_repositories_guard. - The operator gives each Lake a liquid identity passphrase (orama-operator#1215); without it a new pod does not start.
- The operator renders
LAKE_RESEND_FROM,LAKE_SUPPORT_EMAIL,LAKE_TERMS_URL,LAKE_PRIVACY_URLandLAKE_ORDER_SHEETon Orama's Lakes (orama-operator#1191); rolls together with orama-operator#1157 (sealed deliveries), #1164 (service connections, operator first), #1160 (app bindings) and #1150 (launch service tokens). LAKE_GIT_IMPORT_ROOTturns GitHub import on; unset, it answersnot_supported.- After the roll: everyone signs in once more (
__Host-cookies); agent session keys and signed links made before the roll stop verifying; OCI uploads in flight restart.
Not included
- #1293 (the engine enforces
workspace_sql's read; waits for zetta#1507), #1298 (on-demand service connections; its Clerk rule conflicts with #1296), #1323's model-price docs, #1338 (SCIM selectors, migration 0121) and #1342 (SSO pool binding): open for review.
Known issues
- Security issues still open are listed in the repository's issues; they are not described here.
- lake#1353:
WorkspaceStoreHandoff.ASearchRebuildDoesNotHoldOffTheReleasecrashes intermittently at shutdown (a Zetta object send calls a destroyed server's observer). - lake#1334: the image is built on Ubuntu, which bundles GPL and LGPL components.
- lake#1341: an unknown HTTP method on a routed path closes the connection without an answer.
Verification
- Full native suite on
devat565633b0(macOS, Homebrew Clang 22, PostgreSQL): 1758 run, 1 failed (lake#1353), 28 skipped. Six of the skips wereWorkspaceStoreZetta.*, because the Zetta binary used was older than the v0.5.0 pin; the others need an outside service (a Python Hugging Face client, provider credentials) or are Linux-only. The first run ondevafter the merges had 87 failures; every one is fixed in the pull requests above. - After the cut, against Zetta v0.5.0 (
e11c02f5) built from the pin and liquid v0.3.0 (lake#1364):WorkspaceStoreZetta.*6 of 6 passed, none skipped;WorkspaceStore*99 of 99. - After it, only the changes since were tested where they reach: the cleanup sweep (comments and docs) with the docs, markdown and frontend tests, and #1359's three submodule URLs fetched anonymously over HTTPS.
- Not run: the Linux lane, the image build and the dev environment.