runsonwhat

Valo's tech stack

What does Valo use?

Valo (boundarylayer.tech) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Tag Manager for analytics and Squarespace for its website. Last checked .

“Cutting edge hydrofoil systems for boatbuilders”

Industry
Climate
Size
1–10 employees
Based in
San Francisco, United States
Tools found
10
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

Application

3 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Valo tech stack FAQ

What tools does Valo use?

We've found 10 tools at Valo (boundarylayer.tech). Edge & Hosting: Cloudflare and Google Cloud. Application: Google Fonts, Font Awesome and Firebase. Data & Observability: Google Tag Manager. Go-to-market: Squarespace. Company Ops: Microsoft 365 and Google Workspace. Last checked October 2, 2026.

What cloud does Valo run on?

Valo uses Google Cloud for hosting. We found Google Cloud through DNS records.

What email provider does Valo use?

Valo uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Valo use?

Valo uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

What CMS does Valo use?

Valo uses Squarespace for its website. We found Squarespace through custom domain and DNS records.

Does Valo use Microsoft 365?

Yes. We found Microsoft 365 at Valo through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Valo uses?

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