Launched this week
confish
Change a value. Don't redeploy.
4 followers
Change a value. Don't redeploy.
4 followers
Runtime configuration for bots, scripts, workers, and small apps. Define a typed schema, fetch values via official Go / JS / PHP / Python / Rust SDKs, push logs back up, and dispatch one-off actions from the dashboard. Change a value, your code picks it up - no redeploy.
I automate things.
Bots, scrapers, scheduled jobs - I've got dozens of small things running in the background that quietly do useful work for me.
Sometimes I want to tweak something while it's running. A threshold. A toggle. A retry count. Some tiny number I should be able to change in a second, and ideally - AFK, on my phone.
After building tiny control panels for three different services, I decided to centralize it.
So https://confi.sh was born. You define a schema once - whatever fields your app needs. Then you spin up as many environments as you want (staging, prod, per-client, whatever). Same fields, different values. Your code hits one endpoint and gets typed config back.
It grew from there into the things I actually reached for day-to-day:
- Logs. Push entries from your script and read them in the dashboard.
- Webhooks. Your endpoint gets pinged when a value changes, no polling required.
- Actions. Dispatch remote commands to environments via long-poll. Flush a cache, restart workers, trigger custom logic, without exposing inbound endpoints.
- SDKs. Five hand-written ones: Go, JS, PHP, Python, Rust.
If your config story today is "I SSH in and edit a YAML file" or "I built a tiny admin panel for it," I'd love to hear whether confish would fix that - or where it falls short.
Bug reports, feature requests, naming gripes - all welcome. Thanks for taking a look 🙏