Scott HanselmanManaging secrets with Onboardbase and Dante Lex
synopsis
Dante Lex, CEO of Onboardbase, argues that secrets management fails because the secure path is less convenient than the insecure one. His product therefore assumes developers will make mistakes and hides secrets from them, while making sharing and leak-catching automatic.
Positioning against Vault. Lex markets Onboardbase openly as a simpler, cheaper HashiCorp Vault. He likes Vault but says it needs dedicated security engineers, and that naming it brings in customers who already know what they want.
Why secrets leak. Lex blames convenience. Developers keep secrets in text files, Notion and Slack, and he has lived through a breach. His design target is a tool as easy as pasting into Slack.
Seeing nothing, sharing deliberately. In his account, secrets are injected in real time and stay invisible to engineers. Service tokens are scoped per environment, device tokens can be revoked, credentials rotate after a set number of uses or days, and shared secrets travel as links that self-delete minutes after viewing. He wants .env files gone.
SecureLog and assumed negligence. The new product scans console logging and React server components, then masks or strips leaked secrets before they reach production. Lex dismisses the worry that it breeds laziness: he says mistakes are certain. Hanselman calls this falling into "the pit of success".
Testing and friction. Lex says each feature gets a week of security checks and that his team uses the product on all its own work. He calls friction the one controllable variable, and claims setup takes five minutes.
- Onboardbase sells itself as a simpler HashiCorp Vault. Its homepage reads "if HashiCorp Vault was simpler, priced right and just worked". Lex, its CEO, says he used Vault extensively and likes it, but it suits late-stage enterprises with security engineers to set it up. He says the comparison wins customers who already know Vault and need little explanation, and that HashiCorp accounts have signed up without ever contacting the company.
- Secrets leak because developers favour convenience over security. Lex says developers are wrongly assumed to be "secure by default", and they keep secrets in text files, Notion, Google Docs and Slack. He has dealt with a data breach at a former employer. His conclusion is that the secure tool has to be as convenient as pasting a secret into Slack, or it will not be used.
- Developers should work with secrets they never see. By Lex's account, Onboardbase injects secrets in real time into local machines and servers. Per-environment service tokens limit each process to what it needs, and device tokens can be revoked when someone leaves or a machine is compromised. Tokens can auto-expire or rotate after a set number of uses (100, say) or a set time (30 days). Deliberate sharing goes through an encrypted link that deletes itself a few minutes after viewing. His stated goal is to eliminate .env files entirely.
- SecureLog catches the secrets developers leak into logs anyway. Lex says it scans console.log and console.error calls and React server components, then masks or removes the secrets it finds and tells the developer. He says this keeps secrets out of production builds, including the browser's developer tools. Asked whether it would make developers lazy, he said he already assumes negligence and that mistakes are certain. Hanselman framed this as his "pit of success".
- Lex claims every feature gets a week of security testing. By his account, the product gets automated and manual testing, with only the marketing website exempt, and the team uses Onboardbase on all its own projects. He calls friction "the one thing you can always control". He says setup takes five minutes or less and every product he builds ships with a live demo, which he credits with bringing in customers.