Integrations
Designed to coexist with the systems you already run.
Destinations already operate parking, security, payments, signage and building management. Knull is designed for integration with that estate — with every connection scoped, tested and agreed per deployment.
01Integration architecture
Where Knull can connect.
APIs & webhooks
Fleet, dock and session events exposed to destination systems where a deployment requires it.
Designed for integrationIdentity & SSO
Staff access to the operator platform aligned with the destination's identity practices.
Designed for integrationPayments
Where a deployment uses paid sessions, payment handling is scoped with the operator's chosen provider.
Designed for integrationFacilities systems
Service and exception events shared with facilities management workflows.
Designed for integrationFootfall systems
Context from existing footfall counting to inform network planning.
Designed for integrationBI platforms
Aggregate reporting exported to the destination's business-intelligence tools.
Designed for integrationDestination apps
Availability information surfaced in a destination's own app or website.
Designed for integrationDigital wayfinding
Dock locations and availability shown within wayfinding systems.
Designed for integration
02How we classify integrations
We will tell you exactly what exists.
- Available
- Implemented and verified in operation.
- Supported
- Formally supported by Knull as a standard option.
- Custom integration
- Delivered through project-specific engineering, where confirmed.
- Roadmap
- Explicitly planned, not yet delivered.
- Designed for integration
- The system is designed to support it; scope is agreed per deployment.
No named third-party product is listed as compatible on this page. Integration scope is confirmed in writing during deployment design.
Next step
Bring your IT and security team into the conversation.
A technical briefing covers architecture, data flows and integration scoping.