runsonwhat

api.video's tech stack

What does api.video use?

api.video (api.video) uses at least 28 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, HubSpot for sales and Zendesk for customer support. Last checked .

“api.video lets you quickly and securely deliver on-demand and live-stream videos directly from your website, software, or app.”

Industry
Software
Size
11–50 employees
Based in
Bordeaux, France
Founded
2019
LinkedIn
Company page
Tools found
28
Categories
16
Oldest proven tool
Apr 2018
Last checked
Oct 2026

api.video'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

4 tools, where the bytes are served from

Application

7 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

11 tools, what the team runs on day to day

What changed at api.video

Using since

Dates come from the first certificate of the subdomain that points at the tool.

  1. GitHub Pages
  2. Recruitee
  3. Atlassian Statuspage
  4. Auth0

api.video tech stack FAQ

What tools does api.video use?

As of October 2026, runsonwhat has found 28 tools at api.video (api.video) in public records. Edge & Hosting: Fastly, Vercel and OVHcloud. Application: Google Fonts, React and Adobe Fonts. Data & Observability: Atlassian Statuspage. Go-to-market: HubSpot, Zendesk and Freshdesk. Company Ops: Google Workspace, SendGrid and Atlassian. Last checked October 22, 2026.

What cloud does api.video run on?

api.video uses Vercel for hosting and cloud infrastructure, alongside OVHcloud and GitHub Pages, according to runsonwhat (October 2026). runsonwhat found Vercel through a subdomain that points at Vercel and DNS records. Vercel is used by 48,467 companies runsonwhat tracks.

What CRM does api.video use?

api.video uses HubSpot for its CRM, according to runsonwhat (October 2026). runsonwhat found HubSpot through email records that authorize HubSpot and code on api.video. HubSpot is used by 94,348 companies runsonwhat tracks.

What email provider does api.video use?

api.video uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on api.video. Google Workspace is used by 403,712 companies runsonwhat tracks.

What does api.video use for customer support?

api.video uses Zendesk for customer support and documentation, alongside Freshdesk and Chatwoot, according to runsonwhat (October 2026). runsonwhat found Zendesk through email records that authorize Zendesk and code on api.video. Zendesk is used by 42,048 companies runsonwhat tracks.

What payment provider does api.video use?

api.video uses Stripe for payments and billing, according to runsonwhat (October 2026). runsonwhat found Stripe through a DNS verification record for Stripe and code on api.video. Stripe is used by 28,729 companies runsonwhat tracks.

How long has api.video used GitHub Pages?

api.video has used GitHub Pages since at least April 2018, going by the first public certificate of the api.video subdomain that points at GitHub Pages. Other long-running tools at api.video include Recruitee (since February 2019), Atlassian Statuspage (since August 2019) and Auth0 (since September 2019).

Does api.video use Google Fonts?

Yes. runsonwhat found Google Fonts at api.video through Google Fonts code on api.video. Google Fonts is a Media & UI tool used by 812,819 companies runsonwhat tracks.

Which companies have a tech stack similar to api.video's?

The companies with the stacks most like api.video's are Buttercms 🧈, ioki, Omnisense and Adikteev, according to runsonwhat (October 2026). Each shares 4 to 9 tools with api.video, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what api.video uses?

runsonwhat reads public records only. Of the 28 tools at api.video, 10 were found through DNS records, 6 through code on api.video, 6 through subdomains that point at the vendor, 5 through email records and 1 through its own subprocessor list. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and api.video 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.