runsonwhat

CommandPost's tech stack

What does CommandPost use?

CommandPost (getcommandpost.com) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Marketing and Advertising
Size
11–50 employees
Based in
New York, United States
Founded
2009
LinkedIn
Company page
Tools found
13
Categories
7
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

5 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

CommandPost tech stack FAQ

What tools does CommandPost use?

We've found 13 tools at CommandPost (getcommandpost.com). Edge & Hosting: GoDaddy, Amazon Web Services and WP Engine. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Clicky. Go-to-market: WordPress and Yoast SEO. Company Ops: Google Workspace. Last checked October 6, 2026.

What cloud does CommandPost run on?

CommandPost uses Amazon Web Services and WP Engine for hosting. We found Amazon Web Services through custom domain.

What email provider does CommandPost use?

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

What analytics tools does CommandPost use?

CommandPost uses Google Analytics and Clicky for analytics. We found Google Analytics through website code.

What CMS does CommandPost use?

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

Does CommandPost use jQuery?

Yes. We found jQuery at CommandPost through website code. jQuery is used by 688,597 companies we track.

How does runsonwhat know what CommandPost uses?

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