runsonwhat

CodesSavvy's tech stack

What does CodesSavvy use?

CodesSavvy (codessavvy.com) uses at least 10 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics, Resend for email delivery and Let's Encrypt for security. Last checked .

“A full-range software, AI, growth and security agency: custom web and mobile apps, SaaS, AI features and agents, workflow automation, DevOps, cybersecurity, SEO, paid ads and social media, plus ongoing maintenance. Senior engineers, fixed price, clients worldwide.”

Industry
IT Services
Size
1–10 employees
Based in
Karachi, Pakistan
Founded
2024
LinkedIn
Company page
Tools found
10
Categories
7
Layers
5 of 5
Last checked
Oct 2026

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

Hosting & Cloud

Application

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

CodesSavvy tech stack FAQ

What tools does CodesSavvy use?

We've found 10 tools at CodesSavvy (codessavvy.com). Edge & Hosting: Vercel. Application: Next.js. Data & Observability: Google Analytics. Company Ops: Let's Encrypt, Sectigo and Google Trust Services. Last checked October 4, 2026.

What cloud does CodesSavvy run on?

CodesSavvy uses Vercel for hosting. We found Vercel through DNS records.

What analytics tools does CodesSavvy use?

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

Does CodesSavvy use Google Analytics?

Yes. We found Google Analytics at CodesSavvy through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what CodesSavvy uses?

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