Djingr's tech stack
What does Djingr use?
Djingr (djingr.com) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Amazon CloudFront for content delivery and Amazon SES for email delivery. Last checked .
“Djingr is a B2B cross-border payments company. It uses the Bitcoin Lightning Network as settlement rails to move money between countries in about a minute, at fees starting from 0.8%, with no pre-funded accounts required in any market. Customers and their end users transact in ordinary fiat currency”
- Industry
- Fintech
- Size
- 1–10 employees
- Based in
- Cape Town, South Africa
- Founded
- 2024
- Company page
- Tools found
- 8
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Djingr'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
DNS
Application
2 tools, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Djingr tech stack FAQ
What tools does Djingr use?
We've found 8 tools at Djingr (djingr.com). Edge & Hosting: GoDaddy and Amazon CloudFront. Application: Google Fonts. Data & Observability: Google Analytics. Company Ops: Google Workspace and Amazon SES. Last checked October 4, 2026.
What email provider does Djingr use?
Djingr uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Djingr use?
Djingr uses Google Analytics for analytics. We found Google Analytics through website code.
Does Djingr use Google Workspace?
Yes. We found Google Workspace at Djingr through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Djingr uses?
We read public traces only: Djingr'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.