Timelaketimelake
DocsBenchmarksRoadmapSpecContribute
Apache 2.0 ·
Roadmap

DoneIn progressPlanned

Tables and storage

Done:1. Iceberg tablesDone:2. CommitsDone:3. Object-store catalogIn progress:4. Time-series table contractIn progress:5. File layout and encodingsIn progress:6. Last-value indexDone:7. One-request table state and version checksDone:8. Table format versions and upgradesDone:9. SettingsPlanned:10. Supplemental timestamps

Writing

Done:11. AppendsDone:12. Late data and dedup on readDone:13. Writes from WebAssemblyPlanned:14. Hot tier and seconds-fresh readsPlanned:15. BackfillIn progress:16. Import and migrationPlanned:17. DeletesPlanned:18. GDPR erasure

Maintenance

Done:19. CompactionIn progress:20. Maintenance runs, retention and expiry

Reading

In progress:21. Timelake readerDone:22. Block cacheDone:23. Filter pushdownDone:24. Pruning with long IN listsDone:25. Newest-first scansDone:26. Scans in series orderDone:27. Materialized rollups

SQL functions

In progress:28. Function libraryDone:29. Time buckets and gap fillingDone:30. Signal aggregatesDone:31. Downsampling with m4

Integrations

Planned:32. REST catalogPlanned:33. DuckDB extensionPlanned:34. Snowflake connectionPlanned:35. Multitenancy

Services

Planned:36. Ingestion and rulesPlanned:37. Data to eventsPlanned:38. Static read modelsPlanned:39. Computed metricsPlanned:40. Agent access with permission setsPlanned:41. Device syncPlanned:42. Edge gatewayPlanned:43. Server mode

Benchmarks

In progress:44. Benchmark harness: timebenchIn progress:45. Industrial IoT benchmarkPlanned:46. Agent benchmark

Background

ArchitectureDeployment and cost modelEmbedded engine: DataFusionLandscape and positioningLicense and open corePurpose and requirementsReleases
TimelaketimelakeThe open time-series lakehouse.
v0 · Apache 2.0 · Contribute · GitHubBuilt on Apache Arrow, Apache DataFusion, Apache Parquet, and Apache Iceberg.
DocsBenchmarksRoadmapSpecContribute

Spec 35 · Integrations

Multitenancy

PlannedUpdated 2026-10-16View on GitHub
Versions
Not released yet
Roadmap
Any engine can attach, Technical preview
Related
18. GDPR erasure, 40. Agent access with permission sets

Summary

Documented patterns for many tenants: a shared table with a tenant column, a namespace per tenant, or a bucket per tenant, with their isolation and cost, plus credential vending and per-tenant retention, rollups and quotas.

Design

Documented patterns with trade-offs and examples:

PatternIsolationCost / opsWhen
Shared table, tenant partition columnRow-level (enforced by catalog/engine policies)CheapestMany small tenants
Namespace per tenantCatalog-level ACLsLowTens to thousands of tenants
Warehouse/bucket per tenantIAM + per-tenant KMS keysHigherRegulated / enterprise tenants

Plus examples for credential vending via the REST catalog, per-tenant retention and rollups, and per-tenant ingestion quotas.

Open questions and issues

  • #141 Docs: a setup guide per object store
  • #142 Docs: recipes for common deployments

History

  • 2026-10-11: specified (SPEC.md §14)
  • 2026-10-19: moved from SPEC.md into its own spec.
  • 2026-10-19: was spec 29; specs regrouped one per feature, with milestones on the roadmap.