runsonwhat

lakeFS's tech stack

What does lakeFS use?

lakeFS (tilde.run) uses at least 10 tools we can see from public records, including HubSpot for sales, Plausible for analytics, WordPress for its website and Usercentrics for security. Last checked .

“lakeFS is the Control Plane for AI-Ready Data that bridges the data Infrastructure gap for AI. Ensure AI data governance, make AI training and agent runs reproducible, reduce access friction.”

LinkedIn
Company page
Tools found
10
Categories
9
Layers
5 of 5
Last checked
Oct 2026

lakeFS's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Edge & Hosting

1 tool, where the bytes are served from

Application

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Flags & Experiments

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

lakeFS tech stack FAQ

What tools does lakeFS use?

We've found 10 tools at lakeFS (tilde.run). Edge & Hosting: Amazon Route 53. Application: jQuery and Vimeo. Data & Observability: VWO and Plausible. Go-to-market: WordPress, Yoast SEO and HubSpot. Company Ops: Usercentrics. Last checked October 2, 2026.

What CRM does lakeFS use?

lakeFS uses HubSpot for sales and CRM. We found HubSpot through website code.

What analytics tools does lakeFS use?

lakeFS uses Plausible for analytics. We found Plausible through website code.

What CMS does lakeFS use?

lakeFS uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does lakeFS use jQuery?

Yes. We found jQuery at lakeFS through website code. jQuery is used by 105,350 companies we track.

How does runsonwhat know what lakeFS uses?

We read public traces only: lakeFS's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.