runsonwhat

Lieferando's tech stack

What does Lieferando use?

Lieferando (lieferando.de) uses at least 7 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Pardot for marketing and Cloudflare for content delivery. Last checked .

Based in
Germany
Re-check liveVisit lieferando.de
Tools found
7
Categories
6
Layers
3 of 5
Last checked
Oct 2026

Lieferando'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

2 tools, where the bytes are served from

CDN & Edge

DNS

Go-to-market

3 tools, how they find and keep customers

Marketing

Support & Docs

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Lieferando also use

Tools common among companies with a similar stack that we haven't found at Lieferando.

Companies with a stack like Lieferando's

Ranked by shared tools, with rare tools counting more.

Lieferando tech stack FAQ

What tools does Lieferando use?

We've found 7 tools at Lieferando (lieferando.de). Edge & Hosting: Cloudflare and Amazon Route 53. Go-to-market: Zendesk and Pardot. Company Ops: Google Workspace and Validity. Last checked October 3, 2026.

What email provider does Lieferando use?

Lieferando uses Google Workspace for email and documents. We found Google Workspace through email records.

What does Lieferando use for customer support?

Lieferando uses Zendesk for customer support. We found Zendesk through email records.

What marketing software does Lieferando use?

Lieferando uses Pardot for marketing. We found Pardot through DNS verification records.

Does Lieferando use Cloudflare?

Yes. We found Cloudflare at Lieferando through custom domain, DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Lieferando uses?

We read public traces only: Lieferando'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.