[jeffg-nbl]

Hey, I'm a product manager at NetBox Labs, the commercial stewards of the NetBox project. It's great to see such nice and useful feedback.

We're not even a year old yet as a company, and we know that it's currently not easy to find details on netbox.dev, and we're in the middle of a project to address that. In the meantime, I hope you'll check out the resources hosted on https://netboxlabs.com.

There's also a slack workspace at https://netdev-community.slack.com/ where you can interact with me and my colleagues. I'm @Jeff Gehlbach.

[frellus]

Somehow I had no idea that there was a commercial SaaS version of Netbox, as I've been using the OSS version for years hosted internally.

Feedback: the pricing is completely whacked, IMHO. I got excited that I could move to someone else supporting Netbox instead of my team, however due to the number of devices I have, I would have to use the middle license tier -- that's listed as $20,000/yr. This isn't a $20,000/yr problem to me, it would be impossible to justify this to my management, sadly.

Just my feedback on your pricing. Netbox itself, the code and the absolutely stunning dev velocity is inspiring, but unless pricing were drastically lower I couldn't go for it. Would otherwise love to support.

[jeffg-nbl]

Thanks for the kind words! I'm specifically attached to NetBox Open Source, and will pass along the compliments to the dev team.

And yeah, the pricing for NetBox Cloud isn't a fit for every use case. That product isn't the only thing we've got cooking; stay tuned :)

[snerbles]

That's comparable to Device42 and Sunbird - what you're really paying for is "one throat to choke". In an enterprise environment, that's pennies.

In prior roles I've seen NetBox explicitly vetoed in favor of technically inferior solutions because there was no available support contract at the time. Also, Sunbird has fancy 3D rack renders, and that's management catnip.

[dboreham]

Just one datapoint: charging only $20k/yr to take the heat for running a mission critical service for an enterprise customer seems very low to me.

[downrightmike]

I had to dig to a wiki to see what the interface looks like, would like it on the homepage.

[jeffg-nbl]

Noted, thanks for the feedback. I'll make sure that we get some visuals in a place that's easier to find.

[jsz0]

Hey if you're ever looking for any DevOps people with a network engineering background LMK I'm a big fan of NetBox I think it's something I'd enjoy working on.

[jpc0]

Just a comment from a smaller user who has moved away from netbox and realistically went back to spreadsheets. Please don't see it as a negative, netbox may purely just be the wrong product for us.

Some background on our usecase, tldr at the bottom. We effectively just need basic documentation. Which port on which patchpanel does this drop go to? Which network port is that connected to? What vlan should be assigned to it? Which router manages that vlan? What network range is on that vlan if any? What IP address should this device be assigned?

I've always found it just a bit difficult to setup things correctly, partly because everything feels slow. To put it into perspective, I was eventually running netbox on a VPS with 2 Genoa cores and 4 gigs of ram and even then some queries would be slow and page loads felt sluggish. Ping to the DC is sub 1ms on that. To need to provide that much horsepower for a DB with an interface just seemed like overkill to management.

Our usecase was great in earlier versions of netbox, the worst performance degradation came around when the graphql API got pushed and newer versions haven't improved it.

As I said, don't take it as a negative, netbox is a good product and to be fair I have never submitted an issue for this nor have I made an attempt to dig into the code to fix it (you can happily blame Django for that). Internally we see netbox as something we probably didn't put enough effort into doing correctly but at the same time the performance issues are a dealbreaker.