runsonwhat

Jeli Post-Incident Reviews's tech stack

What does Jeli Post-Incident Reviews use?

Jeli Post-Incident Reviews (jeli.io) uses at least 20 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Demandbase for sales and Segment for analytics. Last checked .

Industry
Software
Size
11–50 employees
Based in
San Francisco, United States
Founded
2019
LinkedIn
Company page
Tools found
20
Categories
13
Layers
5 of 5
Last checked
Oct 2026

Jeli Post-Incident Reviews'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

3 tools, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Monitoring

Flags & Experiments

Go-to-market

6 tools, how they find and keep customers

Company Ops

7 tools, what the team runs on day to day

Jeli Post-Incident Reviews tech stack FAQ

What tools does Jeli Post-Incident Reviews use?

As of October 2026, runsonwhat has found 20 tools at Jeli Post-Incident Reviews (jeli.io) in public records. Edge & Hosting: Cloudflare, Amazon Route 53 and Vercel. Application: Next.js. Data & Observability: VWO, Bugsnag and Segment. Go-to-market: WordPress, Webflow and Demandbase. Company Ops: Microsoft 365, Google Workspace and Apple Business. Last checked October 17, 2026.

What cloud does Jeli Post-Incident Reviews run on?

Jeli Post-Incident Reviews uses Vercel for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Vercel through a subdomain that points at Vercel. Vercel is used by 47,088 companies runsonwhat tracks.

What sales tools does Jeli Post-Incident Reviews use?

The sales tools runsonwhat has found at Jeli Post-Incident Reviews are Demandbase (October 2026); no CRM shows up in Jeli Post-Incident Reviews' public records. runsonwhat found Demandbase through Demandbase code on jeli.io. Demandbase is used by 9,535 companies runsonwhat tracks.

What email provider does Jeli Post-Incident Reviews use?

Jeli Post-Incident Reviews uses Microsoft 365 for email and office software, alongside Google Workspace and Apple Business, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365. Microsoft 365 is used by 705,068 companies runsonwhat tracks.

What analytics tools does Jeli Post-Incident Reviews use?

Jeli Post-Incident Reviews uses Segment for analytics, according to runsonwhat (October 2026). runsonwhat found Segment through Segment code on jeli.io. Segment is used by 6,464 companies runsonwhat tracks.

What is Jeli Post-Incident Reviews's website built with?

Jeli Post-Incident Reviews uses WordPress for its website, alongside Webflow, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on jeli.io. WordPress is used by 585,732 companies runsonwhat tracks.

Does Jeli Post-Incident Reviews use Cloudflare?

Yes. runsonwhat found Cloudflare at Jeli Post-Incident Reviews through Cloudflare code on jeli.io. Cloudflare is a CDN & Edge tool used by 695,286 companies runsonwhat tracks.

Which companies have a tech stack similar to Jeli Post-Incident Reviews's?

The companies with the stacks most like Jeli Post-Incident Reviews' are Pylon, Maxio, Perplexity AI and Cline Bot, according to runsonwhat (October 2026). Each shares 8 to 11 tools with Jeli Post-Incident Reviews, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Jeli Post-Incident Reviews uses?

runsonwhat reads public records only. Of the 20 tools at Jeli Post-Incident Reviews, 10 were found through code on jeli.io, 7 through DNS records and 3 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and jeli.io about 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.