Connector

Your storage, our processing

For teams whose answer to “where does the data live” has to be “in our own account”, DataLens reads from and writes back to object storage you control.

How it works

Bring your own lake

Point the platform at storage you own. Processed output is routed back there rather than accumulating in ours.

Read and write

A lake is both a source and a destination — land from it, publish back to it.

Common formats

The columnar and delimited formats a lake actually holds, read directly rather than through an export step.

Same catalogue

A lake-backed dataset is profiled, transformed, governed and published exactly like any other.

What happens after it lands

Once rows are in the catalogue, the connector that produced them stops mattering. The dataset is profiled, can be cleaned, modelled, put in a flow, governed and published exactly like every other dataset — which means switching how data arrives never means rebuilding what happens to it afterwards.

Questions about this connector

Does my data have to leave my account?

With bring-your-own-lake configured, processed data is written back to your storage. The platform reads what it needs to do the work you asked for.

Is bring-your-own-lake included in the free tier?

No — routing storage to a lake you own is a Pro capability.

Can I publish a data product back to the lake?

Yes. Publishing to your own storage is a supported delivery target alongside links and the API.

See it on your own data

DataLens is in private beta. Bring a file, a database or an API and work through the whole lifecycle in one sitting.

Request beta access