Cloud software for managing access across supported smart locks and property technology ecosystems.
Products and selection guidance
RemoteLock focuses on universal access for vacation rental, multifamily and managed-property workflows. The platform may connect multiple lock brands and reservation/property systems, but compatibility is exact-model and integration dependent. Define account ownership, subscriptions, PMS data, code lifecycle, connectivity and support responsibility.
- Cloud account, properties, users and lock groups
- PMS/reservation integration and automated code lifecycle
- Audit, remote operations and staff/vendor access
- Supported lock model, gateway and firmware matrix
- Door, lock, free-egress, accessibility and fire-alarm requirements
- Network, power, standby battery and outage behavior
- Current licenses, subscriptions, firmware and integrations
- Administrator training, backup, documentation and maintenance
Site-specific design
Boston High Tech inventories existing equipment and validates current manufacturer compatibility before specifying reuse, migration or replacement. Qualifications may be confirmed privately when needed; license numbers, certificate copies and named certificate-holder details are not published.
Request a manufacturer-specific consultation
Projects are supported from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For RemoteLock Universal Access Control Cloud Software, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following electronic lock and door-hardware system decisions before equipment is ordered:
- Opening type, handing, frame and door condition
- Fire rating, egress, accessibility and code constraints
- Fail-safe or fail-secure operation and emergency release
- Credential, reader and controller compatibility
- Battery, wireless gateway and offline behavior
- Mechanical key override, maintenance and lifecycle support
Installation, testing and handoff
Each opening is surveyed as a complete assembly. We verify the door, frame, handing, existing prep, latching, closer, egress hardware, power path and the required emergency behavior before specifying a lock. Installation includes alignment and mechanical correction within scope, cable and power testing, credential enrollment, door-state and request-to-exit tests, and failure-mode verification. The owner receives opening schedules, administrator guidance and maintenance requirements; private credential data and certificate details are not published.
Frequently asked questions
Questions about running mixed lock brands, reservation-driven codes and property access from one RemoteLock cloud account.
Can one account manage locks from different manufacturers?
That is the intent of the platform, described as cloud software for managing access across supported smart locks and property technology ecosystems. The limit is that compatibility is exact-model and integration dependent, so each lock is checked against the supported lock model, gateway and firmware matrix before counting as managed. Locks that miss the matrix are replaced or managed outside the platform.
Does a short-term rental portfolio get set up the same way as an apartment building?
One platform covers both, since RemoteLock is aimed at vacation rental, multifamily and managed-property workflows, but the structure differs. Rentals lean on reservation-driven codes with a short life, while an apartment building leans on longer-lived residents plus staff groups. Lay out the cloud account, properties, users and lock groups for the mix you actually manage.
A property loses its internet connection. Can a cleaner still get in?
That depends on the lock model and gateway specified for that property, which is why connectivity is one of the items defined up front. Decide which properties must keep staff/vendor access working without a connection, then confirm the behavior of those exact devices against the supported lock model, gateway and firmware matrix before the site plan is fixed.
Can a smart lock go on a fire-rated stairwell door?
That is settled opening by opening. Fire rating, egress, accessibility and code constraints are checked with opening type, handing, frame and door condition before a lock is specified, and the fail-safe or fail-secure operation with emergency release has to match the egress plan for that door. A rated assembly also limits what may be cut or modified.
Do guest codes have to be typed in for every booking?
Not where a reservation feed is in place. PMS/reservation integration and automated code lifecycle is listed as a design item, so codes can be created and retired against booking dates instead of by hand. Which reservation or property system connects is integration dependent, so name the system and decide who owns the PMS data when two records disagree.
We also have card readers on the office suite doors. Are those covered?
Not by assumption. Credential, reader and controller compatibility is a separate check from the smart-lock list, and compatibility here stays exact-model and integration dependent, so office readers come into scope only after the specific devices are confirmed. Openings that fall outside the platform stay on the system running them today, and the proposal should say which doors sit where.
Official RemoteLock software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.