Xibo gives you Layouts, Regions and DataSets. None of them know what a Zabun pand is. That gap is where Gibeon sits.
Xibo has been around since 2009 and the open-source side is the real draw. If you have an IT person who likes control, you can run the CMS on-prem or take Xibo Cloud, build Layouts in the Layout Designer, slice them into Regions, attach a Playlist, push a Schedule out to a Display Profile. The Module Store gives you weather, RSS, video walls, the lot. For a logistics company or a hospital signage rollout, it is genuinely a good tool. The community is large, the documentation is decent, and you can self-host if that matters to you.
A Zabun kantoor in Roeselare or Kortrijk with one screen location does not have an IT department. The makelaar adds a pand, edits the prijs, swaps a photo, and expects the window screen to follow. With Zabun handling panden, klanten, prospecten and the mailing to Immoweb, the screen is just one more output channel. If your signage tool cannot read Zabun directly, someone ends up exporting a list every Monday, dropping it in PowerPoint, and forgetting on Friday. That is the opvolging nobody wants to own.
Gibeon talks to Zabun through their partner API, which we requested and maintain on your behalf. Every 30 minutes we pull the active panden for your kantoor: address, price, bedrooms, surface, EPC label, status, and the first five photos. An agent updates a price in Zabun at 10:14, the window screen reflects it by 10:45 at the latest. If your internet drops, the player keeps showing the last cached snapshot, so the etalage never goes black. No DataSet to build, no CSV in a shared folder, no manual beheer of a parallel list.
Technically you could try to wire Zabun into a DataSet, but you would be writing and maintaining that bridge yourself, and Zabun's API is partner-gated. Gibeon is a separate player setup. Most kantoren keep Xibo for non-listing screens if they have them, and put Gibeon on the window.
Yes. The 30-minute pull runs around the clock. An edit at 22:00 lands on the screen before 22:30. No one has to log in the next morning to refresh anything, which is the point for a small team without a dedicated agent for screen content.
The Gibeon player keeps showing the last cached snapshot of your panden, so the window keeps looking like a working etalage. When the API answers again, the next 30-minute cycle catches up. We monitor this on our side, you do not have to.
Make a free Gibeon account, ask Zabun to flip on the partner API for your kantoor, and check the window on Friday afternoon.
Plan een demo →