runsonwhat

Sigstore's tech stack

What does Sigstore use?

Sigstore (sigstore.dev) uses at least 14 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Better Stack for monitoring and Let's Encrypt for security. Last checked .

Re-check liveVisit sigstore.dev
Tools found
14
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

Hosting & Cloud

Application

4 tools, what the product is built with

Frontend

Media & UI

Data & Observability

1 tool, what they measure and store

Monitoring

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

5 tools, what the team runs on day to day

Workspace

Dev Tools

Security & Compliance

Companies like Sigstore also use

Tools common among companies with a similar stack that we haven't found at Sigstore.

Companies with a stack like Sigstore's

Ranked by shared tools, with rare tools counting more.

Sigstore tech stack FAQ

What tools does Sigstore use?

We've found 14 tools at Sigstore (sigstore.dev). Edge & Hosting: Google Cloud, Netlify and GitHub Pages. Application: Google Fonts, Tailwind CSS and Vue.js. Data & Observability: Better Stack. Company Ops: Google Workspace, Let's Encrypt and Google Trust Services. Last checked October 7, 2026.

What cloud does Sigstore run on?

Sigstore uses Google Cloud, Netlify and GitHub Pages for hosting. We found Google Cloud through DNS records.

What email provider does Sigstore use?

Sigstore uses Google Workspace for email and documents. We found Google Workspace through email records and website code.

Does Sigstore use Google Fonts?

Yes. We found Google Fonts at Sigstore through website code. Google Fonts is used by 507,566 companies we track.

How does runsonwhat know what Sigstore uses?

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