OwnLocal's tech stack
What does OwnLocal use?
OwnLocal (ownlocal.com) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Zendesk for customer support and Atlassian Statuspage for monitoring. Last checked .
“OwnLocal automates marketing for over 129,000 SMBs through 3,300…”
- Industry
- Marketing
- Size
- 11–50 employees
- Based in
- Austin, United States
- Founded
- 2010
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
OwnLocal'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
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
OwnLocal tech stack FAQ
What tools does OwnLocal use?
We've found 10 tools at OwnLocal (ownlocal.com). Edge & Hosting: Google Cloud and GitHub Pages. Data & Observability: Atlassian Statuspage. Go-to-market: Zendesk. Company Ops: Google Workspace, SendGrid and Mailchimp Transactional. Last checked October 2, 2026.
What cloud does OwnLocal run on?
OwnLocal uses Google Cloud and GitHub Pages for hosting. We found Google Cloud through custom domain and DNS records.
What email provider does OwnLocal use?
OwnLocal uses Google Workspace for email and documents. We found Google Workspace through email records.
What does OwnLocal use for customer support?
OwnLocal uses Zendesk for customer support. We found Zendesk through email records.
Does OwnLocal use Google Workspace?
Yes. We found Google Workspace at OwnLocal through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what OwnLocal uses?
We read public traces only: OwnLocal'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.