Margin's tech stack
What does Margin use?
Margin (usemargin.com) uses at least 14 tools we can see from public records, including Google Workspace for email and documents, Intercom for customer support, Stripe for payments and Webflow for its website. Last checked .
“POS & operating system that makes liquor stores more money”
- Industry
- Retail
- Size
- 1–10 employees
- Based in
- New York City, United States
- Company page
- Tools found
- 14
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
Margin'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
7 tools, what the product is built with
Frontend
Backend & Database
Payments & Billing
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Margin tech stack FAQ
What tools does Margin use?
We've found 14 tools at Margin (usemargin.com). Edge & Hosting: Cloudflare, Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and Vimeo. Go-to-market: Webflow and Intercom. Company Ops: Google Workspace and Valimail. Last checked October 2, 2026.
What email provider does Margin use?
Margin uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Margin use for customer support?
Margin uses Intercom for customer support. We found Intercom through email records.
What payment provider does Margin use?
Margin uses Stripe for payments. We found Stripe through custom domain.
What CMS does Margin use?
Margin uses Webflow for its website. We found Webflow through custom domain and website code.
Does Margin use jQuery?
Yes. We found jQuery at Margin through website code. jQuery is used by 577,881 companies we track.
How does runsonwhat know what Margin uses?
We read public traces only: Margin'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.