runsonwhat

Biokript's tech stack

What does Biokript use?

Biokript (biokript.com) uses at least 10 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, tawk.to for customer support and Google Analytics for analytics. Last checked .

Industry
Financial Services
Size
11–50 employees
Based in
Glendale, United States
Founded
2017
LinkedIn
Company page
Tools found
10
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

Biokript tech stack FAQ

What tools does Biokript use?

We've found 10 tools at Biokript (biokript.com). Edge & Hosting: GoDaddy and Vercel. Application: YouTube, Adobe Fonts and Next.js. Data & Observability: Google Analytics. Go-to-market: tawk.to. Company Ops: Microsoft 365 and Google Workspace. Last checked October 6, 2026.

What cloud does Biokript run on?

Biokript uses Vercel for hosting. We found Vercel through DNS records and website code.

What email provider does Biokript use?

Biokript uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through email records.

What does Biokript use for customer support?

Biokript uses tawk.to for customer support. We found tawk.to through website code.

What analytics tools does Biokript use?

Biokript uses Google Analytics for analytics. We found Google Analytics through website code.

Does Biokript use Microsoft 365?

Yes. We found Microsoft 365 at Biokript through email records. Microsoft 365 is used by 685,727 companies we track.

How does runsonwhat know what Biokript uses?

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