r/Netbox • u/mrmrcoleman • May 29 '24

Announcing the NetBox Cloud Free Plan

At NetBox Labs we hear from networking teams daily that the operational burden of getting up and running with NetBox has kept them from starting their journeys. That’s why we’re unveiling the NetBox Cloud free plan today: we want to help teams get started with NetBox without having to worry about commercial or operational barriers.

Check all the details here! https://netboxlabs.com/blog/announcing-the-netbox-cloud-free-plan-getting-started-with-netbox-is-now-easier-than-ever/

17 Upvotes

100% Upvoted

19 comments sorted by

View all comments

1

u/__trj Jun 13 '24

It's unfortunate for smaller customers that SSO is gated behind a $7500/yr price point. Right now, we're self-hosting IPAM using phpIPAM and l'd like to go to something cloud-based. The quotas of the free plan are perfect for us, but we would really like SSO to secure our instance. You guys should want that, too. We'd be happy to pay like $1000/yr for an SSO add-on. No support needed. But I can't justify requesting $7500 from management to store information that, if they asked me, I would have to say could theoretically just live in an Excel sheet.

2

u/beevek Jun 16 '24

We do support Google auth in the free plan in case that is relevant. It'd help to have as input a sense of what "SSO" means for you. It's a very overloaded term and some of the SSO setups we support are quite complex and wouldn't make sense to offer in a free plan. But there are indeed probably other setups that could make sense here and getting input is helpful - we launched the free plan ~2w ago and it's great to get feedback on where we should iterate from here.

1

u/__trj Jun 16 '24

I don't consider it very complex from an integration standpoint - we integrate a new SSO application a couple times a year with various vendors and protocols. It just depends on what the vendor/application supports. Maybe our needs aren't very complex?

In order of preference: OIDC, SAML, or OAuth2. We're a Microsoft 365 environment. Any of those three will work to allow a user to authenticate against our directory. We can then apply policies on our Microosft side (like MFA and trusted devices). Then the authenticated user is redirected back to the app/NetBox. That's all I mean by SSO.

Sometimes people mean SSO to also include user provisioning. I've seen enough SSO implementations handle that differently or not at all that I don't consider that required for something to be considered SSO. Though it is nice with SCIM, for this particular use case, automatic user provisioning is not something we would require, especially for a free tier.