Cloud-managed access control using Cloud Node head-end hardware and scalable Red-series door, gate and auxiliary controllers.
Products and selection guidance
The Red Cloud Node connects pdk.io to field controllers and maintains local data for uninterrupted access. Red controller choices include one-, two-, four-, eight-door, gate, pedestal, auxiliary and customizable models. Legacy io controllers require lifecycle/migration planning rather than being described as current Red hardware.
- pdk.io cloud software and Red Cloud Node
- Red 1/2/4/8 and Red Max controller sizing
- Red Gate, Pedestal and Aux 8 specialty control
- Legacy Single/Eight/Gate/Pedestal io migration
- 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 ProdataKey pdk.io, Cloud Node and Red Controllers, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
What integrators are asked about pdk.io, the Red Cloud Node and Red controller sizing before a cloud access system is quoted.
What does the Red Cloud Node do that a door controller does not?
The Red Cloud Node is the head-end device: it connects pdk.io to the field controllers and maintains local data so access continues. The Red controllers are the field side, wired to the readers, locks and door contacts at each opening. A design needs both roles accounted for, because neither piece covers the other’s job.
How do we choose among the Red controller sizes?
Start from the number and type of controlled openings at each location. Red controller choices include one-, two-, four-, eight-door, gate, pedestal, auxiliary and customizable models, so the count and the kind of opening drive the selection. Group the doors by where a cabinet can physically be mounted with power and network available, then size against that group.
We still run older io controllers. Do those come out on day one?
Not necessarily, but legacy hardware needs a migration plan instead of being carried forward as current Red equipment. Legacy Single/Eight/Gate/Pedestal io controllers are inventoried by location, and the plan states which openings convert first, what happens to credentials during the change, and which panels stay in service meanwhile. Lifecycle status is checked against current PDK hardware documentation.
Does every door need its own network drop?
No. Each door home-runs its reader, lock and door-position wiring back to the Red controller serving that group of openings, and the network connection is what the controller and the Cloud Node need. That is why cabinet location drives the layout: mount the cabinet where cable runs reach every door in the group and where power is available.
Does access keep working during an internet outage?
The Red Cloud Node maintains local data for uninterrupted access, so doors are not waiting on a live connection to pdk.io before making a decision. The rest of the outage still needs specifying: which openings must release or stay secured, how long standby battery carries controllers and locks, and how staff learn the link is down. Prove each case with the connection pulled.
Will the cards our staff carry today still work?
That is settled by controller, reader, lock and credential compatibility against what is physically installed, not against the drawings. Pull one reader and read the label, then sample the badges in circulation, because a site can be running two or three credential types at once. Where reuse works, badges stay in pockets; where reuse fails, reissue joins the migration plan.
ProdataKey owner, administrator and buyer resources
Discuss ProdataKey installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official ProdataKey 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.