runsonwhat

Heartland Plant Innovations (HPI)'s tech stack

What does Heartland Plant Innovations (HPI) use?

Heartland Plant Innovations (HPI) (heartlandinnovations.com) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, WordPress for its website and Cloudflare for content delivery. Last checked .

“Advancing Plant Biotechnology via Research & Breeding”

Based in
United States
Founded
2009
Tools found
9
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Heartland Plant Innovations (HPI)'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

CDN & Edge

Application

5 tools, 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

Heartland Plant Innovations (HPI) tech stack FAQ

What tools does Heartland Plant Innovations (HPI) use?

We've found 9 tools at Heartland Plant Innovations (HPI) (heartlandinnovations.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress and All in One SEO. Company Ops: Google Workspace. Last checked October 3, 2026.

What email provider does Heartland Plant Innovations (HPI) use?

Heartland Plant Innovations (HPI) uses Google Workspace for email and documents. We found Google Workspace through email records.

What CMS does Heartland Plant Innovations (HPI) use?

Heartland Plant Innovations (HPI) uses WordPress and All in One SEO for its website. We found WordPress through website code.

Does Heartland Plant Innovations (HPI) use Cloudflare?

Yes. We found Cloudflare at Heartland Plant Innovations (HPI) through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Heartland Plant Innovations (HPI) uses?

We read public traces only: Heartland Plant Innovations (HPI)'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.