runsonwhat

OpenVector's tech stack

What does OpenVector use?

OpenVector (openvector.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, PostHog for analytics and web-vitals for monitoring. Last checked .

“Connect any video stream to the frontier vision-language models, optimized for real-time understanding. Video inference as low as 50ms.”

Industry
Infrastructure
Size
1–10 employees
Based in
San Francisco, United States
LinkedIn
Company page
Tools found
10
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

OpenVector tech stack FAQ

What tools does OpenVector use?

We've found 10 tools at OpenVector (openvector.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: GSAP, React and Next.js. Data & Observability: web-vitals and PostHog. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does OpenVector run on?

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

What email provider does OpenVector use?

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

What analytics tools does OpenVector use?

OpenVector uses PostHog for analytics. We found PostHog through website code.

Does OpenVector use Google Workspace?

Yes. We found Google Workspace at OpenVector through email records. Google Workspace is used by 235,409 companies we track.

How does runsonwhat know what OpenVector uses?

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