Pilot Program
A production-grade installation with measured outcomes, acceptance tests, and a clean handover.
Designed for commissioned environments
Residences and penthouses with complex lighting, climate, and access
Estates requiring role-safe operation across staff and operators
Yachts requiring telemetry integration and disciplined boundaries
Facilities where stability and auditability matter
What a pilot includes
Interface
Role-safe UI surfaces for owner, staff, and engineering
Control Core
Hardened on-prem deployment inside the client network
Policy + Audit
Single actuation boundary with correlation IDs
Commissioning
Offline, degraded-mode, and recovery acceptance tests
Handover
Runbook excerpt, topology summary, config export bundle
Typical Timeline
Discovery
Week 1–2Interface inventory + scope boundaries + protocol mapping
Commissioning Build
Week 3–5Certified hardware + validated release line
On-site Deployment
Week 6–8Installation + acceptance testing
Handover
Week 8–10Reports, runbooks, change history, and stewardship plan
Requirements to start
- Protocol inventory and access to existing gateways
- A commissioning window for acceptance tests
- Agreement on scope boundaries
Commercial Structure
Pilots are scoped by environment complexity and interface count. We provide a fixed-band estimate after discovery.
Request a pilot scope
If you want a stable, local-first system that ages well, start with a commissioned pilot.