Systems / ProdataKey pdk.io
ProdataKey pdk.io: cloud platform, Red controllers, API and upgrade options
By Tom Jin
pdk.io is the cloud-managed access-control platform from ProdataKey, usually shortened to PDK. The door hardware sits on site, but management runs in the cloud through the pdk.io web app. Each location has a Red Cloud Node, which is the main panel and also controls one door, and further doors connect through PDK's Red-series controllers. PDK also sells outdoor controllers for gates and Red wireless locksets.
PDK lists small and mid-size businesses, commercial real estate and coworking among its markets. Systems are sold and supported through PDK dealers, and the platform's permission model reflects that: a dealer organization sits above each customer organization. PDK is unusual among SMB systems in publishing a full developer API openly, with REST, webhooks and a streaming interface, and the same API powers pdk.io itself.
How to recognise ProdataKey pdk.io
The clearest sign is that administrators log in to pdk.io in a web browser rather than running software on an office PC. In the network closet or above the ceiling you will find PDK Red-series hardware: a Red Cloud Node at each location and Red 1, Red 2, Red 4 or Red 8 controllers for more doors. Gates may have a Red Gate or Red Pedestal outdoor controller. The PDK branding is on the web app and on the hardware.
- Administrators manage doors at pdk.io in a browser, with no access-control server in the office.
- A PDK Red Cloud Node at each site, the main panel that also controls a single door.
- PDK Red 1, Red 2, Red 4 or Red 8 door controllers, sometimes a Red A8 auxiliary controller or Red Max.
- Red Gate or Red Pedestal outdoor controllers at parking or perimeter gates.
- PDK Red wireless locksets, or ASSA ABLOY Aperio wireless locks, shown as devices in pdk.io.
Still not sure? Follow how to identify your access control system.
Versions and editions
| Name | Details | Status | Source |
|---|---|---|---|
| pdk.io (cloud platform) | Cloud-native management for on-site PDK hardware. Organizations are hierarchical: dealers are parents and customers are children. Each customer has one system, with a cloud node per location. | current | source |
| PDK Web API 2.0 | Public REST API that powers pdk.io itself, with OAuth2 authentication, webhooks and a Socket.IO streaming API. A Postman collection is published. | current | source |
| PDK mobile SDKs | iOS and Android SDKs for building mobile access into other apps. | current | source |
| Earlier API versions | The developer site documents version 2.0. The status of earlier API versions is not confirmed. | unconfirmed | source |
Hardware
| Name | Details | Status | Source |
|---|---|---|---|
| Red Cloud Node | Main panel with a single-door controller. One per location; connects the site to pdk.io. | current | source |
| Red 1, Red 2, Red 4, Red 8 | One-, two-, four- and eight-door controllers. | current | source |
| Red Gate and Red Pedestal | Outdoor controllers. | current | source |
| Red Max and Red A8 | Red Max is described as a customizable controller; Red A8 as an auxiliary controller. | current | source |
| Red Module Kits | Communication add-on modules. | current | source |
| Red wireless locksets | PDK's own wireless locks, listed alongside the controllers. PDK's API also supports ASSA ABLOY Aperio wireless locks as devices. | current | source |
| Legacy controllers | PDK's controllers page has a Legacy section, but we could not read which models it lists or their support status. | unconfirmed | source |
What is ending, and when
We found no dated end-of-sale or end-of-support notices for PDK hardware in the pages we reviewed. The Red Cloud Node and Red-series controllers are on PDK's current controllers page. That page also has a Legacy section, which shows older hardware exists, but we could not confirm which models it covers or how long they are supported, so we do not mark anything as ended.
Because pdk.io is a cloud service, software updates are handled by PDK rather than by the office, so there is no server version to fall behind on. The lifecycle questions shift to the hardware on site and to the subscription and dealer arrangement. If you have older PDK hardware, ask your dealer whether it appears in the Legacy section and what that means for support. Dated notices for other brands are in our end-of-life tracker.
See every dated notice in the end-of-life tracker.
What offices commonly miss
- No record of who left. Like most card systems, exits usually release through a request-to-exit device or push bar with no credential, so pdk.io logs who came in but not who went out.
- Administration depends on the dealer relationship. In PDK's permission model the dealer organization sits above the customer, so check what you can change yourself and what needs the dealer.
- The Red Cloud Node is the site's link to the cloud. Know what happens to door operation and event delivery if the office internet connection drops, and ask your dealer to show you.
- Subscription and mobile-credential pricing is not published in the pages we reviewed, so get it in writing before adding doors or users.
- Older hardware may sit in PDK's Legacy category, whose support terms we could not confirm.
Integration options
PDK publishes its developer API openly. The REST API 2.0 is the same interface that powers pdk.io, and it uses OAuth2 with either the client-credentials or the authorization-code flow. New API clients register by emailing PDK's integrations team with a short description of the application, and receive a client ID and secret. The API models a hierarchy of organizations, systems, cloud nodes, connections (controllers) and devices, where devices are doors and gates with their readers, Aperio wireless locks, and anything else controlled by a relay.
For doors, the API has an open command and a try-open command, which applies the system's access rules first. Events arrive through webhooks, for example when a request is allowed or denied, or through a Socket.IO streaming API. PDK also offers iOS and Android SDKs and an in-app marketplace where integrations can be listed. Because it is a cloud API, an outside service does not need anything installed in the office.
Upgrade paths
Keep pdk.io and add features in software
PDK's hardware is current and its API is public, with door commands and real-time events. That makes it a straightforward system to keep and extend with software for things like exit tracking or a live list of who is inside, without touching the doors.
Expand within PDK
Add doors with Red 1 to Red 8 controllers, gates with Red Gate or Red Pedestal, and a Red Cloud Node for each new location. Ask your dealer about any hardware in PDK's Legacy category and plan its replacement with current Red-series units.
Replace the platform
A full replacement means new controllers, often new readers and credentials, and re-commissioning every door. With current hardware and an open API, PDK rarely forces this; it usually makes sense only if you change your whole security approach or move buildings.
Compare the routes over three years in the savings calculator.
GateStride and ProdataKey pdk.io
Not yet scheduled ProdataKey pdk.io is Not yet scheduled on the GateStride compatibility list. It is not on our roadmap yet, and GateStride does not work with PDK today. GateStride is in early access. PDK's public API would make an integration practical, but no work has started. If your office runs PDK, tell us; demand from real sites decides what we build next.
Questions about ProdataKey pdk.io
- Does PDK have a public API?
- Yes. PDK publishes its REST API 2.0, the same API that powers pdk.io, with OAuth2 authentication, webhooks, a Socket.IO streaming API and iOS and Android SDKs. Developers register by emailing PDK's integrations team to receive a client ID and secret. A Postman collection is also published on the developer site.
- What is a Red Cloud Node?
- It is PDK's main panel for a location. PDK describes it as a main panel with a single-door controller, so it runs one door itself and links the site's other Red controllers to the pdk.io cloud. In PDK's API, each cloud node represents a distinct geographic location within a customer's system.
- Do I need a server in the office for PDK?
- No access-control server is needed. Management runs in the pdk.io cloud, and the hardware on site is the Red Cloud Node and Red controllers on your network. You still need a working network and internet connection at each location for the cloud connection.
- Can PDK control gates and wireless locks?
- Yes. PDK sells Red Gate and Red Pedestal outdoor controllers and its own Red wireless locksets. Its API also lists ASSA ABLOY Aperio wireless locks, and anything else controlled by a relay, as devices. Ask your dealer which lock models fit your doors.
Related systems: UniFi Access · Brivo Access · Paxton10
Sources
- https://www.prodatakey.com/controllers
- https://developer.pdk.io/web/2.0/introduction/
- https://developer.pdk.io/web/2.0/rest/devices/
- https://developer.pdk.io/web/2.0/rest/webhooks/
- https://developer.pdk.io/web/2.0/streaming/
- https://developer.pdk.io/web/2.0/postman-collection
Last reviewed October 2026. ProdataKey pdk.io and other product names are trademarks of their respective owners. GateStride is independent and not affiliated with, endorsed by or a dealer for any manufacturer.