Treasury's tech stack
What does Treasury use?
Treasury (treasury.sh) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .
“An AI money coach and personal-finance command center that answers your money questions in plain English.”
- Industry
- Internet
- Size
- 1–10 employees
- Based in
- Seattle, United States
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Treasury'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
1 tool, where the bytes are served from
CDN & Edge
Application
2 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Treasury tech stack FAQ
What tools does Treasury use?
We've found 8 tools at Treasury (treasury.sh). Edge & Hosting: Cloudflare. Application: Tailwind CSS and SvelteKit. Data & Observability: Google Analytics. Go-to-market: Google Ads. Company Ops: Google Workspace and Amazon SES. Last checked October 2, 2026.
What email provider does Treasury use?
Treasury uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Treasury use?
Treasury uses Google Analytics for analytics. We found Google Analytics through website code.
Does Treasury use Cloudflare?
Yes. We found Cloudflare at Treasury through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Treasury uses?
We read public traces only: Treasury'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.