runsonwhat

Jayride's tech stack

What does Jayride use?

Jayride (jayride.com) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

Industry
Internet
Size
51–200 employees
Based in
Sydney, Australia
Founded
2012
LinkedIn
Company page
Tools found
13
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Jayride'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

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Jayride tech stack FAQ

What tools does Jayride use?

We've found 13 tools at Jayride (jayride.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon CloudFront. Application: Tailwind CSS and SvelteKit. Data & Observability: Google Analytics. Go-to-market: Meta Pixel. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 7, 2026.

What cloud does Jayride run on?

Jayride uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What email provider does Jayride use?

Jayride uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.

What analytics tools does Jayride use?

Jayride uses Google Analytics for analytics. We found Google Analytics through website code.

Does Jayride use Microsoft 365?

Yes. We found Microsoft 365 at Jayride through DNS verification records, email records and website code. Microsoft 365 is used by 685,702 companies we track.

How does runsonwhat know what Jayride uses?

We read public traces only: Jayride'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.