runsonwhat

LifeOS's tech stack

What does LifeOS use?

LifeOS (venturis13lifeos.com) uses at least 15 tools we can see from public records, including DigitalOcean for hosting, Google Workspace for email and documents, Stripe for payments and Shopify for its website. Last checked .

Industry
E-commerce
Based in
United States
Founded
2025
Tools found
15
Categories
12
Layers
4 of 5
Last checked
Oct 2026

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

2 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

6 tools, what the product is built with

Backend & Database

Payments & Billing

Media & UI

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

LifeOS tech stack FAQ

What tools does LifeOS use?

We've found 15 tools at LifeOS (venturis13lifeos.com). Edge & Hosting: Cloudflare and DigitalOcean. Application: YouTube, Anthropic and OpenAI. Go-to-market: Brevo, Shopify and TikTok Pixel. Company Ops: Google Workspace and Make. Last checked October 4, 2026.

What cloud does LifeOS run on?

LifeOS uses DigitalOcean for hosting. We found DigitalOcean through subprocessor list.

What email provider does LifeOS use?

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

What payment provider does LifeOS use?

LifeOS uses Stripe for payments. We found Stripe through subprocessor list.

What CMS does LifeOS use?

LifeOS uses Shopify for its website. We found Shopify through subprocessor list.

What marketing software does LifeOS use?

LifeOS uses Brevo for marketing. We found Brevo through DNS verification records, email records and subprocessor list.

Does LifeOS use Cloudflare?

Yes. We found Cloudflare at LifeOS through DNS records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what LifeOS uses?

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