runsonwhat

Amika's tech stack

What does Amika use?

Amika (amika.dev) uses at least 12 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Discord for customer support and PostHog for analytics. Last checked .

“Infra to build your own software factory”

Industry
Infrastructure
Size
1–10 employees
Based in
New York City, United States
LinkedIn
Company page
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Amika tech stack FAQ

What tools does Amika use?

We've found 12 tools at Amika (amika.dev). Edge & Hosting: Cloudflare and Vercel. Application: React, Tailwind CSS and Next.js. Data & Observability: web-vitals and PostHog. Go-to-market: Discord and Mintlify. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does Amika run on?

Amika uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.

What email provider does Amika use?

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

What does Amika use for customer support?

Amika uses Discord and Mintlify for customer support. We found Discord through website code.

What analytics tools does Amika use?

Amika uses PostHog for analytics. We found PostHog through website code.

Does Amika use Cloudflare?

Yes. We found Cloudflare at Amika through DNS records and website code. Cloudflare is used by 568,557 companies we track.

How does runsonwhat know what Amika uses?

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