runsonwhat

Bigollo's tech stack

What does Bigollo use?

Bigollo (bigollo.com) uses at least 8 tools we can see from public records, including Alibaba Cloud for hosting, Google Workspace for email and documents and Discord for customer support. Last checked .

Industry
Software
Size
51–200 employees
Based in
Shenzhen, China
LinkedIn
Company page
Re-check liveVisit bigollo.com
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

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

Go-to-market

4 tools, how they find and keep customers

Marketing

Ads & Pixels

Support & Docs

Company Ops

1 tool, what the team runs on day to day

Workspace

Companies like Bigollo also use

Tools common among companies with a similar stack that we haven't found at Bigollo.

Companies with a stack like Bigollo's

Ranked by shared tools, with rare tools counting more.

Bigollo tech stack FAQ

What tools does Bigollo use?

We've found 8 tools at Bigollo (bigollo.com). Edge & Hosting: Alibaba Cloud. Application: React and Next.js. Go-to-market: Meta Pixel, TikTok Pixel and Discord. Company Ops: Google Workspace. Last checked October 6, 2026.

What cloud does Bigollo run on?

Bigollo uses Alibaba Cloud for hosting. We found Alibaba Cloud through custom domain.

What email provider does Bigollo use?

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

What does Bigollo use for customer support?

Bigollo uses Discord for customer support. We found Discord through website code.

Does Bigollo use Google Workspace?

Yes. We found Google Workspace at Bigollo through email records. Google Workspace is used by 381,657 companies we track.

How does runsonwhat know what Bigollo uses?

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