SpineOS's tech stack
What does SpineOS use?
SpineOS (spinestudio.dev) uses at least 6 tools we can see from public records, including OVHcloud for hosting, web-vitals for monitoring and Resend for email delivery. Last checked .
“Bureaux cloud pour agents IA. Chaque agent reçoit un vrai bureau cloud, persistant et sécurisé, piloté depuis Mission Control.”
- Based in
- France
- Tools found
- 6
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
SpineOS'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
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
1 tool, what the team runs on day to day
Email Delivery
SpineOS tech stack FAQ
What tools does SpineOS use?
As of October 2026, runsonwhat has found 6 tools at SpineOS (spinestudio.dev) in public records. Edge & Hosting: OVHcloud. Application: Next.js. Data & Observability: web-vitals. Company Ops: Resend. Last checked October 20, 2026.
What cloud does SpineOS run on?
SpineOS uses OVHcloud for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found OVHcloud through email records that authorize OVHcloud and DNS records. OVHcloud is used by 27,038 companies runsonwhat tracks.
What monitoring tools does SpineOS use?
SpineOS uses web-vitals for monitoring, according to runsonwhat (October 2026). runsonwhat found web-vitals through web-vitals code on spinestudio.dev. web-vitals is used by 29,139 companies runsonwhat tracks.
Does SpineOS use Next.js?
Yes. runsonwhat found Next.js at SpineOS through Next.js code on spinestudio.dev. Next.js is a Frontend tool used by 67,383 companies runsonwhat tracks.
How does runsonwhat know what SpineOS uses?
runsonwhat reads public records only. Of the 6 tools at SpineOS, 2 were found through code on spinestudio.dev, 2 through email records, 1 through DNS records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and spinestudio.dev 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.