Skip to content

Release v0.2.0

Choose a tag to compare

@homer6 homer6 released this 17 Oct 23:03
· 641 commits to main since this release
508f954

Released: 2026-10-17 · Branch: main · Previous: v0.1.0 (2026-10-12).

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 then. Everything v0.1.0 lists
is still in this release, and no capability was removed.

This release adds secure networking (declared connections with scoped credentials, egress
rules, developer tunnels with recipient-only certificates, and a Network section in each
workspace), regions and the apex region picker, a managed key for every new account with
an optional move to the person's own identity, Clerk webhooks that create, update and disable
accounts, one name per agent with all nine of Orama's agents offered to people, and a new
Ask Orama home.

Measured Value
Since v0.1.0 49 commits across 22 pull requests, 2026-10-12 to 2026-10-17
Paths in the OpenAPI 573 with billing on (569 under /v1, plus /mcp, /drive/download, /drive/files/download and /tunnel-clients/{platform}); v0.1.0 had 554
New capabilities 18 (listed below), plus the route GET /tunnel-clients/{platform}
Control-plane schema 85 migrations, through 0087_clerk_webhooks (four new: 0084 to 0087)
Guides served at /docs 41 (one new: the Network guide)
Tests 1,107 run, 1,088 passed, 0 failed, 19 skipped (see Verification); web app 327 of 327

Read Known issues before exposing an instance. The sign_in_sso security
defect from v0.1.0 is still open, and the end-to-end suite found more defects with a security
bearing.

How to read the status of a feature. Every feature below is implemented in the source tree
and served by lake-dev, which runs this release's source (see Where it has run).
Being served is not the same as being exercised end to end there; a feature that depends on the
operator says so. docs/design/status.md still describes the 2026-10-01
deployment and has not been brought up to this release.

Contents

  1. Secure networking
  2. Regions
  3. Identity: a managed key for every account, and your own identity
  4. Clerk webhooks
  5. Agents: one name each, all nine offered
  6. Ask Orama's home
  7. Schema
  8. New capabilities
  9. Pull requests

1. Secure networking

Epic #724; the cross-product tracker is
oramasearch/orama-bridge#186. The architecture is
docs/architecture/secure-networking.md.

  • Desired state in Lake's Postgres (#727,
    migration 0084_network): four desired/status pairs (connections, egress rules, tunnel
    grants, peers) matching section 11 of the operator's contract column for column, the guard
    network_guard, a lake_network notification on each desired write, and signed audit in the
    same transaction as each write. On rollout every existing app-to-service path is seeded once,
    so running apps keep their connectivity; Lake writes no internet-egress rows and the operator
    keeps its implicit rule. See docs/control-plane/network.md.
  • Fourteen capabilities through REST, OpenAPI and MCP, permission-checked and audited
    (#728): declare, list and remove connections;
    declare and list egress rules by DNS name or address range; list peers; the effective rules;
    tunnel sessions and network activity. Session and activity reads answer empty arrays with
    pending: "zetta#1281" until Zetta records them. See docs/api/network.md.
  • Scoped connection credentials (#731): an
    app-to-service connection may ask for its own credential (read or write, optionally one
    schema); rotate_network_connection_credential asks the operator to replace it. Lake records
    the scope and shows the workspace-secret reference; the operator creates the native role.
    See docs/api/scoped-credentials.md.
  • Developer tunnels (#730, migration
    0085_network_tunnel_ca): an account admin grants one member access to one service or app
    port for one hour to 30 days; the member sends a CSR and receives a client certificate signed
    under the customer's PKI authority, the relay endpoint and the relay CA. The private key never
    leaves the member's machine. Grants end by revocation or expiry. See
    docs/api/tunnel-grants.md.
  • Lake serves the tunnel client (#745):
    the image carries the zetta-tunnel binaries (macOS arm64, Linux amd64) from
    oramasearch/zetta-tunnel-clients:v0.1.0, pinned by digest. tunnel_client_downloads gives
    any signed-in person the version and, per platform, the SHA-256, the size and a 15-minute
    signed link, which GET /tunnel-clients/{platform} serves without a session. See
    docs/api/tunnel-clients.md.
  • The Network section in each workspace, after Ship
    (#729): Overview, Connections, Developer
    Access, Private Networks, Egress and DNS, Policies and Activity, which together call all
    fourteen network capabilities. Every row shows Waiting, Updating, Ready, Failed, Removing or
    Removed, and pages read again every 3 seconds while a row is still settling (#749).
    Get credentials is numbered copy-and-paste steps: make the key and request, paste it, save
    the certificates, install and start the tunnel client, then connect with the service's own
    working command (psql, mysql, valkey-cli, cqlsh or curl), the password masked until
    Reveal (#748, #750, #751). A Ready service in Ship → Services has Developer access,
    which opens Grant access filled in. See docs/ui/network.md and the
    Network guide.

What the operator does with these rows (enforcing connections and egress, running the relay,
delivering scoped credentials) is the operator's work and is not claimed by this page.

2. Regions

#757, liquid-bridge decision 64.

  • Configuration: LAKE_REGION, LAKE_REGION_LABEL, LAKE_REGIONS and LAKE_APEX_HOST,
    set by the operator when a LakeSet member has a region. Unset, Lake behaves as before. An
    invalid value stops startup with a message naming the variable.
  • server_info gains region ({name, label} or null) and regions
    ([{name, label, host}]).
  • The apex region picker: a request to LAKE_APEX_HOST gets a server-rendered page, working
    without JavaScript, that preselects the lake_region cookie, else the region nearest the
    visitor's country (CF-IPCountry), else the first; choosing one sets the cookie and redirects
    to that region's host with the same path and query.
  • The web app names the region in the top bar (with links to the others), on sign-in and
    sign-up, and beside each workspace.

An account exists in one region only, and a workspace cannot move between regions
(#758,
#759). See docs/api/regions.md
and docs/ui/regions.md.

3. Identity: a managed key for every account, and your own identity

#762, liquid-bridge decision 65 (amending 44),
migration 0086_identity_links.

  • Every new account gets a managed key. Lake's own password sign-up no longer asks for an
    identity document; Lake mints a managed key, as a first Clerk sign-in already did. Application
    pools still require the person's document.
  • Account → Identity (/settings?tab=identity) shows the account identity, the key it signs
    with and what it signs as, and offers Use my own identity: begin_own_identity verifies the
    output of liquid identity show --document (an initial document only) and issues a ten-minute,
    single-use challenge; use_own_identity verifies the liquid sign artifact <challenge>
    signature, has the managed key sign the link, and in one transaction records the link and
    destroys the managed seed. The account keeps its identifier, so grants, memberships, audit and
    repositories carry over; sign_in_taap with the own key reaches it. Linking is one-way.
  • Pushes name their signer: every push_change audit event names author,
    author_account and author_is_caller.

See docs/api/identity.md.

4. Clerk webhooks

#765, migration 0087_clerk_webhooks.

POST /identity/clerk-webhook is verified with Lake's own Svix HMAC under
LAKE_CLERK_WEBHOOK_SECRET (the route answers 404 without it) and applies each svix-id once.
user.created provisions the account as a first Clerk sign-in does; user.updated sets its
verified email and display name; user.deleted disables the account (users.disabled_at) and
revokes its sessions, tokens and devices without erasing anything. A disabled account is issued
no session. Only a verified email is linked or stored. Every delivery is one central audit event.
Registering the endpoint and injecting the secret per instance is
oramasearch/orama-operator#541. See docs/api/clerk.md.

5. Agents: one name each, all nine offered

#763, #788.

  • One source of names, include/lake/control/agent_library.hpp: Ask Orama, Project Agent,
    Application Agent, Experiments Agent, Auto-Suggest Agent, Agent Creator Agent, Eval Generator
    Agent, Auto-Suggest Corpus Agent and Project Corpus Agent. AgentNames.* fails when a page,
    guide, document, test or tool spells one differently.
  • No agent is internal. list_agent_library lists all nine (include_internal is accepted
    and ignored); the corpus agents build a training corpus for you and the Eval Generator Agent
    creates an eval. Design → Agents shows one By Orama list.
  • Talk to in Ask Orama lists every agent by its library name, with its one-sentence purpose
    and Where you meet it; an agent this Lake does not run is shown disabled.

6. Ask Orama's home

#764, #784,
#786, #789,
#791.

The empty home (/) says what Lake is for (AI sovereignty: when you're tired of renting
someone else's AI, Orama Lake is where you own your AI
), lists the agents you can talk to, and
maps Design, train and ship production-grade AI: each rail group (Data, Design, Train, Ship,
Network, Organization, Developer) as a card with its icon, every page with one line and an
example question. The Network group lists all seven Network pages; Developer links MCP Tools and
MCP Worked Flows. A suggested question goes into the message box to edit, instead of being sent.
Only what this Lake runs is shown (Billing only with LAKE_BILLING, Deployments only when
server_info says so). See the Ask Orama guide.

7. Schema

Four 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.

Migration Adds Guard
0084_network the four network desired/status pairs; the one-time rollout of existing app-to-service paths network_guard
0085_network_tunnel_ca client_ca_pem on tunnel grants, relay_ca_pem on their status (none new)
0086_identity_links nullable managed seed with seed_destroyed_at; identity_link_challenges, identity_links identity_links_guard
0087_clerk_webhooks users.disabled_at, clerk_webhook_deliveries clerk_webhooks_guard

The operator's dev vendors the schema through 0087_clerk_webhooks
(internal/controller/assets/lake-schema.sql).

New capabilities

Each is one registry entry, served under /v1/<name>, as an OpenAPI operation and as an MCP
tool. The list was checked against the OpenAPI served by lake-dev and by a local run of this
release's binary: every path in it is named here or on the v0.1.0 page.

Area Capabilities
Network connections create_network_connection, list_network_connections, rotate_network_connection_credential, remove_network_connection
Egress create_network_egress_rule, list_network_egress_rules
Developer tunnels grant_network_tunnel, issue_network_tunnel_certificate, revoke_network_tunnel, list_network_tunnel_grants, list_network_tunnel_sessions, tunnel_client_downloads
Peers, rules and activity list_network_peers, network_rules, network_activity
Identity account_identity, begin_own_identity, use_own_identity

Routes outside the registry: GET /tunnel-clients/{platform} (in the OpenAPI), and
POST /identity/clerk-webhook and the apex region picker (not in the OpenAPI).

Pull requests

#722, #723 (release and branch documentation), #732, #733, #734, #735, #736, #737 (secure
networking), #748, #749, #750, #751 (Developer Access and the tunnel client), #760 (regions),
#766, #793 (agents), #767 (managed key and own identity), #771 (Clerk webhooks), #770, #785, #787,
#790, #792 (Ask Orama's home), and the release pull request itself.


What v0.2.0 does not include

  • A production environment. Lake runs only on development and nonprod instances; lake.live
    is planned (oramasearch/orama-operator#513,
    #755).
  • Network enforcement in Lake. Lake records desired state; the operator enforces it. Tunnel
    session history and network activity are pending in Zetta (zetta#1281), so those reads answer
    empty with pending. Network health (#740),
    usage (#738) and billing
    (#739) for networking are not built. Service
    connection credentials are not yet in the workspace's secret store
    (#629).
  • Tunnel clients for macOS on Intel, Linux arm64 and Windows
    (oramasearch/zetta-tunnel#26).
  • One identity across regions, and moving a workspace between regions
    (#758, #759).
  • Linking an already-rotated identity: only initial liquid documents are accepted, and a link
    cannot be undone.
  • Everything v0.1.0 lists as not included and still open: automatic invoicing
    (#621), all state in workspace Zettas, Zetta
    parity (#185), storage phases 2 to 4,
    pagination on every list page (#227), native
    agents on the Orama base model (#246; see
    also #799 below), changing an agent with the
    Agent Factory (#271), model destinations and
    drift.

Known issues

Security-relevant first. Many were found by the end-to-end suite
(oramasearch/orama-operator#537) on lake-testing at revision
51fe838b, and are open at this tag.

  • Security: #562 — sign_in_sso issues 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: #775 — an invalid, revoked or
    expired bearer is treated as a visitor on capabilities a visitor may call (for example
    list_repositories answers 200) instead of 401.
  • Security: #774 — begin_email_recovery
    answers 200 for an email with an account and 404 for one without, so anyone can find out
    whether an address has a Lake account.
  • Security: #772 — deliver_webhook waits
    for the endpoint on the server's own thread; a slow endpoint stops Lake answering anything,
    including its liveness probe.
  • Security: #773 — enroll_mfa's
    otpauth:// URI carries a hexadecimal secret where authenticator apps expect base32, so a
    person who enrolls cannot sign in with their authenticator.
  • Security: oramasearch/orama-operator#492 — the operator copies any
    Secret named in an app row's legacy secret_env_refs from the Lake namespace into the app.
    Lake's API never writes a plain name; the fix is in the operator.
  • #779 — claim_recovery_deliveries
    answers a signed-in person 400 instead of an authorization refusal.
  • #777 — Branch Protection and the
    Organization Audit tab read the operator-only audit log, so owners cannot open them.
  • #778 — scim_get_user still answers 200
    for a user scim_delete_user deleted.
  • #805 — platform sync skips every
    deployment liquid makes (repository id mismatch).
  • #783 — create_app accepts an image not
    pinned by digest; the operator then fails the app.
  • #801 — run_solution takes its workspace
    offline for about 400 s, then fails.
  • #799 — a native agent on Lake's base model
    cannot chat or run: the base-agent tokenizer is missing.
  • Agent turns that fail: #794 (Ask Orama's
    create_stream proposal), #795 (Auto-Suggest
    discover), #796 (Project Agent pipeline
    design), #797 (Experiments Agent status),
    #803 and
    #804 (Agent Creator Agent).
  • Other defects: #776 (import_repository
    refuses an archive export_repository made), #780
    (a LightGBM binary model is refused, and the error quotes freed memory),
    #781 (upload_dataset jsonl validation),
    #782 (index search ignores field),
    #800 (stop_experiment rewrites a finished
    experiment), #798 and
    #802 (apps and methodology Jobs on
    lake-testing).
  • 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-17 from each instance's GET /v1/server_info and the LakeSet status on the
managing cluster. All of them report version 0.1.0: they were built before the version moved.

Instance Image Revision What it carries
lake-dev.oramadev.net (lake-nonprod member dev) oramasearch/lake:dev-34718173 34718173 This release's source, apart from the version, its test and this page
lake-testing, lake-staging (lake-nonprod) oramasearch/lake:dev-51fe838b 51fe838b Everything up to regions (#760); the end-to-end suite ran on lake-testing
lake.oramadev.net (Lake/prod, temporary) oramasearch/lake:dev-ca3fd195 ca3fd195 Up to the tunnel client (#751)
lake-shared, lake-shared-us (lake-prod) oramasearch/lake:20261012a 2e6f6d7 v0.1.0

lake-dev serves 573 OpenAPI paths, the same set as a local run of this release's binary with
billing on.


Verification

Full suite, run serially (ctest --test-dir build, no -j) on the release branch, 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.1.0
(f669726, liquid-bridge's pin) and Zetta v0.2.0 (4015ef76), 651 seconds:

1,108 tests registered · 1,107 run · 1,088 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 29 docs, markdown, guide, example, agent-name and release-version tests were run again and passed. The suite includes the new ReleaseVersion.* (3 tests): version_string()
equals CMake's PROJECT_VERSION, current_version() agrees with it, and this page exists and is
indexed. Before this page was indexed the third test failed, as it should.

Web app (frontend/): npm test 327 passed, 0 failed, 0 skipped; tsc -b --noEmit clean;
npm run build (typecheck, tests, bundle, the effect and empty-state checks) passed;
tools/ui/test-token-gates.sh passed.

The binary: ./build/lake version prints lake 0.2.0. Run locally with a memory store,
GET /v1/server_info reports version 0.2.0 and /readyz answers 200; its OpenAPI has the same
paths as lake-dev's, apart from the nine billing paths, which it omits because billing was off.

Linux: the image was built from a detached checkout of the v0.2.0 tag (508f9540) on the
cluster BuildKit (linux/amd64, Ubuntu 24.04, Clang 19.1.7, liquid f669726): Lake compiled
(110 s, ccache 801 misses of 3,934) and the built binary printed lake 0.2.0. The web app stage
(npm ci, then npm run build with its tests) was a BuildKit cache hit, because frontend/ is
unchanged since the dev-34718173 image, whose build ran it. See Image.

Not run for this release: the shared-library suite (build-shared), the Linux test lane
(lake-linux-test), and any end-to-end exercise in a deployment beyond what
Where it has run records.


Image

Built from the v0.2.0 tag, 508f9540aa4c195a1d8a24a6001d05ea1f2c0c15
Build tag oramasearch/lake:main-508f9540
Release tag oramasearch/lake:v0.2.0, added without rebuilding
Digest (both tags) sha256:e41273a7a404a99d188c7ca4d9bd973aa3d5c42d958a537400f804fb5d9c95b0

The Docker Hub repository is private (an anonymous request answers 404). No instance runs this
image yet; rolling it onto a cluster goes through the operator's resources, 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 0087_clerk_webhooks) and select
network_guard, identity_links_guard and clerk_webhooks_guard before it serves this binary.
Clerk webhooks need LAKE_CLERK_WEBHOOK_SECRET and the endpoint registered with Clerk
(oramasearch/orama-operator#541); regions need the LakeSet member's
region. See docs/deployment/aks.md and
docs/control-plane/schema.md.

To build and run locally, see docs/build/local.md.