runsonwhat

AgReserves's tech stack

What does AgReserves use?

AgReserves (agreserves.com) uses at least 15 tools we can see from public records, including HPE GreenLake for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

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

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

Hosting & Cloud

Application

2 tools, what the product is built with

Media & UI

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

9 tools, what the team runs on day to day

AgReserves tech stack FAQ

What tools does AgReserves use?

We've found 15 tools at AgReserves (agreserves.com). Edge & Hosting: HPE GreenLake. Application: jQuery and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 3, 2026.

What cloud does AgReserves run on?

AgReserves uses HPE GreenLake for hosting. We found HPE GreenLake through DNS verification records.

What email provider does AgReserves use?

AgReserves uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does AgReserves use?

AgReserves uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does AgReserves use?

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

Does AgReserves use Microsoft 365?

Yes. We found Microsoft 365 at AgReserves through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what AgReserves uses?

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