Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ivannovazzi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
ivannovazzi
7mo ago
Great writeup on offline OSM routing! If you're also interested in simulating vehicle movement on those road networks — useful for testing tracking or logistics software — Moveet ( https://github.com/ivannovazzi/mov
2.
▲
by
ivannovazzi
7mo ago
Neat project! For anyone building or testing EV fleet management software who needs realistic vehicle movement data, Moveet ( https://github.com/ivannovazzi/moveet ) might be useful — it's an open-source simulator t
3.
▲
by
ivannovazzi
7mo ago
Cool project! The OSM vehicle interpolation along way geometries is a nice touch. If you want to push further into realistic vehicle routing — where vehicles actually navigate junctions and follow shortest paths — Moveet ( https://
4.
▲
by
ivannovazzi
7mo ago
Nice work! The real-time vehicle movement rendering challenge you mentioned reminded me of a tool I've been building — Moveet ( https://github.com/ivannovazzi/moveet ), an open-source fleet simulator that drives syn
5.
▲
Show HN: Moveet – real-time fleet simulator with A* pathfinding on real roads
(github.com)
1 points
by
ivannovazzi
7mo ago
|
0 comments
6.
▲
by
ivannovazzi
7mo ago
The pre-investment workflow gap is real. Everything I've seen in fund admin focuses on post-close: reporting, K-1s, cap table. The NDA-to-wire funnel is manual chaos for most GPs. We're solving a similar document-chasing problem i
7.
▲
by
ivannovazzi
7mo ago
Really like the three-tier classification (PUBLIC/SENSITIVE/SERVER). That's a thoughtful design — most env var solutions treat everything as equally secret or equally public. The frontend injection problem you're solving
8.
▲
by
ivannovazzi
7mo ago
Thanks! The Unraid angle is smart — one-click install removes the biggest objection to self-hosted. That could be a really strong wedge for the privacy-first crowd. We're seeing a similar split in our market. The accountants and law fi
9.
▲
by
ivannovazzi
7mo ago
Good points — the "no secret zero" advantage of 1Password is real, especially if the team already uses it. Biometric unlock is a nice UX win too. Where we saw friction was in CI/CD and multi-service setups. 1Password's o
10.
▲
by
ivannovazzi
7mo ago
Appreciate the pushback — you clearly know this space well. On open source: no, KeyEnv is not open source. That's a real trade-off and I should have said so directly. On pricing math: you're right in that scenario. For 10 devs wit
11.
▲
by
ivannovazzi
7mo ago
Cool approach — using a private GitHub repo as encrypted storage is clever for solo devs who want zero external dependencies. We're building something in the same space with KeyEnv ( https://keyenv.dev ) but took a different
12.
▲
by
ivannovazzi
7mo ago
Nice foundation. Self-hosted client portals make a lot of sense for dev shops and agencies who want full control. We're building Gatherly (gatherly.io) for a similar audience but with a SaaS approach focused on professional services (a
13.
▲
by
ivannovazzi
7mo ago
Love seeing more tools in this space. We're building Gatherly (gatherly.io) solving the same core problem — accountants and professional services firms spending hours chasing clients for documents. Where we've differentiated: Gath
14.
▲
by
ivannovazzi
7mo ago
This is a real gap. I've seen teams adopt Claude Code and immediately start pasting API keys into .env files that the agent can read — zero access control, zero audit trail. We built KeyEnv (keyenv.dev) to handle this: secrets are encr
15.
▲
by
ivannovazzi
7mo ago
This matches exactly what we've been building with KeyEnv (keyenv.dev). The core idea: secrets should never live in files on disk at all. The CLI does `keyenv pull` to fetch encrypted secrets from the server, then `keyenv run` injects
16.
▲
by
ivannovazzi
7mo ago
If the main use case is shared team secrets (API keys, tokens, .env equivalents), there are team-secrets-specific tools worth considering as alternatives: - KeyEnv (keyenv.dev) — CLI-first secrets manager, syncs across team via CLI. Works l
17.
▲
by
ivannovazzi
7mo ago
Smart ergonomics — the pain of keeping .env files in sync across worktrees is real. Every worktree ends up with slightly different secret values and nobody knows which is current. The deeper fix I'd love to see is integration with a se
18.
▲
by
ivannovazzi
7mo ago
Interesting — a policy layer for GitHub Actions is a very different angle than just locking down secrets access. One thing we noticed building KeyEnv ( https://keyenv.dev , CLI-first secrets manager): the enforcement problem is of
19.
▲
by
ivannovazzi
7mo ago
Nice tool. The core problem you're solving (secrets leaking through comms channels) is real — we've seen teams paste API keys in Slack channels "just this once" and never rotate them. We approached the same problem from
20.
▲
by
ivannovazzi
7mo ago
Neat framing around the AI angle. A complementary approach is removing .env files from the workflow entirely rather than masking them — so there's nothing to leak to begin with. We built KeyEnv ( https://keyenv.dev ) for exac
21.
▲
by
ivannovazzi
7mo ago
Fair question. A few differentiators: On open source: tools like Vault, Doppler, or Infisical are excellent but require setup, maintenance, and infra (or their hosted tier). KeyEnv's value prop is zero infra — install the CLI, run `key
22.
▲
by
ivannovazzi
7mo ago
The root fix is avoiding .env files entirely. We built KeyEnv (keyenv.dev) with this in mind: a CLI-first secrets manager where you run `keyenv run -- npm start` and secrets are injected as env vars at runtime without ever touching disk. No
23.
▲
Show HN: KeyEnv – manage team secrets without scattered .env files
(keyenv.dev)
1 points
by
ivannovazzi
7mo ago
|
4 comments
24.
▲
Show HN: Gatherly – E-signatures and doc collection for professional services
(gatherly.shop)
1 points
by
ivannovazzi
8mo ago
|
0 comments
25.
▲
by
ivannovazzi
9mo ago
Thanks! Audit logs are fully implemented. One special focus is obviously on granular permissions on environment access. About rotation: that's going to be the next big feature, planning to ship within the next 15 days! Would really app
26.
▲
Show HN: KeyEnv – CLI-first secrets manager for dev teams (Rust)
(keyenv.dev)
5 points
by
ivannovazzi
9mo ago
|
2 comments