Repository navigation
Release v0.3.0
Released: 2026-10-19 · Branch: main · Previous: v0.2.0 (2026-10-17).
Lake is where a customer designs, trains and ships AI on their own data: one C++26 binary that
serves a web app, a REST API and an MCP server over one registry of capabilities. v0.1.0 is the
full inventory of the product; this page lists what changed since v0.2.0. Everything v0.2.0 lists
is still in this release, and no capability was removed.
This release adds the lake.live order sheet (four offers with prices, Stripe Checkout for the
paid ones, an order form for every one, Resend email to support and the customer, and a status
page), and the fixes from the 2026-10-18 UX review (#820):
datasets named after their file and shown in the file's column order with types, a dataset page
that leads to a model, short pipeline and model names, Check that waits for Approve, Ask Orama
proposals that the capability accepts, and a sign-in runbook for every identity provider.
| Measured | Value |
|---|---|
| Since v0.2.0 | 57 commits (37 non-merge) across 15 pull requests, 2026-10-17 to 2026-10-19 |
| New capabilities | none; new routes: the order sheet, order form, Stripe Checkout return and order status pages (outside the registry) |
| Control-plane schema | 87 migrations, through 0089_cloud_orders (two new: 0088, 0089) |
Guides served at /docs |
41 (unchanged) |
| Tests | 1,159 run, 1,140 passed, 0 failed, 19 skipped (see Verification); web app 364 of 364 |
Read Known issues before exposing an instance. The
sign_in_ssosecurity
defect from v0.1.0 is still open.
Contents
- The lake.live order sheet
- Datasets
- Design: pipelines and models
- Ask Orama and the agents
- Developers and operators
- Schema
- Pull requests
1. The lake.live order sheet
#833, issue #831.
Contract: ../api/orders.md; page: ../ui/regions.md.
- Four offers on the apex region picker, prices in USD: Shared (usage-based, linked to the price
list), Private Warehouse ($1,000/month, $400 credit), Dedicated Cluster ($5,000/month, $2,000
credit, by provider and region), On-Prem (from $10,000/month, 40% credit). Every option includes
backups. Choosing the shared region is unchanged. - One configuration: a documented default merged with
LAKE_ORDER_SHEET(an RFC 7386 merge
patch), validated at startup. - Pay path (Private Warehouse, and a Dedicated Cluster in a region the operator can create): the
order is recordedpending_paymentand the person goes to a Stripe Checkout Session (subscription,
USD, quantity 1). The signed Stripe webhook moves it topaidorcancelledfrom the four
checkout.session.*events, once per event. A paid order is for one warehouse or cluster: larger
orders go through the order form (cloud_orders_checkout_one). - Order form path (every offer; On-Prem only this): recorded
submittedand emailed to support. - Email through Resend: support gets every field; the customer's copy carries nothing the sender
typed. Delivery state is on the row and retried with backoff. Resend is a deployment
dependency: withoutLAKE_RESEND_API_KEYorders are recorded but no email is sent
(../deployment/resend.md). - Status page
/orders/<id>?token=…(an HMAC under the instance key, nothing stored):
paid,provisioning,readywith the host, orfailed. - Abuse limits on the anonymous form: per-address and global hourly limits, a honeypot, a 32 KiB
body limit and per-field limits. Every state change is acloud_order_eventsrow and a central
audit event. - Provisioning a paid order is the operator's: orama-operator#634, in review as orama-operator#635.
Until it ships, apaidorder stayspaidand support takes it from the email. - Web app: the region menu and Workspaces offer "New setup…" and "On-prem…" from
server_info.order_sheet_url.
2. Datasets
- Named after the file (#824, issue
#814): choosing a file fills Dataset name from
its name, made valid; a name the person typed is kept. - Columns in the answer's and the file's order, with types
(#822, #834,
issue #812): the Query page and the dataset page
follow the answer'scolumns, never sorted keys. Columns shows each column's Type and Empty share
fromget_dataset's typed columns; First Rows asks forLIMIT 20, and the Query page sends a plain
SELECTwithLIMIT 501. The typed columns and the file's order need a workspace engine with
zetta#1021 (zetta#1299); against an older
engine the pages fall back to the first rows' types, and against one withoutLIMITto reading
the rows as before. - A dataset's page leads to a model (#825, issue
#818): Train a model on this opens a new
project with Build pipeline on the dataset; Keep durable is secondary.
3. Design: pipelines and models
- Short titles and model names from a description
(#826, issue #816),
the same rule on the server and in the web app; both are editable before building, and a typed
name always wins. - Check waits for Approve, in the page's words
(#823, issue #813). - A refused prediction row is named as people count it, with its key
(#828, issue #819).
4. Ask Orama and the agents
- Proposals the capability accepts (#827, issue
#794): each proposal is checked with the
registry's own input validation before it is offered; one that would be refused is withheld, and
the reply names every missing field. A malformed answer no longer loses the turn. A failed confirm
shows why and offers Try again only for a transient refusal. - Auto-Suggest's discover turn may read apps and builds
(#829, issue #795). - Ask Orama's guide gives the real path to a first dataset
(#830, issue #817).
5. Developers and operators
- Quick start's fetch example reads
LAKE_KEYfrom the environment
(#821, issue #815). - Deployments made with
liquid deployare shown
(#806, issue #805):
platform sync matches the repository by its liquid id (migration0088). - Sign-in runbook for Clerk, social connections, Lake OAuth, enterprise SSO and SCIM
(#811,../deployment/sign-in.md),
and a Resend runbook (../deployment/resend.md).
6. Schema
Two additive migrations, applied by the operator's schema Job before this binary serves. The
operator must vendor db/schema.sql at this tag and select the new guards before this image rolls.
The operator's dev vendors through 0088_repository_liquid_ids; 0089 is vendored by
orama-operator#635.
| Migration | Adds | Guard |
|---|---|---|
0088_repository_liquid_ids |
repositories.liquid_id and its index |
repository_liquid_ids_guard |
0089_cloud_orders |
cloud_orders, cloud_order_events, their indexes, the updated_at trigger and the lake_cloud_orders notification for a paid order |
cloud_orders_guard |
Pull requests
#806, #809 (v0.2.0's image), #811, #821, #822, #823, #824, #825, #826, #827, #828, #829, #830,
#833, #834, and the release pull request itself.
What v0.3.0 does not include
- Provisioning paid orders (orama-operator#634), the credit on the monthly bill, and
Stripe live mode (#754). - A signed-in customer's own servers in the picker, organizations owning servers
(#832), one identity across regions and moving a
workspace between regions (#758,
#759). - The 2026-10-18 walkthrough's feature requests (#847):
loading files of any size with progress (#846 and
#848 to #854), data search inside datasets (#841),
a SQL agent from Query it (#840), and the
onboarding, theme and shell fixes #839,
#842 to #845. - Everything v0.2.0 lists as not included and still open.
Known issues
Security-relevant first.
- Security: #562 —
sign_in_ssoissues a
session for an SSO identity it never verifies. Do not enable an SSO provider on an instance
others can reach until this is fixed. (Open since v0.1.0.) - Security: #838 — the order sheet's rate
limit trusts a forgeable client address, and its global cap can be used up by anyone to block
paid orders. - Security: #775 — an invalid, revoked or
expired bearer is treated as a visitor on capabilities a visitor may call instead of 401. - Security: #774 —
begin_email_recovery
tells a visitor whether an email has an account (200 vs 404). - Security: #772 —
deliver_webhookwaits
for the endpoint on the server's own thread; a slow endpoint stops Lake answering anything. - Security: #773 —
enroll_mfa's
otpauth://URI carries a hexadecimal secret where authenticator apps expect base32. - Security: oramasearch/orama-operator#492 — the operator copies any
Secret named in an app row's legacysecret_env_refsinto the app. - Sign-in: SAML has no endpoint an identity provider can post to
(#836), and enterprise OIDC cannot reach Entra,
Okta or Google Workspace (#837). - Ask Orama: a proposal that already worked can be confirmed again through the API (the page
hides the button), andstore_errorcounts as transient for Try again. - #779, #777,
#778, #783,
#801, #799,
#810 (no way to delete an account). - Agent turns that fail: #796,
#797, #803,
#804. - Other defects: #776,
#780, #781,
#782, #800,
#798, #802. - Still open from v0.1.0: #526,
#524, #560,
#522, #275,
#287, #636,
#224, #641,
and the tests that fail on a loaded host, #718
and #618.
Where it has run
Read on 2026-10-19: every lake-nonprod and lake-prod member (lake-dev, lake-testing,
lake-staging, eu.lake.live, us.lake.live) runs oramasearch/lake:v0.2.0. No instance runs
this release's source yet: it rolls after the operator vendors 0089 (see Schema).
Verification
Full suite (ctest --test-dir build -j6) on the release branch (docs/release-v0.3.0 off
dev at 770c041a), with LAKE_TEST_DB_URI set so the Postgres-backed cases run (each test on
its own fresh database). macOS arm64, Homebrew Clang, static Release build, Homebrew PostgreSQL
17.7, liquid v0.2.0 (1bf3d41) and Zetta v0.3.0 (d7551c75), the bridges' pins:
1,160 tests registered · 1,159 run · 1,140 passed · 0 failed · 19 skipped (they need a real
Zetta, a stdio MCP runner, the Hugging Face Python client or a browser terminal) · 1 disabled
(a benchmark)
No test was rerun after a failure. After the full run only documents changed (this page, the
indexes and the status lines); the 31 release-version, docs, markdown, guide, example and
agent-name tests were run again and passed. ReleaseVersion.* reads the version from
lake::version_string() and checks this page is indexed.
The order sheet's own tests (tests/test_orders.cpp, 25, with the Resend client) are in the run
above. The same suite ran on the branch of #833 after it was rebased onto the other PRs of this
release: 1,159 run, 0 failed.
Web app (frontend/): npm test 364 passed, 0 failed; tsc -b --noEmit clean;
npm run build (typecheck, tests, bundle, the effect and empty-state checks) passed.
The binary: ./build/lake version prints lake 0.3.0.
Not run for this release: the shared-library suite (build-shared), the Linux test lane
(lake-linux-test), and any exercise in a deployment: no instance runs this release yet.
Image
| Built from | the v0.3.0 tag, 18a89c14f3ce2629090e9373e673cb450ab96911 |
| Build tag | oramasearch/lake:main-18a89c14 |
| Release tag | oramasearch/lake:v0.3.0, added without rebuilding |
| Digest (both tags) | sha256:a875831ec21e05edfc7d26bb2db50c403f922dfe292b119eae93eacec4a4d89a |
Built on the cluster BuildKit (linux/amd64) from a detached checkout of the tag, with liquid
v0.2.0 (1bf3d41) and Zetta v0.3.0 (d7551c75), the bridges' pins. The web app stage ran
npm run build with its tests, and the built binary printed lake 0.3.0. The Docker Hub
repository is private (an anonymous request answers 404). No instance runs this image yet: it rolls
through the lake-nonprod and lake-prod sets after the operator vendors 0089, and the deployed
digest is recorded here when it does.
Running it
Lake is deployed by oramasearch/orama-operator
as a Lake resource, from a private oramasearch/lake:<tag> image built on the cluster
BuildKit. The operator must vendor this tag's schema (through 0089_cloud_orders) and select
repository_liquid_ids_guard and cloud_orders_guard before it serves this binary. The order
sheet needs LAKE_RESEND_API_KEY (../deployment/resend.md) and the
Stripe keys with the checkout.session.* events (../deployment/stripe.md).
See docs/deployment/aks.md and
docs/control-plane/schema.md.
To build and run locally, see docs/build/local.md.