A lakehouse should let you pick the right tool for the job. As of this winter, Databasin does that across three engines and counting, all reading the same open tables.
The lineup
- Trino is the federated SQL workhorse you already know
- Apache Spark brings clusters with notebooks and one-click wake, for ML and heavy processing (shipped late January)
- Python is first-class in the lakehouse for data science workflows
- DuckDB arrives today with an in-editor engine selector: blazing, lightweight analytics with nothing to manage
One lake underneath
Every engine queries the same data. No copies, no per-engine silos, no sync jobs. New clusters run on Apache Iceberg, the open table format, so nothing about your storage is proprietary.
The supporting cast matters too. Notebook automation (February 11) puts notebooks on schedules, and notebook sharing (February 15) makes them collaborative. New organizations pick their engine mix at setup through the multi-engine onboarding flow.
Update, June 2026: the lineup grew again — Apache Doris joined as engine number four.