History: Before you start

Every change to this page, newest first. Expand an entry to see what changed.

1 Oct 2026 · +4 −4 lines

Show changes

⋯
  | ☐ | The list of films and licence dates in your agreement | The catalog shows only films your licence covers | [Catalog](concepts/catalog.md) |
  | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is tied to them and cannot be moved to other IDs later | [Player SDK licence](#player-sdk-licence) |
- | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) |
+ | ☐ | Your environments (for example staging and production) | Each one needs its own playback key, which your developers create themselves | [Authentication](authentication.md) |
  | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) |
- | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences, keys and go-live all happen there | [Get onboarded](#get-onboarded) |
+ | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences and go-live all happen there | [Get onboarded](#get-onboarded) |
  
  ## 2. Get onboarded {#get-onboarded}
⋯
  | 3. Test organisation and film licences | Wandura decides whether you test in a separate test organisation, and licenses the films you test with to the organisation you test in. | The films you want to test with, from your agreement. |
  | 4. Player SDK trial | Wandura registers your app IDs and issues a trial Player SDK licence. You get access to the Player SDK guide: it is available after onboarding, on the portal, under partner.wandura.ai → **Developers** → **Player SDK** (sign-in required, **Developer** or **Admin** role). | Your final iOS bundle ID and Android package name. |
- | 5. Staging keys | Your developers create read-only keys themselves on the **Developers** page. Wandura issues a playback key for staging. | Which environments need a playback key, for example staging. |
- | 6. Production key and paid licence | At go-live, Wandura issues your production playback key, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. |
+ | 5. Staging keys | Your developers create their staging keys themselves on the **Developers** page, the playback key included (**Stream films in an app**). If a playback key leaks, anyone can stream your licensed films, so revoke it immediately. | Nothing: no request to Wandura is needed. |
+ | 6. Production key and paid licence | At go-live, your developers create the production playback key the same way, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. |
  
  ## 3. Player SDK licence and price {#player-sdk-licence}
⋯

1 Oct 2026 · +21 −8 lines

Show changes

⋯
  | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) |
  | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) |
- | ☐ | How to reach Wandura (the channel named in your agreement) | For licences, keys and go-live | [Support](help/support.md) |
+ | ☐ | Access to your team's Wandura Discord channel | Onboarding, licences, keys and go-live all happen there | [Get onboarded](#get-onboarded) |
  
- ## 2. Player SDK licence and price {#player-sdk-licence}
+ ## 2. Get onboarded {#get-onboarded}
  
- Episodes are encrypted, so your app must play them with the Player SDK that Wandura licenses to you. A standard HLS player cannot decrypt them.
+ Each partner team works with Wandura in **its own Discord channel**: your team's Wandura Discord channel. Onboarding runs in the six steps below, in this order. Each step starts once Wandura has what it needs from you.
  
+ | Step | What happens | What you send |
+ |---|---|---|
+ | 1. Ask | You post in your team's Wandura Discord channel that you are ready to integrate. | Your organisation name and the email of the person who will be its **Admin**. |
+ | 2. Organisation and members | Wandura creates your organisation on [partner.wandura.ai](https://partner.wandura.ai) and invites your Admin and your developers. Developers get the **Developer** role. | The emails of your backend developers. |
+ | 3. Test organisation and film licences | Wandura decides whether you test in a separate test organisation, and licenses the films you test with to the organisation you test in. | The films you want to test with, from your agreement. |
+ | 4. Player SDK trial | Wandura registers your app IDs and issues a trial Player SDK licence. You get access to the Player SDK guide: it is available after onboarding, on the portal, under partner.wandura.ai → **Developers** → **Player SDK** (sign-in required, **Developer** or **Admin** role). | Your final iOS bundle ID and Android package name. |
+ | 5. Staging keys | Your developers create read-only keys themselves on the **Developers** page. Wandura issues a playback key for staging. | Which environments need a playback key, for example staging. |
+ | 6. Production key and paid licence | At go-live, Wandura issues your production playback key, and the paid Player SDK licence replaces the trial. | The result of your [test plan](integration-guide.md#phase-5) and your planned go-live date. |
+ 
+ ## 3. Player SDK licence and price {#player-sdk-licence}
+ 
+ Episodes are encrypted, so your app must play them with the Player SDK. A standard HLS player cannot decrypt them. Wandura registers your app IDs and issues the Player SDK licence; your organisation pays for it.
+ 
  | Licence | Covers | List price | Notes |
  |---|---|---|---|
⋯
  - **One licence per app.** Two different apps need two licences, even if they come from the same company.
  - **IDs are final.** Changing the bundle ID or package name after the licence is issued is not supported: the app loses the right to use the SDK.
- - **Prices change.** The figures above are list prices. Your organisation pays for the Player SDK licence; your agreement with Wandura sets the real price.
+ - **Prices change.** The figures above are list prices. Your agreement with Wandura sets the real price.
  
- ## 3. What your backend builds {#backend}
+ ## 4. What your backend builds {#backend}
  
  | Build | What it does | Details |
⋯
  | ☐ Error mapping + monitoring | Turns API errors into viewer messages; watches error rates | [Errors](concepts/errors.md) |
  
- ## 4. What your app builds {#app}
+ ## 5. What your app builds {#app}
  
  | Build | What it does | Details |
  |---|---|---|
- | ☐ Player SDK integration (per platform) | Plays encrypted episodes; the onboarding pack names the calls | [Playback](concepts/playback.md) |
+ | ☐ Player SDK integration (per platform) | Plays encrypted episodes; the Player SDK guide on the portal names the calls | [Playback](concepts/playback.md) |
  | ☐ Device values | Reads two values from the SDK and sends them with each ticket request | [Device values](concepts/playback.md#send-the-device-values) |
  | ☐ Paywall screens | Free episodes, unlock, subscription — your rules | [Paywall first](integration-guide.md#paywall-first) |
⋯
  | ☐ Viewer messages | What the viewer sees for each error | [Viewer messages](integration-guide.md#viewer-messages) |
  
- ## 5. Before go-live {#go-live}
+ ## 6. Before go-live {#go-live}
  
  - ☐ Staging passes the [test plan](integration-guide.md#phase-5).
⋯

1 Oct 2026 · +6 −6 lines

Show changes

  # Before you start
  
- > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md).
+ > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app, which your organisation pays for (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md).
  
  > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path (coming soon) needs no Player SDK licence.
⋯
  | ☐ | **Final** iOS bundle ID and Android package name | The Player SDK licence is tied to them and cannot be moved to other IDs later | [Player SDK licence](#player-sdk-licence) |
  | ☐ | Your environments (for example staging and production) | Each one needs its own playback key | [Authentication](authentication.md) |
- | ☐ | Who pays for the Player SDK licence, and from when | Settled in your agreement with Wandura | [Player SDK licence](#player-sdk-licence) |
- | ☐ | A named contact at Wandura | For licences, keys and go-live | [Support](help/support.md) |
+ | ☐ | Budget for the Player SDK licence: your organisation pays for it | Agree the tier and start date with Wandura | [Player SDK licence](#player-sdk-licence) |
+ | ☐ | How to reach Wandura (the channel named in your agreement) | For licences, keys and go-live | [Support](help/support.md) |
  
  ## 2. Player SDK licence and price {#player-sdk-licence}
⋯
  | **Standard** — mobile | iOS **and** Android of **one** app (one bundle ID + one package name) | about **US$2,860 per app per year** | Enough to play Wandura's encrypted films. |
  | Premium — mobile | Same, with extra vendor features | about US$32,790 per app per year | Not needed for Wandura films. |
- | Web player | Web | no licence fee at list price | Check with your contact before planning a web app. |
+ | Web player | Web | no licence fee at list price | Check with Wandura before planning a web app. |
  | Trial | One app, for testing | free, about 30 days | Upgrading a trial to a paid licence does **not** require a new app release. |
  
  - **One licence per app.** Two different apps need two licences, even if they come from the same company.
  - **IDs are final.** Changing the bundle ID or package name after the licence is issued is not supported: the app loses the right to use the SDK.
- - **Prices change.** The figures above are list prices. Your agreement with Wandura sets the real price and who pays it.
+ - **Prices change.** The figures above are list prices. Your organisation pays for the Player SDK licence; your agreement with Wandura sets the real price.
  
  ## 3. What your backend builds {#backend}
⋯
  - ☐ Staging passes the [test plan](integration-guide.md#phase-5).
  - ☐ Production key and paid Player SDK licence are in place.
- - ☐ The [go-live checklist](integration-guide.md#go-live-checklist) is done with your Wandura contact.
+ - ☐ The [go-live checklist](integration-guide.md#go-live-checklist) is done with Wandura.

1 Oct 2026 · +2 −0 lines

Show changes

⋯
  > **TL;DR** — To stream Wandura films your team needs three things ready before coding: an organisation on partner.wandura.ai with licences for your films, a **Player SDK licence** for each app (list price about **US$2,860 per app per year** for iOS + Android), and your final app IDs. Then you build two pieces: a **backend** that syncs the catalog and requests playback tickets, and an **app** that plays episodes through the Player SDK. The full path is in the [integration guide](integration-guide.md).
  
+ > **Note:** Showing only videos with no rights to protect (for example fitness clips)? The [open video](open-video.md) path (coming soon) needs no Player SDK licence.
+ 
  ## 1. Prepare (no code yet) {#prepare}
  
⋯

30 Sept 2026 · Page created