SkyDibia Platform · Licensing
SkyDibia Platform can support a customer-operated hotspot, form part of a SkyDibia-managed service, or be independently licensed for an existing operating environment. Those relationships are not interchangeable.
Commercial pathways
Neither route is an instant software checkout. The implementation and responsibilities have to fit the real operating environment.
PATHWAY 01
For an approved hotspot where the customer or their staff operates the business and SkyDibia Platform forms part of the agreed operating solution.
PATHWAY 02
For a hotspot owner who wants SkyDibia to perform the agreed operational role. SkyDibia uses the Platform to operate the service; owner visibility does not automatically become an independent Platform licence.
PATHWAY 03
For an organisation that already has or controls its connectivity environment and wants to operate SkyDibia Platform under separately approved licensing terms.
What gets assessed
A workable deployment needs agreement across technology, operations, responsibilities and commercial terms.
Network environment, access flow, hosting assumptions, isolation requirements and technical compatibility.
Who manages customers, payments, technical review, access decisions, support and operational records.
Data responsibilities, authorised users, audit visibility and the human-review boundary around consequential actions.
Permitted use, support, limits, pricing and other terms that must be expressly agreed.
From interest to an agreed deployment
Each stage narrows uncertainty before implementation authority is considered.
Explain intended use, ownership, customers and the existing or proposed network.
Assess architecture, compatibility, responsibilities, hosting assumptions and integration needs.
Define permitted use, commercial conditions, support boundaries and relevant legal responsibilities.
Complete controlled onboarding and validation before any approved live deployment.
Important boundaries
These boundaries keep the public offer accurate while licensing, hosting and support models are still assessed case by case.
Platform licensing is not part of merchandise checkout and no public price is implied here.
Hosting, isolation and tenant architecture require an approved technical model.
No white-label, redistribution, resale or sublicensing right is granted by this page.
Support scope, response commitments and usage limits must be stated in the agreed commercial terms.
Share the intended use and existing environment so the appropriate licensing pathway can be assessed.