Start with the PHP SDK and integration guide. A paid White-label Pilot is available only for qualified projects that need a separately scoped rollout.
Choose the SDK when your team can integrate into an existing site or product. Use a paid White-label Pilot only when the required rollout cannot be evaluated through the SDK alone.
The main integration path for teams embedding live streaming in an existing PHP, WordPress, or product experience.
Apply for access
Technical route for development teams
For teams with a defined technical integration path.
For a real branded-live project that cannot be evaluated through the SDK alone and needs a defined delivery scope.
Paid, scope-based
Proposal after qualified review
For projects with a commercial owner, technical owner, and launch context.
For requirements outside the SDK path or a paid Pilot scope that need a separately scoped implementation discussion.
Discuss your requirement
Choose Developer SDK when your team has a clear integration path. Choose a Paid White-label Pilot when a real project needs a separately scoped branded rollout. Discuss custom requirements when they are outside both paths.
Developer access starts a technical evaluation. Production operating terms are reviewed with the team before commitment, and Paid White-label Pilots are nonzero-fee, scope-based engagements proposed after qualified review.
Custom hosting or operating requirements are reviewed separately. Any service commitments are defined only in a separate agreement.
It covers one-time custom development for a tailored app or workflow. Hosting and streaming usage are billed by plan, and major future changes are quoted separately. Pricing is determined by project scope.
Start with the SDK when your technical plan is clear. If a branded rollout needs a separately scoped service, request a paid White-label Pilot discussion.