Roark's tech stack
What does Roark use?
Roark (roark.ai) uses at least 10 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Sentry for monitoring and Amazon CloudFront for content delivery. Last checked .
“Roark is the simulation testing and evals platform for voice AI agents. Simulate every scenario before launch, score every production call on audio-native metrics.”
- Industry
- Analytics
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2024
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Roark'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
4 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Roark tech stack FAQ
What tools does Roark use?
We've found 10 tools at Roark (roark.ai). Edge & Hosting: Amazon Route 53, Amazon CloudFront and Vercel. Application: Next.js. Data & Observability: Sentry. Company Ops: Microsoft 365, Google Workspace and Postmark. Last checked October 2, 2026.
What cloud does Roark run on?
Roark uses Vercel and Amazon Web Services for hosting. We found Vercel through custom domain.
What email provider does Roark use?
Roark uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
Does Roark use Microsoft 365?
Yes. We found Microsoft 365 at Roark through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Roark uses?
We read public traces only: Roark'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.