Make: Community's tech stack
What does Make: Community use?
Make: Community (makezine.com) uses at least 32 tools we can see from public records, including WP Engine for hosting, Google Workspace for email and documents, Discord for customer support and Google Analytics for analytics. Last checked .
- Size
- 1–10 employees
- Based in
- Sebastopol, United States
- Company page
- Tools found
- 32
- Categories
- 13
- Oldest proven tool
- Aug 2022
- Last checked
- Oct 2026
Make: Community'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
Hosting & Cloud
CDN & Edge
Application
7 tools, what the product is built with
Frontend
Auth & Identity
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
18 tools, how they find and keep customers
Marketing
Ads & Pixels
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
What changed at Make: Community
Make: Community tech stack FAQ
What tools does Make: Community use?
As of November 2026, runsonwhat has found 32 tools at Make: Community (makezine.com) in public records. Edge & Hosting: Cloudflare and WP Engine. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Pingdom. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: Google Workspace and reCAPTCHA. Last checked October 31, 2026.
What cloud does Make: Community run on?
Make: Community uses WP Engine for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found WP Engine through a subdomain that points at WP Engine, and Make: Community has used it since at least August 2022. WP Engine is used by 51,736 companies runsonwhat tracks.
What email provider does Make: Community use?
Make: Community uses Google Workspace for email and office software, according to runsonwhat (November 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on makezine.com. Google Workspace is used by 410,390 companies runsonwhat tracks.
What does Make: Community use for customer support?
Make: Community uses Discord for customer support and documentation, according to runsonwhat (November 2026). runsonwhat found Discord through Discord code on makezine.com. Discord is used by 6,987 companies runsonwhat tracks.
What analytics tools does Make: Community use?
Make: Community uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on makezine.com. Google Analytics is used by 905,789 companies runsonwhat tracks.
What is Make: Community's website built with?
Make: Community uses WordPress for its website, alongside Yoast SEO, Shopify and Substack, according to runsonwhat (November 2026). runsonwhat found WordPress through WordPress code on makezine.com. WordPress is used by 606,601 companies runsonwhat tracks.
How long has Make: Community used WP Engine?
Make: Community has used WP Engine since at least August 2022, going by the first public certificate of the makezine.com subdomain that points at WP Engine. Other long-running tools at Make: Community include Auth0 (since March 2025).
Does Make: Community use jQuery?
Yes. runsonwhat found jQuery at Make: Community through jQuery code on makezine.com. jQuery is a Frontend tool used by 929,733 companies runsonwhat tracks.
Which companies have a tech stack similar to Make: Community's?
The companies with the stacks most like Make: Community's are GTMstudio, Evernomic, Fundora and Taro, according to runsonwhat (November 2026). Each shares 5 to 9 tools with Make: Community, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what Make: Community uses?
runsonwhat reads public records only. Of the 32 tools at Make: Community, 22 were found through code on makezine.com, 4 through website configuration files, 3 through DNS records, 2 through subdomains that point at the vendor and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and makezine.com 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.