Built a companion app for NetBird to cover gaps we hit as an MSP - is this interesting to anyone else?

Not a product pitch - genuinely asking if anyone else needs this.

We run NetBird (cloud, MSP plan) for our own company and for customer tenants. It’s great, but as our usage grew we kept hitting the same walls:

Activity and traffic history - events are only retained for a limited window, and there’s no long-term searchable log. We needed “who accessed what, from where, six months ago” for audits and forensics.
Temporary access - no built-in way to grant someone access to a resource for 4 hours and have it torn down automatically, let alone a request/approval flow.
MSP tenant onboarding - every new customer tenant meant manually re-creating the same settings, webhooks, filters and policies, one dashboard at a time.
Guardrails - nothing stops an admin from accidentally exposing a sensitive internal range as a resource.
So over time I built an internal self-hosted companion app (Node + Postgres + React) that sits next to NetBird and talks to its API. What it ended up doing:

Ingests the event-streaming webhook into Postgres - unlimited, searchable activity/traffic history with retention we control, per account
Time-boxed access grants with a self-service request flow - approvals happen in-app or from Telegram, and everything is torn down automatically on expiry
Full MSP layer: tenants are managed like the main account (same pages, isolated data), new tenants are seeded from an admin-defined defaults profile (NetBird account settings, filters, blocklist, retention), one-click webhook/notification setup per tenant, a readiness checklist, and a cross-tenant fleet report
Address blocklist that blocks accidental exposure of protected ranges, auto-provisioning of resources from external sources (IPAM/inventory), periodic access recertification, and a guided troubleshoot page for end users
Encrypted backups, audit log of every change, Telegram/email notifications per account
It’s been running in production for our environment for a while now.

My question: are these pains common enough that it’s worth cleaning this up and sharing it? If there’s real interest I’d consider open-sourcing it. Curious what others do today for long-term event history and temporary access on NetBird - and if you’re an MSP, how you handle tenant onboarding.

(Not affiliated with NetBird - it’s an independent companion that uses their public API.)

Hey Shlomi,

Thanks for opening this and sharing the use case with your companion.

We are very interested in discussing the temporary access and the tenant onboarding. Would you be available for a call next week?

Sure. Whenever you want
I have full documentation on all these features if you’re interested in taking a look (I can share it with you on github, it’s currently in a private repo)