runsonwhat

API Restauration's tech stack

What does API Restauration use?

API Restauration (api-restauration.com) uses at least 16 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and SendGrid for email delivery. Last checked .

Based in
France
LinkedIn
Company page
Tools found
16
Categories
11
Layers
5 of 5
Last checked
Oct 2026

API Restauration'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

1 tool, where the bytes are served from

Application

6 tools, what the product is built with

Data & Observability

2 tools, 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

Collaboration

Finance & Legal

API Restauration tech stack FAQ

What tools does API Restauration use?

We've found 16 tools at API Restauration (api-restauration.com). Edge & Hosting: Gandi. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Matomo. Go-to-market: WordPress. Company Ops: Google Workspace, SendGrid and Mailgun. Last checked October 4, 2026.

What email provider does API Restauration use?

API Restauration uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does API Restauration use?

API Restauration uses Google Analytics and Matomo for analytics. We found Google Analytics through website code.

What CMS does API Restauration use?

API Restauration uses WordPress for its website. We found WordPress through website code.

Does API Restauration use Google Workspace?

Yes. We found Google Workspace at API Restauration through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what API Restauration uses?

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