No mandatory SaaS access
Core workplace functions must continue without relying on an external scheduling service.
Regulated and secure environments
Workplace scheduling without a mandatory external dependency
Operate flexEZ inside customer-controlled infrastructure, including fully air-gapped environments, with a standalone scheduling engine and locally connected workplace devices.
Controlled operations
Security constraints change the deployment—not the need for usable scheduling
Teams still need clear booking and workplace coordination when internet access and external services are restricted.
Customer-controlled data paths
Application, device and integration traffic may need to remain inside the managed network.
Local enterprise systems
Identity, Exchange and operational systems may also be installed inside the isolated environment.
Specialized policies
Access, booking and administration rules often require sector- or site-specific adaptation.
Where control matters
Built for organizations that must control more of the operating environment
The required level of isolation varies. Some sites need a fully air-gapped system; others need customer-controlled hosting, integrations and data paths to satisfy governance and risk requirements.
Military installations
Operational sites where workplace systems may run on restricted or disconnected networks.
Why control matters
Network classification, mission continuity and attack-surface reduction can prohibit reliance on public cloud or internet connectivity.
Defense and military contractors
Organizations handling sensitive programs, facilities and supply-chain relationships.
Why control matters
Contractual security obligations, controlled technical information and customer accreditation can require tightly governed hosting and network routes.
Banking and financial services
Institutions operating critical services under extensive security, resilience and audit obligations.
Why control matters
Third-party risk, data governance, business continuity and change-control policies may favor infrastructure and integrations the institution can directly govern.
Insurance and other regulated organizations
Enterprises that manage sensitive personal, commercial or operational information.
Why control matters
Privacy, residency, retention, auditability and internal security policies may require clear ownership of where data is stored and how systems communicate.
Government offices
Public-sector workplaces managing citizen services, sensitive records or essential administrative functions.
Why control matters
Sovereignty requirements, procurement rules, records governance, continuity obligations and security classification may require government-controlled hosting and explicit data paths.
A self-contained workplace operating path
Keep the user experience and connected devices within the boundaries defined by the organization.
1
Authenticate locally
Use configured local identity, directory or access-control arrangements.
2
Schedule inside flexEZ
The standalone engine manages resources, availability and booking policies.
3
Connect local endpoints
Tablets and supported occupancy sensors communicate with the flexEZ server.
4
Retain operational visibility
Authorized teams use local schedules, status and analytics for decisions.
Capabilities for controlled environments
Combine standalone operation with the hardware and management functions appropriate to the site.
On-premises and air-gapped deployment
Run core flexEZ services within infrastructure controlled by the customer.
View capability
Room and resource scheduling
Provide a complete local booking experience across workplace resources.
View capability
Server-connected room tablets
Use tablets that communicate with flexEZ without requiring an external source.
View capability
Local occupancy sensors
Connect supported 3D people-counting and Atlona OCS sensors using local addresses.
View capability
Local workplace analytics
Use booking, status and sensor data within the controlled deployment.
View capability
Local IoT integration
Connect supported devices and operational data through local integration patterns.
View capability
Physical access integration
Where approved, a custom integration can exchange authorized-user or reservation-derived lists with a local physical security system—for example, allowing a door or controlled zone to open only for eligible people during approved times.
View capability
Usability and control for the teams involved
A controlled deployment must serve employees and operators without weakening the organization’s architecture boundaries.
Employees
Use a clear scheduling experience within the approved environment.
IT and security
Control hosting, identity, network paths, updates and integration boundaries.
Facilities and operations
Manage resources, room devices, policies and local workplace data.
Architecture choices for restricted networks
The final design should reflect the organization’s network classification, identity and operational-support requirements.
Fully air-gapped
Operate the standalone engine and local endpoints without external network access.
Local Microsoft Exchange
Connect to an Exchange environment installed within the same controlled network.
Controlled on-premises
Allow only the explicitly approved integrations and network routes.