Background
I served in the U.S. Air Force, and the discipline, resilience and teamwork from that time still shape how I work.
I've been hands-on with Fortinet firewalls since 2009. Today most of my work is on client networks: FortiGate upgrades, VPN migrations, and the change windows that come with them, where there are real users on the other side and no room to guess.
Why I built ArkhiNet
Working across many customer environments means living in a pile of disconnected tools: PuTTY and SecureCRT session lists, IP spreadsheets, Visio diagrams nobody updates after the install, and client notes scattered across folders and inboxes. Every one of them is another place for information to go stale.
So I built the tool I wanted for my own daily work: one place for every client, site and device, with the connection one click away, the topology drawn for me, and a report I can hand to a customer.
It turned out to help other engineers too, so I give it away. ArkhiNet is free for individual engineers with every feature included, and it isn't a trial. Teams that depend on it pay for Team, which keeps it maintained and supported.
What I hold it to
Never stores passwords or keys
An engineer's tool shouldn't be the place your customers' credentials leak from. ArkhiNet keeps no device passwords or private keys, anywhere.
Offline, with no telemetry
Your inventory lives in a file you choose, on your machine or your own share. None of it is ever sent to me.
Vendor-agnostic
I live in Fortinet, but customers also run Cisco, Palo Alto, Meraki, SonicWall and Sophos. ArkhiNet doesn't care what's in the rack.
Free for engineers, for real
Every feature, unlimited devices, no license key and no trial clock. Organizations with two or more engineers pay for Team, and that keeps it maintained.
Questions, feedback, or a feature you need?
I read every email. Write to support@arkhinet.com.