SPI-RFIDBridge
RFID identification as platform events.
SPI-RFIDBridge connects RFID readers to SPIDEX and turns tag reads into structured, timestamped platform events tied to a location and an asset.
Why it exists
RFID installations tend to end at the reader. The reads exist, but reaching them means a separate integration for every reader model and every site.
- ·Reader integration
- ·Tag read to platform event conversion
- ·Location and asset context
- ·Local filtering and de-duplication
Adjacent to the reader installation at gates, doorways and checkpoints.
Security- · Distinct device identity
- · Authenticated platform connection
- · Encrypted transport
- · Signed firmware images
- · Access-controlled remote sessions
How it fits the stack
Events stream into SPIEngine and can be routed onward through APIs and integrations.
About SPIEngineHardware detail
Published values are confirmed. Anything hardware-dependent that has not been verified by engineering is marked rather than estimated.
- Reader compatibility
- Pending verification
- Tag standards
- Pending verification
- Device framework
- C3F
- Power input
- Pending verification
- Mounting
- Pending verification
Highlighted entries are hardware-dependent values awaiting engineering confirmation. They are published only once verified — ask for the current datasheet during evaluation.
Where it is applied
Movement and checkpoint tracking
Access and zoning
Inventory and stock movement
Evaluating SPI-RFIDBridge?
Ask for the current datasheet, lead time and integration detail. Anything not yet verified will be identified as such.