We deploy it, integrate it,
and keep it running.
Beyond installs Purple over the hardware you already own, connects it to the systems you already run, and supports it after go-live. Preferred Purple partner and authorised distributor, working hands-on across South African venues.
Purple sells professional services too
Purple offers deployment, onboarding, training, custom integration work and an optional managed service. There are ROI and access-point coverage calculators, an open API with webhook delivery, and a four-step rollout: consult, customise, develop, evolve. On a standard estate with common hardware and common systems, that is often all you need — and you can buy it from Purple directly.
This page is about the estates where it isn’t.
Six things a venue still has to solve
None of these are faults in the platform. They are the normal gap between software that ships and software that runs in your building.
Your systems need a connector that may not exist
Purple ships over 400 pre-built connectors for the big platforms. If your property-management system, till software or loyalty tool is local or custom, there won’t be one, and someone has to build it.
The API has no SDK
Purple’s Company API is HMAC-signed and documented by example rather than by an installable library. Pulling your own venue and visitor data out means implementing the signing and mapping the responses yourself.
The tiers and add-ons have rules
SecurePass runs on a single SSID and won’t run alongside Paid WiFi. Insight Surveys only come with Engage. Verify is bundled from Capture up. Buying the wrong tier is an expensive way to learn the matrix.
Multi-SSID estates need scoping first
A venue running separate guest, staff, tenant and paid networks can’t simply switch features on. Which network each capability lands on is a decision, and it has to be made before install day.
POPIA stays your obligation
The platform gives you the compliance controls. Which consent applies to which message, in which channel, for your venue — that is a design job, and it sits with you.
Someone has to be there on the day
Site surveys, controller configuration, and the match day or September intake when it has to work first time. That is a person in the building, in your timezone.
That work is the job
We are integrators. Everything below is running code we can walk you through, not a capability statement.
We wrote our own Purple API client
Built from the specification and HMAC-signed, running in production. It reads live venue and visitor data two ways: webhooks for capture as it happens, plus a nightly sweep that reconciles anything the webhook stream missed.
We build the connectors that don’t exist
We have joined Purple guest data to WhatsApp through Twilio, and resolved one customer across four separate identifiers — Purple ID, mobile number, email and device — into a single profile, in production.
We build POPIA into the send path
Consent is checked by one gate that every message passes through, so it can’t be honoured in one place and forgotten in another. Our build pipeline blocks non-compliant content from reaching messaging code before it can be merged.
We write software, not just configuration
We run our own applications on Google Cloud, including AI document checks that read CIDB, SARS and ID documents and flag what looks wrong. When a venue needs something Purple doesn’t sell, we can build it.
We scope before we quote
Which network each capability lands on, which tier actually fits, and what happens to the networks a feature can’t cover. You get that in writing before anyone touches your controller.
We support it after go-live
Deployment and onboarding, then the peak weekends. Same team, same country, same working hours as your venue.
We wire together the Purple toolkit, the tier that fits and your own systems — across every venue type we serve.
What we have done
Not a pilot, and not a partnership announcement. Live estates we deploy, integrate and keep compliant.
Tell us your estate — you’ll get it back in writing
A scoping call covers which tier fits, which network each capability lands on, and what has to be built. You keep the write-up either way.
Get your estate scoped