# What does Jeli Post-Incident Reviews use?

Jeli Post-Incident Reviews (jeli.io) shows public evidence of 20 tools, according to runsonwhat (last checked 2026-11-15).

- Industry: Software
- Size: 11–50 employees
- Based in: San Francisco, United States
- Founded: 2019
- LinkedIn: https://www.linkedin.com/company/pagerduty

## Edge & Hosting

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Cloudflare](https://www.runsonwhat.com/reverse/cloudflare) | CDN & Edge | Website code |  |
| [Amazon Route 53](https://www.runsonwhat.com/reverse/route53) | DNS | DNS records |  |
| [Vercel](https://www.runsonwhat.com/reverse/vercel) | Hosting & Cloud | Custom domain | 2020-10 |

## Application

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Next.js](https://www.runsonwhat.com/reverse/nextjs) | Frontend | Website code |  |

## Data & Observability

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [VWO](https://www.runsonwhat.com/reverse/vwo) | Flags & Experiments | Website code |  |
| [Bugsnag](https://www.runsonwhat.com/reverse/bugsnag) | Monitoring | Website code |  |
| [Segment](https://www.runsonwhat.com/reverse/segment) | Analytics | Website code |  |

## Go-to-market

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [WordPress](https://www.runsonwhat.com/reverse/wordpress) | Website & CMS | Website code |  |
| [Webflow](https://www.runsonwhat.com/reverse/webflow) | Website & CMS | Custom domain, DNS verification records |  |
| [Demandbase](https://www.runsonwhat.com/reverse/demandbase) | Sales & CRM | Website code |  |
| [Marketo](https://www.runsonwhat.com/reverse/marketo) | Marketing | Website code |  |
| [Navattic](https://www.runsonwhat.com/reverse/navattic) | Marketing | Website code |  |

## Company Ops

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Microsoft 365](https://www.runsonwhat.com/reverse/microsoft-365) | Workspace | DNS verification records |  |
| [Google Workspace](https://www.runsonwhat.com/reverse/google-workspace) | Workspace | DNS verification records, Email records |  |
| [Apple Business](https://www.runsonwhat.com/reverse/apple) | Workspace | DNS verification records |  |
| [Atlassian](https://www.runsonwhat.com/reverse/atlassian) | Dev Tools | DNS verification records |  |
| [OneTrust](https://www.runsonwhat.com/reverse/onetrust) | Security & Compliance | Website code |  |
| [1Password](https://www.runsonwhat.com/reverse/1password) | Security & Compliance | DNS verification records |  |
| [Vanta](https://www.runsonwhat.com/reverse/vanta) | Security & Compliance | Custom domain | 2023-05 |

## FAQ

### What tools does Jeli Post-Incident Reviews use?

As of November 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 November 15, 2026.

### What cloud does Jeli Post-Incident Reviews run on?

Jeli Post-Incident Reviews uses Vercel for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found Vercel through a subdomain that points at Vercel, and Jeli Post-Incident Reviews has used it since at least October 2020. Vercel is used by 53,988 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 (November 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,780 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 (November 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365. Microsoft 365 is used by 739,180 companies runsonwhat tracks.

### What analytics tools does Jeli Post-Incident Reviews use?

Jeli Post-Incident Reviews uses Segment for analytics, according to runsonwhat (November 2026). runsonwhat found Segment through Segment code on jeli.io. Segment is used by 6,807 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 (November 2026). runsonwhat found WordPress through WordPress code on jeli.io. WordPress is used by 606,882 companies runsonwhat tracks.

### How long has Jeli Post-Incident Reviews used Vercel?

Jeli Post-Incident Reviews has used Vercel since at least October 2020, going by the first public certificate of the jeli.io subdomain that points at Vercel. Other long-running tools at Jeli Post-Incident Reviews include Vanta (since May 2023).

### 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 738,768 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 Thrive, Productboard, Alkira and Achievers, according to runsonwhat (November 2026). Each shares 9 to 13 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.


---

Source: runsonwhat, https://www.runsonwhat.com/company/jeli.io (updated November 2026). Counts are companies with direct public evidence of the tool (DNS records, certificates, website code, a real-browser crawl, subprocessor lists), so they are lower bounds. Methodology: https://www.runsonwhat.com/methodology.
