Cloud-managed BMS, explained — what Neeve actually does.
The question a facility manager asks first, more often than you’d think: Can I check my building from home? The honest answer used to be a shrug — sure, if you install this VPN client, ask IT to punch a hole in the firewall, and remember which jump box lives on which subnet. The polite version was yes. The real version was it depends who’s on-call.
Cloud-managed BMS platforms exist to make that answer a real yes. Neeve is one of them — arguably the one purpose-built for our world. Here’s what it actually does, what it doesn’t, and where we’re deploying it.
What Neeve actually is.
Neeve is a zero-trust cloud platform for building systems. Three pieces, one subscription:
- Remote Access. Browser-based, no VPN, no client software. A facility engineer signs in and sees the building from wherever they are — as if they were sitting on the front-end workstation.
- BMS Cloud Hosting. The BMS server itself runs in the cloud instead of a closet on-site. Neeve handles the OS, the patches, the backups, the uptime. Niagara 4 is supported natively. Any Windows or Linux-based BMS can run on it — EcoStruxure Building Operation, Facility Explorer, Niagara. If it runs on a server, it runs on Neeve.
- Edge Intelligence. Advanced applications — analytics, fault detection, IoT integrations — run at the building edge on Neeve’s hardware, in the same secure envelope as the BMS itself.
The pitch to the facilities team is you can see your building without calling IT. The pitch to IT is SOC 2 Type II, ISO 27001, NIST-aligned, and independently pen-tested by BishopFox. Both are true. Which is what makes the conversation different this time.
What Neeve isn’t.
Make no mistake — Neeve is not a BMS. It doesn’t replace Niagara, EcoStruxure Building Operation, Facility Explorer, or anything else you already trust to run sequences and hold trends. It’s the layer underneath those platforms — the hosting, the network, the security envelope. Your BMS still is your BMS. Neeve just gives it a stable roof and a legitimate front door.
It’s also not a bolt-on you install and forget. Neeve is a subscription platform with real ongoing service behind it. That’s the point — the trade is that someone else owns the hosting so your team doesn’t have to.
Three problems it actually solves.
Problem 1
Remote access without the VPN gymnastics.
The classic BMS remote-access story is a VPN client, an IT ticket, a jump box, and a workstation someone forgot to update. Neeve replaces all of that with a browser tab. The engineer sees the same graphics they’d see on-site — from a phone in a parking lot if they have to. No client software. No firewall exception. No call IT.
Problem 2
Hosting without a server closet.
Traditional BMS servers live in a mechanical room or an IT closet — an aging Windows box, a UPS that’s older than the last controls tech, a backup policy that maybe someone owns. Neeve moves that server into the cloud. OS patching, backups, uptime, redundancy — all handled. The building keeps a small piece of Neeve hardware on-site for local communication; everything else runs upstairs.
Problem 3
A cybersecurity posture that IT will actually accept.
Here’s the thing — the BAS industry has spent a decade being the “yeah, but nobody attacks HVAC” holdout. That’s not true anymore, and every IT director we work with knows it. Neeve’s answer is zero-trust architecture, third-party audits, and framework alignment (SOC 2 Type II, ISO 27001, NIST). Meaning: when IT asks the questions they ask, there are real documents to hand over. That is not a small thing.
Where we deploy it.
For the record — we deploy Neeve on our own building first. Piper Spirit, our office in San Dimas, is in setup and evaluation. We’re running it, testing it, breaking it in ways only real buildings break, and figuring out what deserves a footnote before we recommend it to a client. That’s on purpose. We don’t want the first person to hear hmm, that’s odd to be a customer.
Once we’re satisfied — and we’re moving fast on this — Neeve becomes part of how we deliver hosted BMS to clients who don’t want to own the server themselves. Those tend to be:
- Facilities without a real IT team of their own — small campuses, single-building owners, non-profits
- Multi-site portfolios where standing up a server per site is a nightmare and cloud consolidation is a relief
- Public-sector and regulated clients whose security teams need the documentation before they’ll sign off on remote access
- Anyone whose current on-prem BMS server is aging out and the replacement question keeps getting pushed a quarter
The integrator’s take.
What we like. Neeve solves problems we’ve been solving one-off for years — VPN configurations, jump-box maintenance, server refresh cycles — with a single subscription. The security story is real and audited, which cuts a category of IT-review meetings down from months to weeks. Cloud hosting means we can put analytics and fault detection alongside the BMS without adding another box in the closet.
What we watch for. Cloud-managed anything requires a reliable internet connection at the site. Buildings with flaky ISPs or single-uplink configurations need to be honest about that before signing up — Neeve’s edge hardware handles local BMS operation if the WAN goes down, but you lose remote visibility until the link comes back. We also watch the total-cost-over-time math carefully: subscription pricing beats a $15,000 server refresh in year one, but the numbers depend on portfolio size and how long the building expects to keep the platform.
Where it fits in the stack.
Neeve isn’t a standalone service line — it’s an option we bring into the picture when we’re designing or upgrading a building automation system. It’s especially relevant on legacy migration projects, where the old on-prem server is aging out anyway and moving to cloud hosting saves the client from buying hardware that only exists to run their BMS. And if you’re already thinking about a service contract, cloud-hosted BMS pairs naturally with our service and maintenance offering — remote access is what turns a two-hour on-site call into a fifteen-minute Loom video.
If any of the three problems above sound like a Tuesday at your building, that’s the conversation to have.
The short version.
Neeve isn’t the BMS. It’s the way the BMS gets to the cloud safely — with a security posture that IT will actually approve and a subscription model that replaces a lot of infrastructure a small facilities team shouldn’t be maintaining in the first place. We’re running it on our own building. When we’re satisfied, we’ll be ready to run it on yours.
Want to talk through whether cloud-hosted BMS makes sense for your building? Get in touch.
