secr's tech stack
What does secr use?
secr (secr.dev) uses at least 6 tools we can see from public records, including Vercel for hosting. Last checked .
“CLI-first secrets management for modern teams. Encrypt, sync, and inject environment variables without writing them to disk.”
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Houston, United States
- Founded
- 2021
- Company page
- Tools found
- 6
- Categories
- 4
- Layers
- 3 of 5
- Last checked
- Oct 2026
secr'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
3 tools, where the bytes are served from
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Go-to-market
1 tool, how they find and keep customers
Marketing
secr tech stack FAQ
What tools does secr use?
As of November 2026, runsonwhat has found 6 tools at secr (secr.dev) in public records. Edge & Hosting: Vercel, IONOS and Render. Application: Next.js. Last checked October 29, 2026.
What cloud does secr run on?
secr uses Vercel for hosting and cloud infrastructure, alongside IONOS and Render, according to runsonwhat (November 2026). runsonwhat found Vercel through a subdomain that points at Vercel and a DNS verification record. Vercel is used by 51,520 companies runsonwhat tracks.
Does secr use Next.js?
Yes. runsonwhat found Next.js at secr through Next.js code on secr.dev. Next.js is a Frontend tool used by 69,229 companies runsonwhat tracks.
Which companies have a tech stack similar to secr's?
The companies with the stacks most like secr's are Noona, Rts Reliable Tax Service, Rojkind Inmobiliaria, SA de CV and Tecnoweb Informática, according to runsonwhat (November 2026). Each shares 1 to 4 tools with secr, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what secr uses?
runsonwhat reads public records only. Of the 6 tools at secr, 2 were found through subdomains that point at the vendor, 1 through DNS records, 1 through website configuration files, 1 through code on secr.dev and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and secr.dev 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.