One facility map
Doors, cameras, and sensors on the building plan. Events appear in zone context — not only as journal rows.
Platform
Why EAS: access control, video, and sensors on one map
EAS is designed as one site platform: access control, video, and telemetry share a web UI and one facility map. Not apps side by side — one picture for security, HR, and leadership.
Four product pillars
On-premises Ubuntu server
Data and live operation stay on site. Internet is for updates and licensing — not for every passage.
Clear licensing
One-time ₽30,000 RUB with no door limit. Pay for the platform, not per door.
ZKTeco C3-200 controllers out of the box
ZKTeco C3-200 and C3-200 Plus and turnstiles out of the box; the model list grows with updates. Plus Hikvision/RTSP video and mobile pass / TV Wall.
How EAS differs from a classic multi-app stack
- Not three windows at the post (ACS + VMS + Excel) — one UI with live events
- The facility map is core product, not an optional add-on
- ~50 KB hub patches without rebuilding the site stack
- 30-day trial and browser demo before the contract
Moving from a legacy ACS
If security juggles multiple apps and per-door licenses inflate cost — typical path: pilot EAS beside the old system, then migrate cards and access zones.
- Evaluate the demo and facility map without stopping the current ACS
- Install the Ubuntu trial and connect one controller / cameras
- Align roles, journal, and attendance — then plan full migration
Where to start
- Get the trial and install on Ubuntu
- Connect a controller and verify passages
- Upload the facility floor plan
- Review pricing and request an invoice
FAQ
Is EAS only access control?
No. The core is one platform: access, video, sensors, and the map. ACS is a module — not the whole product.
Is a vendor cloud required?
No. The site runs on your server. The central hub is for install, updates, and license activation.
How fast can we evaluate?
Browser demo or a 30-day Ubuntu trial with your controller.