runsonwhat

Brightbytes's tech stack

What does Brightbytes use?

Brightbytes (brightbytes.net) uses at least 9 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Zendesk for customer support and Squarespace for its website. Last checked .

Industry
Education Management
Size
51–200 employees
Based in
San Francisco, United States
Founded
2012
LinkedIn
Company page
Tools found
9
Categories
7
Layers
3 of 5
Last checked
Oct 2026

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

Go-to-market

3 tools, how they find and keep customers

Website & CMS

Support & Docs

Company Ops

5 tools, what the team runs on day to day

Brightbytes tech stack FAQ

What tools does Brightbytes use?

We've found 9 tools at Brightbytes (brightbytes.net). Edge & Hosting: Google Cloud. Go-to-market: Zendesk and Squarespace. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 6, 2026.

What cloud does Brightbytes run on?

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

What email provider does Brightbytes use?

Brightbytes uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What does Brightbytes use for customer support?

Brightbytes uses Zendesk for customer support. We found Zendesk through custom domain and email records.

What CMS does Brightbytes use?

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

Does Brightbytes use Microsoft 365?

Yes. We found Microsoft 365 at Brightbytes through DNS verification records. Microsoft 365 is used by 685,713 companies we track.

How does runsonwhat know what Brightbytes uses?

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