Inkbox's tech stack
What does Inkbox use?
Inkbox (inkbox.ai) uses at least 13 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, LinkedIn for marketing and Clerk for sign-in. Last checked .
“The identity and communication layer for AI agents”
- Industry
- Infrastructure
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Company page
- Tools found
- 13
- Categories
- 10
- Oldest proven tool
- Mar 2026
- Last checked
- Oct 2026
Inkbox'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
CDN & Edge
Application
4 tools, what the product is built with
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
What changed at Inkbox
Inkbox tech stack FAQ
What tools does Inkbox use?
We've found 13 tools at Inkbox (inkbox.ai). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Anthropic, Next.js and Clerk. Data & Observability: Google Analytics, web-vitals and PostHog. Go-to-market: LinkedIn Insight Tag and LinkedIn. Company Ops: Google Workspace. Last checked October 2, 2026.
What email provider does Inkbox use?
Inkbox uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Inkbox use?
Inkbox uses Google Analytics and PostHog for analytics. We found Google Analytics through website code.
What marketing software does Inkbox use?
Inkbox uses LinkedIn for marketing. We found LinkedIn through DNS verification records.
Does Inkbox use Google Workspace?
Yes. We found Google Workspace at Inkbox through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Inkbox uses?
We read public traces only: Inkbox'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.