runsonwhat

Vaultpay's tech stack

What does Vaultpay use?

Vaultpay (vaultpay.io) uses at least 5 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, ReadMe for customer support and Branch for marketing. Last checked .

“Digital banking platform for the 30 million smartphone users in DRC.”

Industry
Fintech
Size
1–10 employees
Based in
Kinshasa, Democratic Republic of the Congo
Founded
2023
LinkedIn
Company page
Tools found
5
Categories
4
Layers
3 of 5
Last checked
Oct 2026

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

Go-to-market

2 tools, how they find and keep customers

Marketing

Support & Docs

Company Ops

1 tool, what the team runs on day to day

Vaultpay tech stack FAQ

What tools does Vaultpay use?

We've found 5 tools at Vaultpay (vaultpay.io). Edge & Hosting: Google Cloud and Vercel. Go-to-market: ReadMe and Branch. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does Vaultpay run on?

Vaultpay uses Google Cloud and Vercel for hosting. We found Google Cloud through custom domain and DNS records.

What email provider does Vaultpay use?

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

What does Vaultpay use for customer support?

Vaultpay uses ReadMe for customer support. We found ReadMe through custom domain.

What marketing software does Vaultpay use?

Vaultpay uses Branch for marketing. We found Branch through custom domain.

Does Vaultpay use Google Workspace?

Yes. We found Google Workspace at Vaultpay through email records. Google Workspace is used by 175,552 companies we track.

How does runsonwhat know what Vaultpay uses?

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