runsonwhat

CreatorDB's tech stack

What does CreatorDB use?

CreatorDB (creatordb.app) uses at least 16 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Calendly for sales and Mintlify for customer support. Last checked .

“Global creator data platform and influencer marketing agency, with deep Asia expertise. Provides data-driven creator talent selection, campaign management, and a real-time creator analytics API covering 30M+ YouTube, Instagram, and TikTok profiles.”

Industry
Marketing and Advertising
Size
51–200 employees
Based in
Taipei, Taiwan
Founded
2021
LinkedIn
Company page
Tools found
16
Categories
13
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

CreatorDB tech stack FAQ

What tools does CreatorDB use?

As of October 2026, runsonwhat has found 16 tools at CreatorDB (creatordb.app) in public records. Edge & Hosting: GoDaddy, Google Cloud and Fastly. Application: Google Fonts, Firebase and MCP Registry. Data & Observability: Google Analytics. Go-to-market: Brevo, Calendly and Reddit Ads. Company Ops: Google Workspace and Vanta. Last checked October 7, 2026.

What cloud does CreatorDB run on?

CreatorDB uses Google Cloud for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Google Cloud through Google Cloud code on creatordb.app. Google Cloud is used by 74,986 companies runsonwhat tracks.

What sales tools does CreatorDB use?

The sales tools runsonwhat has found at CreatorDB are Calendly (October 2026); no CRM shows up in CreatorDB's public records. runsonwhat found Calendly through Calendly code on creatordb.app. Calendly is used by 24,288 companies runsonwhat tracks.

What email provider does CreatorDB use?

CreatorDB uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on creatordb.app. Google Workspace is used by 396,641 companies runsonwhat tracks.

What does CreatorDB use for customer support?

CreatorDB uses Mintlify for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Mintlify through a subdomain that points at Mintlify. Mintlify is used by 1,082 companies runsonwhat tracks.

What analytics tools does CreatorDB use?

CreatorDB uses Google Analytics for analytics, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on creatordb.app. Google Analytics is used by 850,248 companies runsonwhat tracks.

Does CreatorDB use Google Fonts?

Yes. runsonwhat found Google Fonts at CreatorDB through Google Fonts code on creatordb.app. Google Fonts is a Media & UI tool used by 789,728 companies runsonwhat tracks.

Does CreatorDB use AI tools?

Yes. runsonwhat has found MCP Registry at CreatorDB; MCP Registry, for example, through a DNS verification record for MCP Registry. AI services called only from servers leave no public trace, so CreatorDB may use more AI tools than these.

Which companies have a tech stack similar to CreatorDB's?

The companies with the stacks most like CreatorDB's are Rootly, Kajabi, Tenderly and Honeycomb, according to runsonwhat (October 2026). Each shares 6 to 8 tools with CreatorDB, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what CreatorDB uses?

runsonwhat reads public records only. Of the 16 tools at CreatorDB, 6 were found through DNS records, 5 through code on creatordb.app, 3 through subdomains that point at the vendor, 1 through email records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and creatordb.app 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.