How large is the team?+
Small and deliberately so. The platform was built by one team with a consistent design, which is exactly why its pieces agree with each other. For delivery, the engagement is scoped to what can genuinely be committed to rather than to what would look impressive.
Can we speak to a reference?+
No, and the honest reason is that there is no external customer to refer you to yet. The platform runs a live consumer service, which is a different claim, and it is one you can check without asking anyone: open www.playboox.net. Where this leaves you is with evidence instead of assurance — the running service, the published architecture, the capability list with its gaps on it. If a customer reference is a hard requirement in your process, we do not meet it today.
Do we have to bring our own content?+
Yes. PLAYBOOX builds and operates the platform; the catalogue and the rights are yours. There is no content library bundled with this and no licensing arm behind it, which is worth saying plainly because several platform vendors do have one.
Is this a product or a consulting project?+
Both are available and they are different agreements. A licence gets you the platform and the Terraform to run it yourself. An implementation engagement stands it up with you. A managed agreement means we operate it. The platform underneath is the same in all three, and you can move between them without changing platforms.
Can we see it working before committing?+
Yes, and without talking to us first — the production consumer service is open in a browser. The demo page sets out what to look at if you are evaluating rather than browsing.
How do we see revenue and churn?+
Monthly recurring revenue in taka, a monthly revenue series and subscriber counts by status are real figures out of billing today. Churn, lifetime value and cohort retention are not built — no subscription state-transition history is recorded yet, so nothing distinguishes a cancellation today from one in March. That is a build, and the monetization pages say so rather than leaving it to a demo.
Which devices, and what about iOS?+
Web, Android phone and tablet, and Android TV ship today. iOS and Samsung Tizen are in development with no published date, because a date that slips is worse than no date. Roku, Fire TV, LG webOS and Apple TV have no application at all, and they are named individually on the applications page so their absence cannot be read as an oversight.
Whose developer account are the apps published under?+
Yours. That is how the live Android listing is published today, not a policy we intend to adopt. It follows that the listing, the reviews, the install base and the release timing are yours — and that a vendor who publishes under their own account keeps all of those.
What do you need from our team?+
Your real numbers in week one, infrastructure or cloud accounts early, access to the content and whatever describes it, brand assets and your own store accounts, merchant credentials from the gateway, and one person who can decide. The timeline page sets out which stage each is on the critical path for.
Can our team run it after handover?+
That is what a licence is for, and the implementation page answers the hiring question honestly: you need operational capability rather than streaming specialists, plus somebody reachable when hardware fails. The alternative is retaining the engineering with us and hiring nobody.
Why not just build it in-house?+
Sometimes that is the right answer, and the economics page gives you the model to test it rather than an argument. What a build costs is a streaming team for the time it takes; what it buys is a platform shaped exactly to you. The case against is that the integration between fifteen components is most of the work and none of the differentiation.
What happens if you are unavailable?+
It is a fair question and the answer is structural rather than reassuring: your estate is Terraform in your repository with runbooks written against it. That is precisely so the platform does not depend on the continued availability of any particular engineer, ours included.
Where are you based?+
Bangladesh, with delivery experience across regional streaming — including in-country peering, which is one of the largest available performance improvements for a regional audience and one of the most commonly missed.