Axiora's tech stack
What does Axiora use?
Axiora (axiora.dev) uses at least 15 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Stripe for payments and Cloudflare for content delivery. Last checked .
“Developer infrastructure for Japanese financial data. Source-linked, LLM-ready financials, ownership data, and filings from EDINET, delivered via REST API and an MCP server.”
- Industry
- Financial Services
- Size
- 1–10 employees
- Based in
- Japan
- Founded
- 2026
- Company page
- Tools found
- 15
- Categories
- 11
- Layers
- 4 of 5
- Last checked
- Oct 2026
Axiora'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
Frontend
Backend & Database
Payments & Billing
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
7 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
Security & Compliance
Axiora tech stack FAQ
What tools does Axiora use?
We've found 15 tools at Axiora (axiora.dev). Edge & Hosting: Cloudflare, Vercel and Google Cloud. Application: Next.js, Stripe and Supabase. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.
What cloud does Axiora run on?
Axiora uses Vercel and Google Cloud for hosting. We found Vercel through website code and subprocessor list.
What email provider does Axiora use?
Axiora uses Google Workspace for email and documents. We found Google Workspace through email records.
What payment provider does Axiora use?
Axiora uses Stripe for payments. We found Stripe through subprocessor list.
Does Axiora use Cloudflare?
Yes. We found Cloudflare at Axiora through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Axiora uses?
We read public traces only: Axiora'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.