Akendi UX — London Office's tech stack
What does Akendi UX — London Office use?
Akendi UX — London Office (akendi.com) uses at least 16 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Stripe for payments and WordPress for its website. Last checked .
- Industry
- Design
- Size
- 11–50 employees
- Based in
- London, United Kingdom
- Founded
- 2007
- Company page
- Tools found
- 16
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Akendi UX — London Office'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
1 tool, where the bytes are served from
DNS
Application
8 tools, what the product is built with
Frontend
Payments & Billing
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Workspace
Finance & Legal
Akendi UX — London Office tech stack FAQ
What tools does Akendi UX — London Office use?
As of November 2026, runsonwhat has found 16 tools at Akendi UX — London Office (akendi.com) in public records. Edge & Hosting: GoDaddy. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress, Ahrefs and MailerLite. Company Ops: Microsoft 365 and Uber for Business. Last checked October 30, 2026.
What email provider does Akendi UX — London Office use?
Akendi UX — London Office uses Microsoft 365 for email and office software, according to runsonwhat (November 2026). runsonwhat found Microsoft 365 through email records that authorize Microsoft 365 and code on akendi.com. Microsoft 365 is used by 720,957 companies runsonwhat tracks.
What payment provider does Akendi UX — London Office use?
Akendi UX — London Office uses Stripe for payments and billing, according to runsonwhat (November 2026). runsonwhat found Stripe through a DNS verification record for Stripe and code on akendi.com. Stripe is used by 30,970 companies runsonwhat tracks.
What analytics tools does Akendi UX — London Office use?
Akendi UX — London Office uses Google Analytics for analytics, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on akendi.com. Google Analytics is used by 905,966 companies runsonwhat tracks.
What is Akendi UX — London Office's website built with?
Akendi UX — London Office uses WordPress for its website, according to runsonwhat (November 2026). runsonwhat found WordPress through WordPress code on akendi.com. WordPress is used by 607,143 companies runsonwhat tracks.
What marketing software does Akendi UX — London Office use?
Akendi UX — London Office uses Ahrefs for marketing, alongside MailerLite, according to runsonwhat (November 2026). runsonwhat found Ahrefs through Ahrefs code on akendi.com. Ahrefs is used by 23,994 companies runsonwhat tracks.
Does Akendi UX — London Office use jQuery?
Yes. runsonwhat found jQuery at Akendi UX — London Office through jQuery code on akendi.com. jQuery is a Frontend tool used by 929,928 companies runsonwhat tracks.
Does Akendi UX — London Office use AI tools?
Yes. runsonwhat has found Anthropic and OpenAI at Akendi UX — London Office; Anthropic, for example, through a DNS verification record for Anthropic. AI services called only from servers leave no public trace, so Akendi UX — London Office may use more AI tools than these.
Which companies have a tech stack similar to Akendi UX — London Office's?
The companies with the stacks most like Akendi UX — London Office's are Futura, Menos ruido. Más impacto., Bizpoke Intelig and Aerlytix, according to runsonwhat (November 2026). Each shares 3 to 6 tools with Akendi UX — London Office, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what Akendi UX — London Office uses?
runsonwhat reads public records only. Of the 16 tools at Akendi UX — London Office, 7 were found through code on akendi.com, 7 through DNS records, 1 through email records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and akendi.com about 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.