Live data from Hacker News

Viewing profile — ivannovazzi

ivannovazzi

HN member
Joined
Sun, Jan 18, 2026, 11:53 AM UTC
HN karma
3
Public activity
26 items

About ivannovazzi

No profile information was provided.

Recent public activity

  1. comment
    Comment #47332871

    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 (…

  2. comment
    Comment #47332869

    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 usefu…

  3. comment
    Comment #47332866

    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 junc…

  4. comment
    Comment #47332859

    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-sou…

  5. story
  6. comment
    Comment #47254568

    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. …

  7. comment
    Comment #47254560

    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 f…

  8. comment
    Comment #47254546

    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 …

  9. comment
    Comment #47254538

    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…

  10. comment
    Comment #47234519

    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 ma…

  11. comment
    Comment #47234332

    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…

  12. comment
    Comment #47234257

    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 w…

  13. comment
    Comment #47234252

    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 clien…

  14. comment
    Comment #47234242

    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 bui…

  15. comment
    Comment #47234241

    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 encryp…

  16. comment
    Comment #47152141

    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) — C…

  17. comment
    Comment #47152089

    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. …

  18. comment
    Comment #47152030

    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-fir…

  19. comment
    Comment #47151756

    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 th…

  20. comment
    Comment #47151748

    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…

  21. comment
    Comment #47149772

    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…

  22. comment
    Comment #47149751

    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 in…

  23. story
    Show HN: KeyEnv – manage team secrets without scattered .env files

    Tired of .env files getting out of sync across team members and environments? KeyEnv is a CLI-first secrets manager that replaces scattered .env files with a secure, encrypted stor…

  24. story
    Show HN: Gatherly – E-signatures and doc collection for professional services

    I built this after hearing the same complaint from accountants, lawyers, and consultants: they spend more time chasing clients for documents than doing actual work. The pattern rep…

  25. comment
    Comment #46676577

    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, pla…