> For the complete documentation index, see [llms.txt](https://docs.ggwp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ggwp.com/ggwp-client-sdk/additional-supported-integrations/voice-vivox/vivox-unity-ssr-vs-ggwp-sdk.md).

# Vivox: Unity SSR vs GGWP SDK

There are two paths to integrate with GGWP Voice product if you are using Vivox with Unity or Unreal.

#### 1. Unity SSR

Unity has a [Server Side Recording (SSR)](https://services.docs.unity.com/ssr/v2/#tag/vivox-ssr/operation/postSSRMonitor) service for Vivox. Broadly the flow is as follows:

1. Customer enables Vivox SSR for their account by talking to Unity. (Ref: [SSR](https://docs.vivox.com/v5/general/core/5_19_0/en-us/Default.htm#Core/developer-guide/server-side-recording/ssr-overview.htm))
2. Once enabled, voice data can be forwarded to GGWP with the following workflow:

   1. GGWP configures an S3 bucket and shares the IAM with the customer
   2. Customer calls the SSR API to decide when it should trigger and store audio into S3
   3. GGWP ingests uploaded audio from S3 and processes through voice pipeline

#### 2. GGWP SDK

The GGWP SDK is available for Unity and Unreal with out-of-the-box support for Vivox, EOS and the Discord Social SDK. It also provides support for BYO C/C# APIs. Broadly the flow is as follows:

1. GGWP creates a tenant for customer and shares the API key
2. Customer builds an API on their server for authentication
3. Customer integrates SDK onto the client using included sample apps

   1. Calls the API built in 2-b
   2. Initializes the GGWP SDK with the result from (i)

   <figure><img src="/files/c6ZfygXJuZo9sqLXIcEu" alt=""><figcaption></figcaption></figure>

#### **Comparing SSR and SDK integration**

1. **Location of integration**

   SSR integration can be handled on customer server-side only without touching the client. SDK integration requires integration on the client and an associated API on the game server to support client authentication.
2. **Processing time**

   Processing audio through Vivox’s SSR workflow generally adds about 5-10min of latency. Using the GGWP SDK would only add a few seconds of latency.
3. **Integration efforts**

   While both paths are straightforward, integrating through Vivox SSR is slightly lower effort as no additional work is required on the client. Integrating through the GGWP SDK requires client and light server work, with the benefit of lower latency and costs.
4. **Pricing**

   Unity charges for SSR which is bundled into GGWP's voice usage billing when taking the SSR path.