Welcome back.
Log in to your LakehouseBox account.
Advanced connection options
Need help? Contact support
Welcome
Set your password.
You are finishing the setup of your LakehouseBox account.
The link in the mail is valid for three days and works once. Expired? Sign up again with the same address, or ask for a reset link.
Password reset
Choose a new password.
Every session of yours is signed out when it is set. Tokens your agents hold are not affected.
The link is valid for 30 minutes and works once. Expired? Ask for another.
Forgot your password
Reset it by email.
Enter the address of your account. If it has one, a link to choose a new password is on its way; it is valid for 30 minutes.
Check your email.
If has a LakehouseBox account, a mail from no-reply@lakehousebox.com with the reset link is on its way. The link is valid for 30 minutes and works once.
Nothing arrives within a minute? Check the spam folder, then the spelling of the address; a new link can be requested once a minute. An account that logs in through an external identity provider has no password here and gets no mail.
Connect an agent
Connect this agent to your catalog?
An agent ran lhbox login on a machine and is waiting. Approving creates an agent of your organisation, named after that machine, with exactly the access you choose below; its key goes to that machine only and never through the conversation. You can revoke it at any time from Connections on your account page.
First login
Name your organisation.
You are signed in, but this identity belongs to no organisation yet. Catalogs, tokens and members live in one; you will be its first admin.
Catalogs
An Iceberg catalog holds your tables and connects them to your tools; LakehouseBox includes the storage and the table maintenance, your agent or engine runs the analysis. Your level on a catalog decides what its credentials can do: write or read. Click a catalog to connect to it, see its tables, its access and its settings.
Loading…
Connect your engine
One command fetches a connection recipe for DuckDB, PyIceberg or Spark with a credential that carries your level on this catalog. Every table is then <catalog>.<namespace>.<table>.
For engines and the API
The identifiers behind the name. The API resolves the name wherever it takes an id; these are for a recipe or a request written by hand.
Tables
Agents and engines create tables with the connection recipe; this list is what the catalog holds now. Query opens a table in the SQL explorer.
Loading…
Create a table by hand
The table gets this catalog's format version for new tables (Settings; version 2 unless changed). Field ids are assigned in order.
Who can use
Grants per catalog: members have read through membership, the creator and admins write. An admin, or someone holding write, can change them here.
Tokens and connections on this catalog
Every agent of the organisation holding read or write here. Create, edit and revoke them under .
Visibility
A private catalog is read with credentials only. A public catalog exposes every data file and every retained metadata file to anonymous reads (a bucket policy); the catalog API itself stays private. Admins only, the name typed out.
Rotate the catalog credential
Issues a new key pair for this catalog and revokes the old one at once. Every engine using the old recipe stops; fetch a new recipe afterwards. Storage sessions already vended keep working until they expire, up to one hour.
Pick a table on the left for its schema, row count and snapshots.
This panel refuses statements other than SELECT, WITH, SHOW, DESCRIBE, EXPLAIN as a courtesy against accidents; it is not a permission. The credential is the boundary: via catalog, DuckDB holds the credential the API vends for your level on the catalog; in Direct mode, a credential scoped to one table's prefix. Writes go through your engine (DuckDB, PyIceberg, Spark) with the connection recipe. The one exception is the Load the sample table button on the Catalogs tab, which creates samples.readings (20 rows) through the catalog with your write credential. A query without a LIMIT gets one.
Connections
Machines connected with lhbox login and approved by a person here, and applications (mcp) authorised on the consent page of the remote MCP server. Each connection is an agent of the organisation named after the machine or the application, holding exactly the access approved; its key lives on that machine only, and an application's access and refresh tokens all end when it is revoked. Revoking stops it at once.
Loading…
Tokens
A token is a machine identity of the organisation (the CLI calls it an agent): its own API key, shown once, with read or write on the catalogs you choose and nothing else. Revoking it stops it at once. A token's grants can never exceed those of the person creating it.
Loading…
Create a token
Members
Two roles: admin (everything, including inviting, removing and deleting catalogs) and member (read on every catalog, write on the ones they create or are granted). The last admin cannot leave or be demoted.
Loading…
Invite
Usage
The free plan meters one thing: bytes stored, summed over the organisation, measured hourly by maintenance. Over the limit, creating catalogs or tables and vending write credentials answer 409 quota_exceeded until space is freed; reading keeps working.
Loading…
You
Organisation
Loading…
Domains
Claim your email domain to let colleagues with a verified address there join by themselves (switch it on below). Public mail domains cannot be claimed; the proof is your own verified address on the domain.
Change password
At least 12 characters. Every other session of yours is signed out when it changes; this one stays.
Sessions
Every browser tab logged in as you. Revoking one signs it out at its next request; the refresh token behind it stops working at once.
Loading…
Your API keys
Keys minted for you as a person (the CLI's lhbox login does this). Prefer tokens for anything automated: they are scoped and revocable on their own. Revoking the key you signed in with signs you out.
Cancel account
Deletes your account now: every API key of yours revoked, your identity unlinked, your memberships removed. An organisation left without members has its catalogs purged within 30 days. If you are the only admin of an organisation with other members, make someone else an admin first. This cannot be undone.