Anuvrat Chandra

Hi, Im looking to launch my app and i was curious how to position myself

by

I built Dotward because I got tired of feeling anxious every time I pushed code.

A couple years ago I accidentally committed a .env file to a public repo. API keys, database creds, the whole thing. I caught it fast and rotated everything, but it made me realize how normal that workflow actually is for most developers.

Even after that happened, I still kept secrets the same way:
plaintext .env files, copied credentials between devices, random old tokens sitting around longer than they should.

Dotward started as me trying to fix that for myself.

The idea was simple:
what if secrets didn’t need to live on disk all the time, and what if accidental leaks could be stopped before they ever reached GitHub?

That became the core of the app.

dotward inject lets me run apps with secrets injected directly into memory instead of writing everything into plaintext files.

dotward install-hook adds a pre-commit scanner that catches exposed keys, tokens, or staged .env files before I can accidentally push them.

I kept the whole thing offline-first because I personally didn’t want another cloud dashboard holding sensitive credentials. No telemetry, no accounts, no syncing — everything stays local.

The desktop app adds some extra quality-of-life stuff like encryption, security scoring, and rotation reminders, but honestly the main goal is just reducing stupid mistakes without making development more annoying.

I’m not trying to replace enterprise secret managers or pretend I invented a brand new category. I just wanted a tool that fit naturally into how developers already work while quietly preventing the kind of mistake I made myself.

Here's the link to the site

dotward

5 views

Add a comment

Replies

Be the first to comment