secr review
A focused, CLI-first secrets platform with scanning, runtime injection, and team controls.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
secr is a CLI-first secrets management platform for development teams that need centralized storage, environment separation, credential scanning, and controlled access. It encrypts application secrets with AES-256-GCM envelope encryption and KMS-wrapped project keys, then injects values into processes without requiring local .env files. Teams can manage development, staging, and production environments through the web dashboard, CLI, REST API, SDKs, and integrations. Its open-source status, AI-agent credentials, and machine-token support also make it relevant to teams managing both human and non-human access.
Pricing is structured around a free plan and three paid tiers. Free costs $0 per organization per month and includes 3 projects, 100 secrets, 1 AI agent, version history, secret promotion, development and staging environments, and a 7-day audit log. Pro costs $6 per user per month and adds unlimited projects and secrets, rollback, webhooks, all environments plus 5 custom environments, a 30-day audit log, CI/CD integrations, machine tokens, and agent identities. Team costs $14 per user per month and adds 20 custom environments, a 90-day audit log, Git secret scanning, priority support, and NHI governance and compliance. Enterprise adds SSO, SCIM, MFA and passkey enforcement, 365-day audit retention, dedicated infrastructure, SLA, and onboarding.
The integration surface is practical for developer workflows, covering GitHub Actions, Vercel, Netlify, Terraform, Node.js/TypeScript, Python, Go, VS Code, Postman, MCP, Render, Heroku, Supabase, Railway, and AWS Parameter Store and Secrets Manager. Role-based access control includes environment-level scoping, while immutable audit logs cover secret and administrative events. secr suits teams prioritizing scanning, CI/CD injection, versioning, and machine access. Teams centered on automated rotation, dynamic short-lived application credentials, or Kubernetes workflows should consider alternatives with those capabilities clearly established.
secr pros and cons
- Where it wins
- Runtime injection avoids writing secrets to .env files
- Credential scanning covers 20+ patterns with pre-commit protection
- Machine tokens and scoped AI-agent credentials support automation
- Where it doesn't
- Free plan is limited to 3 projects and 100 secrets
- Automated application-secret rotation is not a documented feature
- Kubernetes integration and dynamic credentials are not documented
secr fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update