# LakehouseBox

> LakehouseBox is a managed Apache Iceberg catalog service operated in Nuremberg, Germany, by NewCo SL (Spain). API https://api.lakehousebox.com, Iceberg REST catalog https://catalog.lakehousebox.com, S3-compatible storage https://s3.lakehousebox.com, website https://lakehousebox.com. People sign up at https://lakehousebox.com/signup and finish from a set-password link sent by email (the CLI can instead use an emailed code: POST /v1/signup/start, then /v1/signup/verify with accept_terms true); the engine, DuckDB 1.5.5+, PyIceberg or Spark, connects directly to the catalog with a per-catalog credential. Free plan: 5 GB stored, nothing else metered, no card.

The CLI is one standard-library Python file: `curl -fsSL https://lakehousebox.com/install.sh | sh`, then `export LHBOX_URL=https://api.lakehousebox.com`. Every API error is a typed JSON object with a code, a message and usually a remedy; GET /v1/usage lists every limit with its headroom. Accepting the Terms of Service is a decision for a person: an agent should show them and ask before sending accept_terms.

People sign up at https://lakehousebox.com/signup (name, email, organisation name and handle; a mail to finish setting up the account follows) and log in at https://lakehousebox.com/app/ with email and password (the session stays in the browser tab; no cookie; https://lakehousebox.com/app/forgot resets a forgotten password). A self-hosted deployment may trust an external OpenID Connect issuer instead. The account page https://lakehousebox.com/app/<organisation handle> is a static page, small on purpose: warehouses with the caller's level (read or write) on each, create and delete (typed name) warehouses, tokens for agents with read or write per warehouse (the API key shown once), members and roles (admin, member), usage against the 5 GB, the organisation's name and domains, the Terms, account cancellation, and a SQL panel that runs DuckDB compiled to WebAssembly in the visitor's browser against the catalog and the object store with the visitor's own scoped credentials (nothing of LakehouseBox's sees the data). It refuses writes as a courtesy, not as a permission. It is not a dashboard and is not the primary interface: the API and the CLI are; agents hold tokens, never a person's login.

Not available today: a Snowflake data path, Google or social login, an SLA, paid plans.

## Docs

- [Getting started](https://lakehousebox.com/docs/): install the CLI, sign up (browser or email code), connect an engine, import Parquet, agent keys, limits
- [Uploaders](https://lakehousebox.com/docs/uploaders/): a write-only credential for the blob bucket, for relays, devices and partners that only drop files
- [Lifecycle rules](https://lakehousebox.com/docs/lifecycle/): expire blob-bucket files by age or date under a prefix, abort stale multipart uploads; blob buckets only
- [Ingest sinks](https://lakehousebox.com/docs/ingest/): one HTTP intake per table for producers without an engine, JSON arrays in with a send-only key, Iceberg rows out on a rolling policy
- [Agent setup](https://lakehousebox.com/docs/agent-setup/): the instructions an agent follows: install the CLI, lhbox login, the person approves once in the browser, the DuckDB recipe, the first task
- [CLI reference](https://lakehousebox.com/docs/cli/): every command's --help, exit codes, environment variables, the credentials file
- [API reference](https://lakehousebox.com/docs/api/): every public route with method, path, auth, request and response fields and typed errors
- [Engines](https://lakehousebox.com/docs/engines/): DuckDB, PyIceberg and Spark recipes (verified), Trino and ClickHouse recipes (from the REST contract, not yet verified), Snowflake (data path not yet) and Databricks (untested), importing Parquet and CSV files, geometry columns, and the measured gotchas (bare bucket name for DuckDB, s3:// for PyIceberg, format version 2)
- [MCP server](https://lakehousebox.com/docs/mcp/): the account as MCP tools for Claude Desktop, Claude Code and other hosts (lhbox mcp install), one tool per REST capability, no query tool; the security model and today's token limitation
- [Self-hosting](https://lakehousebox.com/docs/self-hosting/): what a self-hosted LakehouseBox runs and what is missing

## Full text

- [llms-full.txt](https://lakehousebox.com/llms-full.txt): the whole documentation above as one plain-text file

## Journal

- [Why the world needs LakehouseBox](https://lakehousebox.com/blog/why-the-world-needs-lakehousebox/): Agents already have compute and tools. What they lack is a shared place to keep analytical data between sessions. Why we built that as a managed Apache Iceberg service, and why we ended up running the storage ourselves, in Germany.
- [Does your agent need a data warehouse?](https://lakehousebox.com/blog/does-your-agent-need-a-data-warehouse/): Start with the compute you already have. An agent running DuckDB and a set of shared Apache Iceberg tables are often enough to begin, and a managed warehouse remains the right choice for the workloads that need one.
- [Atom feed](https://lakehousebox.com/blog/feed.xml)

## Legal

- [Terms of Service](https://lakehousebox.com/legal/terms/): draft, version 2026-09-19-draft, must be accepted at signup
- [Privacy Policy](https://lakehousebox.com/legal/privacy/)
- [Acceptable Use Policy](https://lakehousebox.com/legal/aup/)
- [Data Processing Agreement](https://lakehousebox.com/legal/dpa/)
- [Security overview](https://lakehousebox.com/legal/security/): how tenants are isolated, credentials, encryption, backups, what is not done yet
- [Legal notice](https://lakehousebox.com/legal/legal-notice/)

## Optional

- [Sign up](https://lakehousebox.com/signup): name, email, organisation name and handle; the account is finished from the mail
- [Log in](https://lakehousebox.com/app/?login): email and password, then the account page at https://lakehousebox.com/app/<handle>; https://lakehousebox.com/app/forgot for a forgotten password; https://lakehousebox.com/app/device approves a `lhbox login` from a terminal
- [Recover a lost API key](https://lakehousebox.com/recover)
- [Your account](https://lakehousebox.com/app/): warehouses and your level on each, tokens for agents, members, usage, the organisation, and SQL with DuckDB in the browser
- [install.sh](https://lakehousebox.com/install.sh): the installer; downloads https://lakehousebox.com/cli/lhbox and verifies https://lakehousebox.com/cli/lhbox.sha256
- [security.txt](https://lakehousebox.com/.well-known/security.txt): security contact
- Support: hello@lakehousebox.com