runsonwhat

ISPConfig's tech stack

What does ISPConfig use?

ISPConfig (ispconfig.org) uses at least 6 tools we can see from public records, including Amazon SES for email delivery, Amazon Web Services for hosting, WordPress for its website and Cloudflare for content delivery. Last checked .

Size
1–10 employees
Based in
Lüneburg, Germany
LinkedIn
Company page
Tools found
6
Categories
5
Layers
4 of 5
Last checked
Nov 2026

ISPConfig's stack, layer by layer

Of 6 tools, 4 came from website code, 1 from DNS records and 1 from email records. 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

Application

1 tool, what the product is built with

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Email Delivery

ISPConfig tech stack FAQ

What tools does ISPConfig use?

As of November 2026, runsonwhat has found 6 tools at ISPConfig (ispconfig.org) in public records. Edge & Hosting: Cloudflare and Amazon Web Services. Application: jQuery. Go-to-market: WordPress and Yoast SEO. Company Ops: Amazon SES. Last checked November 15, 2026.

What cloud does ISPConfig run on?

ISPConfig uses Amazon Web Services for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found Amazon Web Services through Amazon Web Services code on ispconfig.org. Amazon Web Services is used by 148,189 companies runsonwhat tracks.

What is ISPConfig's website built with?

ISPConfig uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (November 2026). runsonwhat found WordPress through WordPress code on ispconfig.org. WordPress is used by 604,998 companies runsonwhat tracks.

Does ISPConfig use jQuery?

Yes. runsonwhat found jQuery at ISPConfig through jQuery code on ispconfig.org. jQuery is a Frontend tool used by 920,298 companies runsonwhat tracks.

How does runsonwhat know what ISPConfig uses?

runsonwhat reads public records only. Of the 6 tools at ISPConfig, 4 were found through code on ispconfig.org, 1 through DNS records and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and ispconfig.org about 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.