Operating Infrastructure for Physical Spaces

Software that runs buildings the way an OS runs computers.

PlaceOS connects every system in your building — HVAC, access, AV, occupancy — into a single programmable layer. Then lets you build applications, automate workflows, and deploy AI on top of it.

The PlaceOS Stack
Applications
WorkMate StageHand Custom Apps AI Agents
↕ Interfaces
PlaceOS Platform
Orchestration AI Gateway Automation Data Layer
↕ Drivers
Building Systems
HVAC Access Control AV Sensors
Integrations
13yr In production
50+ Countries

Three forces converging

The big idea

“Linux for smart spaces.”

PlaceOS is the missing layer between building hardware and the applications people actually use. Open, programmable, and built for enterprise scale.

What PlaceOS delivers

Outcome 01
Cut energy waste.
Save real money.

When rooms know they're empty, HVAC turns down automatically. PlaceOS ties occupancy data directly to building systems — no manual rules, no separate platform. Customers average 20% HVAC savings without new hardware.

  • Automatic HVAC setback on vacancy
  • Energy savings visible in Backoffice dashboard
  • Works with your existing sensors and building systems
ROI Calculator
How much could you save?

Drag the slider to see your estimated annual savings.

Number of rooms: 50
Energy Saved
MWh / yr
Cost Saved
USD / yr (est.)
CO₂ Avoided
tonnes / yr

Estimate based on 200m² avg room size, 265.9 kWh/m²/yr, 20% HVAC reduction, ~$0.25/kWh avg commercial rate

Outcome 02
One experience.
Not ten apps.

Your staff don't want 10 different apps and 5 separate AI assistants to manage their day. PlaceOS delivers a single integrated layer — one interface for rooms, desks, visitors, AV, and everything else — built on a common data model.

  • Unified employee app (WorkMate) for all spaces
  • AI assistant with context across every building system
  • One source of truth for occupancy, bookings, and access
Your experiences — one integration layer
Turnkey
WorkMate

Out-of-the-box workplace app. Deploy in weeks, not months.

  • Room & desk booking
  • Visitor management
  • Building navigation
Custom
Your Interface

Your brand, your UX, your logic — powered by PlaceOS underneath.

  • Web, mobile or kiosk
  • On-brand experience
  • Bespoke workflows
Intelligent
AI Agents

Chat, voice or automation — AI that understands and acts on your building.

  • Natural language queries
  • Automated actions
  • Proactive alerts
Shared integration layer — PlaceOS
HVAC Access Control AV Systems Sensors Microsoft 365 HR Systems
Outcome 03
Build once.
Deploy everywhere.

Whether you're managing a single flagship building or a global portfolio of 500 sites, PlaceOS scales without re-architecting. Automation, analytics, and AI that you configure once — applied across every building that runs on your stack.

  • Single platform across campus, enterprise, and healthcare
  • Consistent policy enforcement across every site
  • Portfolio-level analytics in one Backoffice view
13yr In enterprise production
Unlimited integrations — hundreds in open source library, build your own via API
~4wk Avg time to first value
27.5k+ Spaces managed daily
Our model

SaaS isn't dead. But one size fits all is.

We have SaaS solutions that are great starting points — but you always have the flexibility to expand or build something bespoke that runs in parallel. Your building is unique. Your platform should be too.

Unlimited integrations. One platform.

Hundreds of integrations already in our open source library — and an API to build anything that isn't. No rip-and-replace required.

Cisco Meraki
Gallagher
Crestron
Honeywell
Microsoft 365
Salto
Extron
Build your own →

Build new drivers with AI.

With our open-source driver library and well-documented APIs, it's easy to point your coding agents — like Claude Code — at the right resources and references to rapidly build new integration drivers. What used to take a week can now take hours.

Claude Code
# PlaceOS Integration Driver Build Time Estimate
TL;DR: 1 day to 2 weeks — depending almost entirely on API complexity and protocol type, not the PlaceOS framework itself.
## Estimates by Driver Type
Simple HTTP/REST — e.g. sensor with clean REST API
→ 4–8 hours with Claude Code
Moderate TCP/Serial — e.g. display or projector, 15–30 commands
→ 1–3 days
Complex REST integration — e.g. access control, BMS with webhooks
→ 3–7 days
Complex bidirectional streaming — e.g. DSP audio system
→ 1–2 weeks
## Scoping Guide
Tier 1 – REST, clean API Sensor, SaaS service 0.5–1 day
Tier 2 – HTTP with complexity BMS, access control 2–4 days
Tier 3 – TCP/serial AV, displays 2–5 days
Tier 4 – Complex protocol DSP, HVAC controllers 5–10 days
With Claude Code in the loop, these estimates are ~30–40% lower than pre-2024.

Built on PlaceOS

Book a Demo

See PlaceOS in your building

Tell us about your spaces and we'll show you a tailored demo — from a single campus to a global portfolio.

  • 45-minute personalised walkthrough
  • ROI estimate for your building portfolio
  • No sales pressure — just the platform
Request a demo