Any Robot.
Any Building.
One Intelligent Connection.
VERTICONNECT LINK connects autonomous robots with elevators, access control, doors, building systems and cloud services through one vendor-neutral integration platform.
Building Intelligence. Connected.
Every lift, door and robot — one live picture.
We do not replace the elevator controller or robot intelligence. We connect them safely into one coordinated building ecosystem.
Robots, elevators, access control and building systems already exist in your building — from many different vendors. What is missing is the layer that lets them work as one system. VERTICONNECT LINK normalises every brand's protocol into a canonical model, keeps critical interaction local on the edge, and gives operators one real-time view of the whole physical system.
Whatever robot or lift you choose, VERTICONNECT makes the building work together.
Robots move across floors autonomously
Elevator calls, door release and access permission handled by LINK — less manual intervention, 24/7.
Faster deployment on existing buildings
A reusable adapter library and compatibility database mean the first integration becomes the template for the next.
One monitoring and integration layer
Digital Twin, fleet and site monitoring in one place — lower integration cost for every future project.
One platform.
Modular by design.
Deploy only the modules a site needs — from a single lift integration to full building orchestration — on the same platform.
LINK Core
Mission, workflow, policy and orchestration engine.
LINK Edge
Local gateway connecting field devices — critical interaction stays on site.
LINK Lift
Elevator integration with real-time Digital Twin. The controller remains the final operational authority.
LINK Queue
Lift queueing and dispatch for luxury residences that require private elevator use — with or without robots.
LINK Queue in detail →LINK Robot
Robot adapters and mission integration for any manufacturer's fleet.
LINK Access
Access permission and credential integration for doors, gates and lift floors.
LINK HMI
Smart HMI and building interaction for residents, staff and technicians.
LINK Studio
Protocol analysis, commissioning and interface verification toolkit.
LINK Cloud
Fleet, site and remote monitoring with analytics across every deployment.
SERVE
Multi-floor autonomous service robot solution for hotels, condominiums and hospitals — robots of your choice, running on LINK.
MOVE
Industrial AMR and logistics integration — WMS, doors, lifts and fleet on one orchestration layer.
An engineering process,
not a product demo.
Every building and controller is different. We start with your existing equipment and prove compatibility before you commit.
Compatibility Assessment
Lift controller, robot platform, access system and network reviewed against the LINK compatibility database.
Site Survey & Protocol Analysis
On-site verification with LINK Studio. Interfaces are analysed and documented before any change.
Paid Pilot
One lift, one robot, one route — commissioned, measured and reviewed with your engineering team.
Commercial Deployment
Full rollout with software license, cloud monitoring and an annual maintenance / SLA agreement.
Built for the people who own
the integration problem.
Take your robots multi-floor without learning every lift brand
LINK Lift, Partner API and integration engineering — white-label or co-delivered.
Partner program →Room delivery and 24/7 service without adding manpower
SERVE + LINK: service robots that use your existing guest lifts safely.
Private lift dispatch, parcel delivery and access in one system
LINK Queue for residents who expect privacy — add robots later on the same platform.
LINK Queue in detail →Multi-floor transport of supplies, medicine and specimens
Robot–lift–door integration with policy control for restricted floors.
Bring robots and lifts into the building automation scope
LINK Partner API for BMS integrators, developers and smart-building consultants.
Add robot orchestration to service and modernisation offers
Integration partnership — we work alongside the controller, never around it.
Elevator engineering depth.
Platform thinking.
Founded by elevator field engineers, built as a platform company. We understand controllers, CAN, RS485, Modbus and HMI — and we turn that into reusable IP.
One card. One lift.
One connected journey.
Filmed on our integration bench: a resident card is verified, floor 2 is booked, the Queue Agent dispatches the car, the Digital Twin follows it from floor 1 to floor 2 and holds the doors open beside the real landing door — physical and digital in the same state, every step observed and logged. Book a technical meeting to see it live.
Have robots, need the building?
Have buildings, need orchestration?
We are selecting robot SIs, distributors, BMS contractors and elevator partners for co-delivered pilots in Thailand. Bring your equipment; we bring the integration layer.
Request a Compatibility Assessment
Tell us about your lifts, robots and building systems. We reply with an initial compatibility view and the next technical step — no obligation.
VERTICONNECT LINK
The autonomous building orchestration platform: an integration layer between devices from many manufacturers — robots, elevators, access control, doors, HMI and cloud — that lets them operate as one coordinated system.
How it is built
Devices on site — robots, HMI panels, access controllers and building systems — connect to LINK Edge, a local gateway that speaks each device's native protocol (CAN, RS485, Modbus, REST and manufacturer APIs). Edge normalises every signal into the canonical LINK model, so a lift from one brand and a robot from another describe themselves in the same terms.
LINK Core runs missions and policies on that model: which robot may call which lift, to which floors, under which conditions. Time-critical interaction — the elevator call, the door release, the safety interlock — is executed locally on the edge. The elevator controller always remains the final operational authority; LINK requests, it never overrides.
LINK Cloud collects fleet, site and event data for monitoring and analytics, and the Digital Twin shows the physical state of every lift, door and robot in real time. LINK Studio is the engineering toolkit used to analyse protocols, commission interfaces and verify each integration before it goes live.
Modules
Licensed per site, lift or device. Start with the modules a project needs and add the rest on the same platform.
| Module | Role | Typical use |
|---|---|---|
| LINK Core | Mission, workflow, policy and orchestration | Every deployment |
| LINK Edge | Local gateway connecting field devices | Every site — hardware + installation |
| LINK Lift | Elevator integration + Digital Twin | Any building where robots or residents need lift control |
| LINK Queue | Lift queueing & dispatch module — see the module page → | Luxury residences requiring private lift use; works with or without robots |
| LINK Robot | Robot adapter and mission integration | Service robots, AMRs, delivery fleets |
| LINK Access | Access permission / credential integration | Doors, gates, floor authorisation |
| LINK HMI | Smart HMI / building interaction | Resident and staff touchpoints, technician panels |
| LINK Studio | Engineering, protocol analysis, commissioning | Assessment, site survey, verification |
| LINK Cloud | Fleet, site, remote monitoring, analytics | Multi-site operators, partners, AMC |
SERVE
Multi-floor autonomous service robot solution — hotels, condominiums, hospitals.
MOVE
Industrial AMR / logistics integration — factories and warehouses.
Commercial structure
Pricing is quotation-based, because every building, controller and robot fleet has a different scope. The structure is always the same:
Engineering + Gateway + Installation + Commissioning
Integration engineering, LINK Edge hardware, site installation and commissioning with LINK Studio.
Software License + Cloud + AMC / SLA
LINK module licenses per site, lift or device; LINK Cloud subscription; annual maintenance and support under CARE.
LINK Queue
Lift queueing and dispatch for buildings where the ride is private. Residents book a journey, check in at the car, and LINK Queue asks the elevator controller for exactly that trip — for the people who are actually on board. Works with or without robots.
Book
Mobile app, landing panel or card swipe. Pickup and destination — only the floors this credential is authorised for.
Ready
The passenger confirms they are at the landing. The trip joins the FIFO queue by ready time.
Group
Passengers already waiting with the same origin and direction ride together, up to car capacity. Nobody is added mid-trip.
Pickup
The Queue Agent requests the car. On arrival a boarding check-in window opens (15 s in the reference setup).
Check-in
Card, QR, NFC or face at the car panel. LINK verifies trip, user, car, session, door state, telemetry freshness and current permission.
Dispatch
Destinations are sent only for checked-in passengers. A no-show gets no destination — the car serves the next group.
Complete
Observed arrival closes the trip. Every step is on the journey timeline and in the audit log.
One queue. One requester. One controller.
In a conventional lobby anyone can press a hall call, and the lift stops for anyone. In a luxury residence that is exactly the problem: residents expect to ride alone or with their household, and a destination should exist only for people with the right to go there.
LINK Queue changes who talks to the elevator. The mobile app, the landing panel and the car panel only express passenger intent. The Queue Agent is the single normal-service requester towards the controller: no screen calls the lift directly, no destination is registered until a passenger has checked in, and the elevator controller keeps full authority over motion, doors and the safety circuit.
Because it is a LINK module, the same queue is designed to serve people today and robots later — a delivery robot requests the lift through the same agent and the same policies via LINK Robot, on the same edge.
What residents, the lobby and the operator see.
Real screens from the LINK Queue software bench running a seeded traffic scenario in TWIN mode. Credentials, lift and traffic are simulated; layouts are the ones that ship.
Screens are from the v0.3.1 software bench (TWIN mode). Credentials, traffic and lift movement are simulated; hardware adapters for readers, HMI and the lift controller are built per site after a compatibility assessment.
Card, queue, controller, doors — and the twin watching.
One minute from our integration LAB: the resident journey from card tap to observed completion — booking, dispatch, the car arriving at floor 2, the doors opening in full, and the real landing door beside the twin in the same state. Chapters follow the same steps as the journey above.
Built to work with the controller — never around it.
Sole requester
Every hall or destination request originates from the Queue Agent. Panels and apps only express intent — there is no path from a screen to the controller.
Controller authority
The elevator controller accepts or refuses, and owns doors, motion and the safety circuit. ACK means “request received” — completion is observed from telemetry, never assumed.
Check-in before destination
A destination exists only after a verified check-in at the car. A repeat scan in the same round adds nothing; a no-show registers nothing.
Private groups
Same origin, same direction, up to capacity, formed at dispatch time. One group is served to completion before the next is collected.
Authorisation with revisions
Issue or revoke a card, change floors or validity — the authorisation revision increments and every panel must re-sync before it accepts the change.
Restart-safe by design
State persists on the edge. After a restart active trips become RECOVERY_REQUIRED and pending commands are abandoned — nothing is replayed to the lift.
Everything the building team needs, on one edge.
A local operations workspace on the building's edge server — no login to a cloud, no external database. Ten workspaces, one state.
Live operations
Active journeys, completed trips, mean pickup wait, system condition, recent activity and waiting counts by pickup floor.
Journeys & timeline
Search by queue ID or credential, filter active trips, cancel, and open a journey to see each state change with ACK separated from observed completion.
Users & floor rights
Residents, visitors, staff and contractors with unit, contact, allowed floors and valid-from / valid-until windows. Changes persist across restarts.
Issue, revoke, sync
Issue a card to a user, revoke lost cards, and push the authorisation revision to every landing and car panel — PENDING, ACKNOWLEDGED, STALE or FAILED per device.
Service modes & recovery
FIRE and INSPECTION modes, fault injection, pause dispatch and a Recover action that closes uncertain sessions without replaying commands.
Inventory & heartbeat
Every panel, reader, gateway and controller with transport, heartbeat and NOT OBSERVED / OFFLINE state. Planned CAN / RS485 mappings are recorded, not invented.
Repeatable scenarios
Seeded demand plans with profile (mixed / morning / evening), arrival interval, duration and no-show probability. Compare runs on wait mean / P95, in-car time and observed stops.
Site configuration
Site, building, group and lift names, floor labels, travel / boarding / drop-off timing and capacity — editable when no trip is active.
Journal & export
Bookings, access decisions, commands, faults and recoveries in one journal. Export state and audit as JSON for test records and hand-over.
Deployment and current status
LINK Queue runs on a PC-class edge server inside the building. Users, cards, trips, commands and the audit journal are persisted locally; the site keeps working without internet, and LINK Cloud is optional for multi-site monitoring.
TWIN mode has a built-in lift simulator, so the queue logic, panels and lobby screen can be commissioned and demonstrated before any hardware is touched. LAB mode drives an external gateway over the documented LAB protocol — the same contract a hardware adapter implements.
Adapters for the real reader, HMI and lift controller (CAN / RS485) are built per site after the controller model, protocol and floor map are confirmed in a compatibility assessment. We do not invent frames for a manufacturer's bus, and closing other call paths on the controller is configured with the manufacturer, not by the software.
| Item | LINK Queue v0.3.1 |
|---|---|
| Reference setup | 1 car · 6 floors (G–5) · capacity 6 · 15 s boarding window |
| Modes | TWIN (built-in simulator) · LAB (external gateway, LAB protocol) |
| Touchpoints | Mobile booking · LOP / LIOP · COP check-in · Lobby Queue Monitor · Command Center |
| Access | Users, floor rights, validity windows · card issue / revoke · authorisation revision & sync |
| Metrics | Wait mean / P95 · in-car mean · no-show · skipped · observed stops |
| Robots | Optional — LINK Robot missions on the same platform |
| Hardware | Reader, HMI and controller adapters per site — by compatibility assessment |
| Pricing | By quotation after the compatibility assessment |
Show us the lift, the lobby
and who should ride it.
A compatibility assessment covers the controller, the reader / HMI options and the resident flow — and returns a documented pilot scope for one car.
Built for the people who own the integration problem.
VERTICONNECT sells outcomes — robots that move across floors, buildings that work as one system — not protocols. Find the situation closest to yours.
Take your robots multi-floor without learning every lift brand
Pain: your robot cannot cross floors, and every new building means integrating another elevator brand from scratch.
What we provide: LINK Lift, LINK Robot adapters, Partner API and integration engineering — delivered white-label under your brand or co-delivered with your team. Your first project with us becomes a reusable adapter for your next ten.
Partner program →Room delivery and 24/7 service without adding manpower
Pain: delivery manpower, night shifts and guest-service consistency.
What we provide: SERVE + LINK — service robots of your choice using your existing guest lifts, with door release and access permission handled by LINK. Works alongside your BMS and PMS integrations.
Private lift dispatch, parcel delivery and access in one system
Pain: residents expect privacy in the lift; parcel delivery, security and access are separate systems from separate vendors.
What we provide: LINK Queue for private lift queueing and dispatch — deployable without any robot — plus LINK Access. Add delivery robots later on the same platform, without re-integrating the lifts.
Multi-floor transport of supplies, medicine and specimens
Pain: transport of goods, medicine and specimens between floors depends on staff time and is hard to trace.
What we provide: multi-floor robot integration with policy control — which robots may use which lifts and floors, at which hours — and full event data in LINK Cloud.
Bring robots and lifts into the building automation scope
Pain: robots and lifts sit outside the traditional BMS scope; multiple vendors cannot be connected without custom code that never scales.
What we provide: LINK as the vendor-neutral orchestration layer with a Partner API for BMS integrators, developers and smart-building consultants.
Add robot orchestration to service and modernisation offers
Pain: customers ask for robot integration; there is no orchestration platform in the portfolio.
What we provide: an integration partnership. LINK works alongside the controller, never around it — the controller remains the final operational authority.
AMR, WMS, doors and lifts on one orchestration layer
Pain: AMR fleets, WMS, industrial doors and freight lifts each come with their own integration.
What we provide: MOVE + LINK — industrial AMR and logistics integration, planned for the next phase. Register interest to be part of the first deployments.
Have robots, need the building? Have buildings, need orchestration?
We are selecting robot SIs, distributors, BMS contractors and elevator partners for co-delivered pilots in Thailand. Bring your equipment; we bring the integration layer.
Manufacturers, distributors, robot SIs
You have robots and customers. We give them the building.
- LINK Lift + LINK Robot adapters for your platform
- Partner API and white-label option
- Joint compatibility testing and listing
- Co-delivered pilots with your first customers
BMS SIs, developers, consultants
You own the building scope. We add robot and lift orchestration to it.
- LINK as the vendor-neutral orchestration layer
- Partner API into your BMS / IBMS
- Specification support for new developments
- LINK Queue for luxury residential projects
Elevator service & modernisation teams
You know the controller. We never work around it.
- Integration partnership on your installed base
- Controller-first, safety-aware architecture
- Shared engineering with LINK Studio
- New recurring revenue on modernisation projects
What the program looks like
We work with a small number of partners at a time so that every pilot gets real engineering attention. A partnership starts with a technical meeting, a compatibility assessment of your platform or site, and one paid pilot — one lift, one robot, one route — measured and documented together.
After a successful pilot, partners can quote LINK modules, gateway and engineering within their own proposals, with VERTICONNECT delivering integration, commissioning and annual support under CARE.
Pricing and partner terms are provided by quotation after the technical meeting.
Autonomous Robotics & Intelligent Building Solutions
VERTICONNECT is a system integrator and platform company. We connect robots, elevators, access control, doors, building systems and cloud into one coordinated ecosystem — and we build the platform that makes each integration reusable.
Where we come from
VERTICONNECT was founded by elevator field engineers who spent years inside machine rooms, controllers and service calls. We saw robots arriving in buildings that were never designed for them — and integrations rebuilt from scratch for every brand, every site.
We built LINK to end that. It is an engineering platform first: canonical models, protocol intelligence, a compatibility database and a safety-aware architecture in which the elevator controller always remains the final authority.
How we work
Engineering-driven, practical and vendor-neutral. We do not sell a robot brand or a lift brand. We prove compatibility before you commit, pilot before we scale, and document every interface so the next project starts further ahead.
Building Intelligence. Connected.
แพลตฟอร์มเชื่อมหุ่นยนต์ ลิฟต์ และระบบอาคารอัจฉริยะให้ทำงานร่วมกัน
Request a Compatibility Assessment
Tell us about your lifts, robots and building systems. We reply with an initial compatibility view and the next technical step — no obligation.