runsonwhat

SenexPay's tech stack

What does SenexPay use?

SenexPay (senexpay.com) uses at least 13 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Zoho for sales and Google Analytics for analytics. Last checked .

Industry
Fintech
Size
11–50 employees
Based in
Lagos, Nigeria
Founded
2016
LinkedIn
Company page
Tools found
13
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

SenexPay tech stack FAQ

What tools does SenexPay use?

We've found 13 tools at SenexPay (senexpay.com). Edge & Hosting: Cloudflare and Vercel. Application: Tailwind CSS, Vue.js and Nuxt. Data & Observability: Google Analytics and Sentry. Go-to-market: Zoho. Company Ops: Google Workspace, SendGrid and Mailjet. Last checked October 4, 2026.

What cloud does SenexPay run on?

SenexPay uses Vercel for hosting. We found Vercel through website code.

What CRM does SenexPay use?

SenexPay uses Zoho for sales and CRM. We found Zoho through custom domain, DNS verification records and email records.

What email provider does SenexPay use?

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

What analytics tools does SenexPay use?

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

Does SenexPay use Cloudflare?

Yes. We found Cloudflare at SenexPay through DNS records and website code. Cloudflare is used by 306,534 companies we track.

How does runsonwhat know what SenexPay uses?

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