Increase's tech stack
What does Increase use?
Increase (increase.com) uses at least 14 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and WorkOS for sign-in. Last checked .
“API-first banking for ambitious technology companies.”
- Industry
- Banking and Exchange
- Size
- 11–50 employees
- Based in
- Bend, United States
- Company page
- Tools found
- 14
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Increase'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
4 tools, what the product is built with
Data & Observability
4 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Increase tech stack FAQ
What tools does Increase use?
We've found 14 tools at Increase (increase.com). Edge & Hosting: Cloudflare and Google Cloud. Application: Tailwind CSS, Astro and WorkOS. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Google Ads and LinkedIn Insight Tag. Company Ops: Google Workspace. Last checked October 2, 2026.
What cloud does Increase run on?
Increase uses Google Cloud for hosting. We found Google Cloud through DNS records and website code.
What email provider does Increase use?
Increase uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does Increase use?
Increase uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Increase use Cloudflare?
Yes. We found Cloudflare at Increase through website code. Cloudflare is used by 428,012 companies we track.
How does runsonwhat know what Increase uses?
We read public traces only: Increase'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.