We watched a teammate paste database credentials into a Slack channel. That was the last time. We built ConfigShield the next week.
Every developer knows the drill. You join a new project and someone sends you the .env file over Slack. Or email. Or — worst case — it's committed to the repo. API keys, database passwords, and production secrets floating around in plaintext.
Enterprise tools like HashiCorp Vault exist, but they cost a fortune and take days to set up. We needed something simpler: encrypt your secrets, share them safely with your team, track who accessed what, and pull them into your CI/CD pipeline with a single CLI command.
ConfigShield is a product of Obsidian Clad Labs LLC, a group of friends from Tennessee who build developer tools that solve real problems without enterprise pricing. Simple. Affordable. Always on your side.
“If your secrets are in a Slack channel, they're not secrets anymore. ConfigShield fixes that.”
Every secret is encrypted with Fernet (AES) at rest and in transit. Zero plaintext storage.
Pull secrets into your local environment or CI/CD pipeline with a single command.
Triple auth: JWT tokens, HTTP-only cookies, and API keys. Use what fits your workflow.
Import your existing .env files. Export back anytime. No lock-in.
Full audit log of who accessed which secret, when, and from where.
Secrets are scoped to projects. Each project has its own encryption and access controls.
25+
API Endpoints
AES
Fernet Encryption
3
Auth Methods
Free plan: 1 project, 25 secrets. No credit card required. 30-day money-back guarantee on Pro.
Try Free Now