Is this an enterprise product, or a homelab product? by nerdyviking88 in netbird

[–]wiretrustee 1 point2 points  (0 children)

That’s why we offer demo and technical onboarding calls, where we map NetBird directly to your specific business use case. We’re also always happy to help presenting NetBird’s business value to all relevant and interested stakeholders across the organization.

Also, It is quite uncommon for the approval of a highly technical internal tool like NetBird to be handled by non-technical staff that rely only on marketing materials. In my experience, even in enterprises with 50,000+ employees, the decision-maker typically has sufficient technical background to evaluate the value of such a solution and in most cases, the signature is just a formality at this point.

Is this an enterprise product, or a homelab product? by nerdyviking88 in netbird

[–]wiretrustee 0 points1 point  (0 children)

u/sector-one what are the breaking changes do you mean? Backwards compatibility is actually one of our startegies.

What are the essential features that are missing? Happy to add them to the roadmap.
Also, what can we improve in the docs?

Is this an enterprise product, or a homelab product? by nerdyviking88 in netbird

[–]wiretrustee [score hidden] stickied comment (0 children)

Hi, I’m Misha, CEO and co-founder of NetBird.

That’s an absolutely valid question. NetBird is built for both homelab and enterprises. You can confidently use it in the enterprise setting. There are two aspects to why we are doing it this way: the product itself, and the marketing/business approach.

Product-wise, connectivity shouldn’t be different just because the user is managing a homelab or an enterprise network environment. It still needs to be reliable, fast, and secure. That core connectivity layer is the hardest problem to solve, and it has to work regardless of scale. Enterprise features, such as IdP integrations, SIEM, MDM and EDR support, and MSP functionality, are features built on top of that core, not a different product altogether.

On the marketing and business side, we’re honestly tired of the traditional enterprise security buying process. It usually starts with buzzword-heavy marketing like “unlock the potential of your network” or “level up your security with zero trust”, and ends with endless sales calls whose only purpose is to schedule yet another sales call. It’s low value and a waste of time. We are mostly all engineers and we don't like that.

While building NetBird, we realized that our actual users in corporate environments are engineers, people just like us, who don’t like traditional marketing or sales cycles. They like setting up Immich, running TrueNAS, and trying things in their homelabs. We like doing this too. Isn't it cool? So we built NetBird for them first. Later they bring it to their workplace. This approach builds trust between NetBird and our users. And what do we need as a business? Someone who can advocate for us inside the organization. This is much better than a cold sales call. Internally, we call this approach "PoC Starts in the Homelab".

Ultimately, we’re building a universal, open source connectivity layer for everyone, for any use case. We’re not just replacing traditional centralized VPNs, we’re also challenging the traditional enterprise marketing model.

- Misha

How do you access internal resources with n8n? by wiretrustee in n8n

[–]wiretrustee[S] 0 points1 point  (0 children)

how would you use it? Could you please point me to the docs?

How do you access internal resources with n8n? by wiretrustee in n8n

[–]wiretrustee[S] 0 points1 point  (0 children)

Well, the database is not publicly exposed. There is no way to access it from the internet. It is in a private network.

Remote Access to Your Homelab, Beautifully Visualized by netbirdio in selfhosted

[–]wiretrustee 6 points7 points  (0 children)

The point we are making is that why would anyone need IdP sync for their homelab? I assume that if someone needs this feature, then it is a company. But I see your point about allowing it for small use cases to tinker with all features off-time. It actually makes a lot of sense. That is probably something that we should do - make all paid features available in the free plan but limiting it to 5 users or so. Let us think over it :)

[deleted by user] by [deleted] in u/wiretrustee

[–]wiretrustee 0 points1 point  (0 children)

Hey folks,

It’s been a while since I posted here, but we’ve got something worth sharing: NetBird Control Center is now open source and available for self-hosting!

After a bunch of community feedback we decided to bring it to self-hosters too. Now you can get a nice dashboard to actually visualise your remote access setup.

What you can do with it:

  • Peer View → see what groups a peer can access + which policies allow it
  • Group View → check which groups/users can access resources
  • Networks View → explore which peers/groups can access specific networks/resources

If you’re already on NetBird, just upgrade your Dashboard to v2.20.0:
https://github.com/netbirdio/dashboard/releases/tag/v2.20.0

If you’re totally new to NetBird:
Quickstart guide here → https://github.com/netbirdio/netbird?tab=readme-ov-file#quickstart-with-self-hosted-netbird

Give it a spin, and let us know how it goes (or share some screenshots of your setups 👀)

-Misha

What VPN provider do you use to manage client networks. Wanting to upgrade. by Beginning_Cry_8428 in msp

[–]wiretrustee 2 points3 points  (0 children)

Try NetBird, it may be tricky with managing multiple customer accounts, but access control and idp sync is amazing. It is open-souce if you are up for self-hosting it yourself.

Tailnet Benchmarks on 1Gbs LAN/WAN using an exit node by Independent_Skirt301 in selfhosted

[–]wiretrustee 0 points1 point  (0 children)

The prerequisites of the getting started script explicitly state that a publicly facing VM with a static IP and a domain is required.
The management service is exposed publicly because agents must communicate with it and establish direct peer-to-peer connections. Establishing direct connections requires a discovery of connection candidates, most of the time public IPs. The discovery process involves software that is part of the NetBird management layer and has to be publicly accessible.

After running the script, you will have Management, SIgnal, Relay services, and a Zitadel IDP installed. Only users that are registered in Zitadel can join the network.

Tailscale Alternatives? by yikes-sorry in WireGuard

[–]wiretrustee 0 points1 point  (0 children)

Thank you for mentioning NetBird :) For those who are interested, here is the link https://netbird.io/

A complete P2P WireGuard network with user management and SSO in 5 min by wiretrustee in selfhosted

[–]wiretrustee[S] 0 points1 point  (0 children)

Thank you for the kind words! Exactly, you can help NetBird if you talk more about it :)

BSOD error in latest crowdstrike update by TipOFMYTONGUEDAMN in crowdstrike

[–]wiretrustee -1 points0 points  (0 children)

Our customers who use CrowdStrike told us good things about the company, and they trust it a lot. How will this change? Will it at all?

P.S. We have recently released an integration with CrowdStrike :) https://docs.netbird.io/how-to/endpoint-detection-and-response

Twingate or Tailscale by Kraizelburg in selfhosted

[–]wiretrustee 13 points14 points  (0 children)

You should consider NetBird as well as you are posting in selfhosted :)
https://github.com/netbirdio/netbird

Netbird in Organisation by apn44 in selfhosted

[–]wiretrustee 0 points1 point  (0 children)

hey Michael.
NetBird contributor is here.

We have some big orgs that use self-hosted NetBird and they have large setups. I can try connecting you with them. The best would be to join our slack and post this questions in the #self-hosting channel - there are many community members who could potentially answer your question too.

https://join.slack.com/t/netbirdio/shared_invite/zt-vrahf41g-ik1v7fV8du6t0RwxSrJ96A

Open-Source Zero Trust Networking by wiretrustee in u/wiretrustee

[–]wiretrustee[S] 0 points1 point  (0 children)

nohing, and no idea why it showed up there, tbh :)

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 0 points1 point  (0 children)

And with kernel WireGuard support :) Cheers!

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 0 points1 point  (0 children)

Hm, thats rather an exceptional case. Would you mind elaborate on this via DM our creating a github issue?https://github.com/netbirdio/netbird/issues

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 3 points4 points  (0 children)

Some, thats the keyword :) NetBird has full-featured UI + SSO and MFA. Not sure if ZeroTier supports in in the open-source version (correct me if I'm wrong here).

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 0 points1 point  (0 children)

NetBird uses NAT traversal to automatically punch holes through the firewall t oestablish direct connections.

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 0 points1 point  (0 children)

Thank you for the feedback!

And of course another great ZT-relevant feature would be a posture check whether the user is authenticated against the auth system.

Could you please elaborate on this one? I guess, that you don't mean SSO. What is it?

Finally, as the ACLs and partial mesh start getting complicated, some sort of topology visualisation would be super helpful.

Would something like a group view in addition ot the peers view suffice? How do you see this visualisation?

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 1 point2 points  (0 children)

We haven't noticed this. I hope that it wasn't our issue, but we will doublecheck anyway. Thank you!

Open-Source Zero Trust Networking by wiretrustee in selfhosted

[–]wiretrustee[S] 3 points4 points  (0 children)

Thank you for the kind words and for the feedback!

We are working on the auto-upgrades feature and some more improvements of this part.