Lakekeeper · Rate Limits
Lakekeeper Rate Limits
Lakekeeper Rate Limits is the rate-limit profile for Lakekeeper on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the published and note response headers.
Tagged areas include Apache Iceberg, Data Catalog, Lakehouse, Open Source, and Rust.
0 Limits
publishednote
Transcribed from the provider's documentation on 2026-08-27 — docs.lakekeeper.io/docs/latest/configuration/, docs.lakek....
View Source
Limits
Lakekeeper publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Lakekeeper publishes NO rate limits and returns NO rate-limit response headers, and that is a property of the product rather than a documentation gap: it is self-hosted server software, so throughput is bounded by the operator's own Postgres, object store and pod count, not by a vendor quota. A full-text search of the published documentation corpus (llms-full.txt, 580KB) finds no X-RateLimit-*, no RateLimit-*, and no documented 429 response from Lakekeeper itself. Every 429 mentioned in the docs is one Lakekeeper RECEIVES from an upstream (Microsoft Graph, cloud STS/SAS endpoints) and retries with Retry-After — the client side, not the server side.
Apache IcebergData CatalogLakehouseOpen SourceRustData GovernanceAccess ControlObject StorageMetadataSelf-HostedopenfgaData Engineering
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.