Request Finance's tech stack
What does Request Finance use?
Request Finance (request.finance) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, HubSpot for sales, GitBook for customer support and Auth0 for sign-in. Last checked .
- Industry
- Financial Services
- Size
- 11–50 employees
- Based in
- Paris, France
- Founded
- 2020
- Company page
- Tools found
- 12
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Request Finance'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
CDN & Edge
Application
2 tools, what the product is built with
Auth & Identity
Backend & Database
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Request Finance tech stack FAQ
What tools does Request Finance use?
We've found 12 tools at Request Finance (request.finance). Edge & Hosting: Cloudflare and Amazon CloudFront. Application: Auth0 and MongoDB Atlas. Data & Observability: UptimeRobot. Go-to-market: HubSpot and GitBook. Company Ops: Google Workspace, SendGrid and Postmark. Last checked October 6, 2026.
What CRM does Request Finance use?
Request Finance uses HubSpot for sales and CRM. We found HubSpot through email records.
What email provider does Request Finance use?
Request Finance uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Request Finance use for customer support?
Request Finance uses GitBook for customer support. We found GitBook through custom domain.
Does Request Finance use Cloudflare?
Yes. We found Cloudflare at Request Finance through DNS records, email records and website code. Cloudflare is used by 567,972 companies we track.
How does runsonwhat know what Request Finance uses?
We read public traces only: Request Finance'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.