How fast the first frame arrives
Open a title on your own connection rather than on a stand at a conference. Start-up time is the metric a viewer feels first and it is the one a demo environment usually flatters.
Most vendors offer a trial tenant assembled for trials. What is offered here is the platform running a real consumer service with a real catalogue and real viewers, reachable from your browser without a form, a sales call or an account.
No form, no account, no scheduled call. Both hosts resolved on 30 August 2026 and are re-checkable at any moment.
| What | Where | What you can do without us |
|---|---|---|
| The consumer service | www.playboox.net | Browse the catalogue, start playback, use it on a phone and on a desktop, on your own connection |
| The operator console | admin.playboox.net | Confirm it resolves and is deployed. It is a production console holding a real operator's data, so it is not open to sign in |
| The architecture behind both | 33 engineering pages on this site | Read how it is built, including the trade-offs and what is not built |
| What the platform can and cannot do | /platform/features | 55 capabilities with a status on every row, including the 23 with no code |
A demo is usually driven by whoever is selling. This one is not, so here is what we would point at.
Open a title on your own connection rather than on a stand at a conference. Start-up time is the metric a viewer feels first and it is the one a demo environment usually flatters.
Jump into the middle of a film. A seek that resolves quickly is a range-aware cache doing its job; one that stalls is an origin fetch pretending to be a CDN.
Throttle your network and watch the ladder step down. What you want to see is the picture soften before the buffer empties, not a spinner after it does.
The Android TV application is a real leanback build rather than a stretched phone layout. If living-room viewing matters to your audience, it is the surface worth judging.
Read the capability spec sheet alongside the service. A platform that publishes what it cannot do is telling you what the first three months of an engagement will actually be about.
Judge the team by the pages describing the trade-offs rather than by the ones describing the benefits. That is the closest available proxy for how the next decision will be made.
What is on this page is everything currently open to the public. A separate tenant with your own catalogue, your own console access and your own credentials is available on request, and it is set up as part of an evaluation rather than self-served from here.
There is deliberately no sign-up link, no sandbox URL and no shared credential on this page, because none exists today. A demo environment promised on a page and missing on the first click is a worse first impression than no demo page at all, and it is the failure mode this section is written to avoid.
If an evaluation tenant is what you need in order to proceed, ask for it in the first conversation. It is a real thing that gets built for you, not a link somebody forgot to add.
The real thing. It is the production consumer service, running on the architecture described across this site, serving actual viewers. There is no separate demo deployment to flatter.
Not into that one. It is a production console holding a real operator's data. A walkthrough is a scheduled conversation, and a console of your own comes with an evaluation tenant.
Not self-served, and there is no sign-up link on this page because there is nothing behind it. A scoped tenant is set up on request during an evaluation.
Then you have learnt something real about it, which is more than a curated demo would have told you. No availability figure is published anywhere on this site, and the service-levels page explains why.
The viewer-facing service is open to anyone. The operator console is not, so a walkthrough of it is a scheduled conversation rather than a link.