diff --git a/content/en/feature_flags/client/unity-openfeature.md b/content/en/feature_flags/client/unity-openfeature.md
new file mode 100644
index 00000000000..705263c1d1b
--- /dev/null
+++ b/content/en/feature_flags/client/unity-openfeature.md
@@ -0,0 +1,285 @@
+---
+title: Unity Feature Flags (OpenFeature)
+description: Set up Datadog Feature Flags for Unity applications using OpenFeature.
+aliases:
+  - /feature_flags/setup/unity-openfeature/
+further_reading:
+- link: "/feature_flags/client/"
+  tag: "Documentation"
+  text: "Client-Side Feature Flags"
+- link: "/real_user_monitoring/application_monitoring/unity/"
+  tag: "Documentation"
+  text: "Unity Monitoring"
+- link: "https://github.com/DataDog/dd-sdk-unity"
+  tag: "Source Code"
+  text: "dd-sdk-unity source code"
+- link: "https://openfeature.dev/"
+  tag: "External"
+  text: "OpenFeature"
+---
+
+<div class="alert alert-info">This page documents the <strong>OpenFeature integration</strong> for Unity Feature Flags. For the direct FlagsClient API (without OpenFeature), see <a href="/feature_flags/client/unity/">Unity Feature Flags</a>.</div>
+
+## Overview
+
+This page describes how to instrument your Unity application with the Datadog Feature Flags SDK using the OpenFeature standard. Datadog feature flags provide a unified way to remotely control feature availability in your app, experiment safely, and deliver new experiences with confidence.
+
+This guide explains how to install and enable the SDK, register the Datadog OpenFeature provider, set an evaluation context, and evaluate flags.
+
+## Installation
+
+Declare the Datadog Unity SDK as a dependency in your project. The Datadog Unity SDK includes feature flags support.
+
+1. Install the [External Dependency Manager for Unity (EDM4U)][1]. This can be done using [Open UPM][2].
+
+2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.
+
+3. (Android only) Configure your project to use [Gradle templates][4], and enable both `Custom Main Template` and `Custom Gradle Properties Template`.
+
+4. (Android only) If you build and receive `Duplicate class` errors (common in Unity 2022.x), add the following code to the `dependencies` block of your `mainTemplate.gradle`:
+
+   ```groovy
+   constraints {
+        implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.8.0") {
+            because("kotlin-stdlib-jdk8 is now a part of kotlin-stdlib")
+        }
+   }
+   ```
+
+## Initialize the SDK
+
+Initialize Datadog as early as possible in your app lifecycle. Navigate to your `Project Settings` and click on the `Datadog` section to configure your client token, environment, and other settings.
+
+For more information about setting up the Unity SDK, see [Unity Monitoring Setup][5].
+
+## Getting started
+
+After the SDK is initialized, set up feature flags with these steps:
+
+{{< code-block lang="csharp" >}}
+using Datadog.Unity.Flags;
+using OpenFeature;
+using OpenFeature.Model;
+using UnityEngine;
+
+// 1. Enable the Flags feature after Datadog SDK initialization
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true
+));
+
+// 2. Create the Datadog provider and register it with OpenFeature
+var provider = DdFlags.Instance.CreateProvider();
+await Api.Instance.SetProviderAsync(provider);
+
+// 3. Get an OpenFeature client
+var client = Api.Instance.GetClient();
+
+// 4. Set the evaluation context
+await client.SetContextAsync(
+    EvaluationContext.Builder()
+        .SetTargetingKey("user-123")
+        .Set("email", "user@example.com")
+        .Set("tier", "premium")
+        .Build()
+);
+
+// 5. Evaluate flags
+var isNewCheckoutEnabled = await client.GetBooleanValueAsync("checkout.new", false);
+Debug.Log($"checkout.new = {isNewCheckoutEnabled}");
+{{< /code-block >}}
+
+## Enable flags
+
+After initializing Datadog, enable flags in your application code:
+
+{{< code-block lang="csharp" >}}
+using Datadog.Unity.Flags;
+
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true
+));
+{{< /code-block >}}
+
+You can also pass additional configuration options; see [Advanced configuration](#advanced-configuration).
+
+## Register the provider
+
+Create the Datadog provider and register it with the OpenFeature `Api`:
+
+{{< code-block lang="csharp" >}}
+using OpenFeature;
+
+var provider = DdFlags.Instance.CreateProvider();
+await Api.Instance.SetProviderAsync(provider);
+{{< /code-block >}}
+
+Retrieve a client anywhere in your app using the OpenFeature API:
+
+{{< code-block lang="csharp" >}}
+var client = Api.Instance.GetClient();
+{{< /code-block >}}
+
+You can also register named providers and retrieve named clients:
+
+{{< code-block lang="csharp" >}}
+var provider = DdFlags.Instance.CreateProvider();
+await Api.Instance.SetProviderAsync("checkout", provider);
+var client = Api.Instance.GetClient("checkout");
+{{< /code-block >}}
+
+## Set the evaluation context
+
+Define who or what the flag evaluation applies to using an OpenFeature `EvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to ensure proper targeting.
+
+{{< code-block lang="csharp" >}}
+using OpenFeature.Model;
+
+await client.SetContextAsync(
+    EvaluationContext.Builder()
+        .SetTargetingKey("user-123")
+        .Set("email", "user@example.com")
+        .Set("tier", "premium")
+        .Build()
+);
+{{< /code-block >}}
+
+This triggers a fetch of flag assignments from the server. Flag updates are available for subsequent evaluations once the operation completes.
+
+## Evaluate flags
+
+After setting the evaluation context, you can start reading flag values throughout your app. Flag evaluation is _local and instantaneous_—the SDK uses locally cached data, so no network requests occur when evaluating flags. This makes evaluations safe to perform on the main thread.
+
+Each flag is identified by a _key_ (a unique string) and can be evaluated with a _typed method_ that returns a value of the expected type. If the flag doesn't exist or cannot be evaluated, the SDK returns the provided default value.
+
+The Unity SDK uses the [OpenFeature][6] standard API for flag evaluation.
+
+### Boolean flags
+
+Use `GetBooleanValueAsync(key, defaultValue)` for flags that represent on/off or true/false conditions. For example:
+
+{{< code-block lang="csharp" >}}
+var isNewCheckoutEnabled = await client.GetBooleanValueAsync("checkout.new", false);
+
+if (isNewCheckoutEnabled)
+{
+    ShowNewCheckoutFlow();
+}
+else
+{
+    ShowLegacyCheckout();
+}
+{{< /code-block >}}
+
+### String flags
+
+Use `GetStringValueAsync(key, defaultValue)` for flags that select between multiple variants or configuration strings. For example:
+
+{{< code-block lang="csharp" >}}
+var theme = await client.GetStringValueAsync("ui.theme", "light");
+
+switch (theme)
+{
+    case "light":
+        SetLightTheme();
+        break;
+    case "dark":
+        SetDarkTheme();
+        break;
+    default:
+        SetLightTheme();
+        break;
+}
+{{< /code-block >}}
+
+### Integer and double flags
+
+For numeric flags, use `GetIntegerValueAsync(key, defaultValue)` or `GetDoubleValueAsync(key, defaultValue)`. These are appropriate when a feature depends on a numeric parameter such as a limit, percentage, or multiplier:
+
+{{< code-block lang="csharp" >}}
+var maxItems = await client.GetIntegerValueAsync("cart.items.max", 20);
+var priceMultiplier = await client.GetDoubleValueAsync("pricing.multiplier", 1.0);
+{{< /code-block >}}
+
+### Object flags
+
+For structured or JSON-like data, use `GetObjectValueAsync(key, defaultValue)`. This method returns an OpenFeature `Value` object, which can represent primitives, arrays, or dictionaries. Object flags are useful for remote configuration scenarios where multiple properties need to be provided together. For example:
+
+{{< code-block lang="csharp" >}}
+var config = await client.GetObjectValueAsync(
+    "ui.config",
+    new Value(new Structure(new Dictionary<string, Value>
+    {
+        { "color", new Value("#00A3FF") },
+        { "fontSize", new Value(14) }
+    }))
+);
+
+var color = config.AsStructure["color"].AsString;
+var fontSize = config.AsStructure["fontSize"].AsInteger;
+{{< /code-block >}}
+
+### Flag evaluation details
+
+When you need more than just the flag value, use the detail methods. These methods return both the evaluated value and metadata explaining the evaluation:
+
+* `GetBooleanDetailsAsync(key, defaultValue)` -> `FlagEvaluationDetails<bool>`
+* `GetStringDetailsAsync(key, defaultValue)` -> `FlagEvaluationDetails<string>`
+* `GetIntegerDetailsAsync(key, defaultValue)` -> `FlagEvaluationDetails<int>`
+* `GetDoubleDetailsAsync(key, defaultValue)` -> `FlagEvaluationDetails<double>`
+* `GetObjectDetailsAsync(key, defaultValue)` -> `FlagEvaluationDetails<Value>`
+
+For example:
+
+{{< code-block lang="csharp" >}}
+var details = await client.GetStringDetailsAsync("paywall.layout", "control");
+
+Debug.Log($"Value: {details.Value}");         // Evaluated value (for example: "A", "B", or "control")
+Debug.Log($"Variant: {details.Variant}");     // Variant name, if applicable
+Debug.Log($"Reason: {details.Reason}");       // Description of why this value was chosen (for example: "TARGETING_MATCH" or "DEFAULT")
+Debug.Log($"ErrorType: {details.ErrorType}"); // The error that occurred during evaluation, if any
+{{< /code-block >}}
+
+Flag details may help you debug evaluation behavior and understand why a user received a given value.
+
+## Advanced configuration
+
+The `DdFlags.Enable()` API accepts optional configuration with options listed below.
+
+{{< code-block lang="csharp" >}}
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true,
+    evaluationFlushIntervalSeconds: 10.0f
+));
+{{< /code-block >}}
+
+`trackExposures`
+: When `true` (default), the SDK automatically records an _exposure event_ when a flag is evaluated. These events contain metadata about which flag was accessed, which variant was served, and under what context. They are sent to Datadog so you can later analyze feature adoption. Set to `false` to disable exposure tracking.
+
+`trackEvaluations`
+: When `true` (default), the SDK tracks flag evaluations and sends aggregated evaluation telemetry to Datadog. This enables analytics about flag usage patterns and performance. Set to `false` to disable evaluation tracking.
+
+`evaluationFlushIntervalSeconds`
+: The interval in seconds at which batched evaluation events are sent to Datadog. Accepted values are between `1` and `60`. Default is `10.0` seconds.
+
+`customFlagsEndpoint`
+: Configures a custom server URL for retrieving flag assignments.
+
+`customExposureEndpoint`
+: Configures a custom server URL for sending flags exposure data.
+
+`customEvaluationEndpoint`
+: Configures a custom server URL for sending flags evaluation telemetry.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://github.com/googlesamples/unity-jar-resolver
+[2]: https://openupm.com/packages/com.google.external-dependency-manager/
+[3]: https://github.com/DataDog/unity-package
+[4]: https://docs.unity3d.com/Manual/gradle-templates.html
+[5]: /real_user_monitoring/application_monitoring/unity/setup
+[6]: https://openfeature.dev/
diff --git a/content/en/feature_flags/client/unity.md b/content/en/feature_flags/client/unity.md
new file mode 100644
index 00000000000..338ca77c49a
--- /dev/null
+++ b/content/en/feature_flags/client/unity.md
@@ -0,0 +1,284 @@
+---
+title: Unity Feature Flags
+description: Set up Datadog Feature Flags for Unity applications.
+aliases:
+  - /feature_flags/setup/unity/
+further_reading:
+- link: "/feature_flags/client/"
+  tag: "Documentation"
+  text: "Client-Side Feature Flags"
+- link: "/real_user_monitoring/application_monitoring/unity/"
+  tag: "Documentation"
+  text: "Unity Monitoring"
+- link: "https://github.com/DataDog/dd-sdk-unity"
+  tag: "Source Code"
+  text: "dd-sdk-unity source code"
+---
+
+<div class="alert alert-info">This page documents the <strong>direct FlagsClient API</strong> for Unity Feature Flags. If you're looking for OpenFeature integration, see <a href="/feature_flags/client/unity-openfeature/">Unity Feature Flags (OpenFeature)</a>.</div>
+
+## Overview
+
+This page describes how to instrument your Unity application with the Datadog Feature Flags SDK. Datadog feature flags provide a unified way to remotely control feature availability in your app, experiment safely, and deliver new experiences with confidence.
+
+This guide explains how to install and enable the SDK, create and use a `FlagsClient`, and configure advanced options.
+
+## Installation
+
+Declare the Datadog Unity SDK as a dependency in your project. The Datadog Unity SDK includes feature flags support.
+
+1. Install the [External Dependency Manager for Unity (EDM4U)][1]. This can be done using [Open UPM][2].
+
+2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.
+
+3. (Android only) Configure your project to use [Gradle templates][4], and enable both `Custom Main Template` and `Custom Gradle Properties Template`.
+
+4. (Android only) If you build and receive `Duplicate class` errors (common in Unity 2022.x), add the following code to the `dependencies` block of your `mainTemplate.gradle`:
+
+   ```groovy
+   constraints {
+        implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.8.0") {
+            because("kotlin-stdlib-jdk8 is now a part of kotlin-stdlib")
+        }
+   }
+   ```
+
+## Initialize the SDK
+
+Initialize Datadog as early as possible in your app lifecycle. Navigate to your `Project Settings` and click on the `Datadog` section to configure your client token, environment, and other settings.
+
+For more information about setting up the Unity SDK, see [Unity Monitoring Setup][5].
+
+## Getting started
+
+After the SDK is initialized, set up feature flags with these steps:
+
+{{< code-block lang="csharp" >}}
+using System.Collections.Generic;
+using Datadog.Unity.Flags;
+using UnityEngine;
+
+// 1. Enable the Flags feature after Datadog SDK initialization
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true
+));
+
+// 2. Create a client (once, at startup)
+var client = DdFlags.Instance.CreateClient();
+
+// 3. Set the evaluation context (fetches flag assignments from the server)
+client.SetEvaluationContext(
+    new FlagsEvaluationContext(
+        targetingKey: "user-123",
+        attributes: new Dictionary<string, object>
+        {
+            { "email", "user@example.com" },
+            { "tier", "premium" }
+        }
+    ),
+    onComplete: success =>
+    {
+        if (success)
+        {
+            // 4. Evaluate flags — local and instantaneous
+            var isNewCheckoutEnabled = client.GetBooleanValue("checkout.new", false);
+            Debug.Log($"checkout.new = {isNewCheckoutEnabled}");
+        }
+    }
+);
+{{< /code-block >}}
+
+## Enable flags
+
+After initializing Datadog, enable flags in your application code:
+
+{{< code-block lang="csharp" >}}
+using Datadog.Unity.Flags;
+
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true
+));
+{{< /code-block >}}
+
+You can also pass additional configuration options; see [Advanced configuration](#advanced-configuration).
+
+## Create and retrieve a client
+
+Create a client once, typically during app startup, and hold a reference to it:
+
+{{< code-block lang="csharp" >}}
+var client = DdFlags.Instance.CreateClient(); // Creates the default client
+{{< /code-block >}}
+
+You can also create multiple clients by providing the `name` parameter:
+
+{{< code-block lang="csharp" >}}
+var checkoutClient = DdFlags.Instance.CreateClient("checkout");
+{{< /code-block >}}
+
+<div class="alert alert-info">If a client with the given name already exists, the existing instance is reused.</div>
+
+## Set the evaluation context
+
+Define who or what the flag evaluation applies to using a `FlagsEvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to ensure proper targeting.
+
+{{< code-block lang="csharp" >}}
+client.SetEvaluationContext(
+    new FlagsEvaluationContext(
+        targetingKey: "user-123",
+        attributes: new Dictionary<string, object>
+        {
+            { "email", "user@example.com" },
+            { "tier", "premium" }
+        }
+    ),
+    onComplete: success =>
+    {
+        if (success)
+        {
+            Debug.Log("Flags loaded successfully!");
+        }
+    }
+);
+{{< /code-block >}}
+
+This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations once the background operation completes.
+
+## Evaluate flags
+
+After creating the `FlagsClient` and setting its evaluation context, you can start reading flag values throughout your app. Flag evaluation is _local and instantaneous_—the SDK uses locally cached data, so no network requests occur when evaluating flags. This makes evaluations safe to perform on the main thread.
+
+Each flag is identified by a _key_ (a unique string) and can be evaluated with a _typed method_ that returns a value of the expected type. If the flag doesn't exist or cannot be evaluated, the SDK returns the provided default value.
+
+### Boolean flags
+
+Use `GetBooleanValue(key, defaultValue)` for flags that represent on/off or true/false conditions. For example:
+
+{{< code-block lang="csharp" >}}
+var isNewCheckoutEnabled = client.GetBooleanValue("checkout.new", false);
+
+if (isNewCheckoutEnabled)
+{
+    ShowNewCheckoutFlow();
+}
+else
+{
+    ShowLegacyCheckout();
+}
+{{< /code-block >}}
+
+### String flags
+
+Use `GetStringValue(key, defaultValue)` for flags that select between multiple variants or configuration strings. For example:
+
+{{< code-block lang="csharp" >}}
+var theme = client.GetStringValue("ui.theme", "light");
+
+switch (theme)
+{
+    case "light":
+        SetLightTheme();
+        break;
+    case "dark":
+        SetDarkTheme();
+        break;
+    default:
+        SetLightTheme();
+        break;
+}
+{{< /code-block >}}
+
+### Integer and double flags
+
+For numeric flags, use `GetIntegerValue(key, defaultValue)` or `GetDoubleValue(key, defaultValue)`. These are appropriate when a feature depends on a numeric parameter such as a limit, percentage, or multiplier:
+
+{{< code-block lang="csharp" >}}
+var maxItems = client.GetIntegerValue("cart.items.max", 20);
+var priceMultiplier = client.GetDoubleValue("pricing.multiplier", 1.0);
+{{< /code-block >}}
+
+### Object flags
+
+For structured or JSON-like data, use `GetObjectValue(key, defaultValue)`. This method returns an `object`, which can be cast to the appropriate type. Object flags are useful for remote configuration scenarios where multiple properties need to be provided together. For example:
+
+{{< code-block lang="csharp" >}}
+var config = client.GetObjectValue(
+    "ui.config",
+    new Dictionary<string, object>
+    {
+        { "color", "#00A3FF" },
+        { "fontSize", 14 }
+    }
+);
+
+if (config is Dictionary<string, object> configDict)
+{
+    var color = configDict["color"] as string;
+    var fontSize = (int)configDict["fontSize"];
+}
+{{< /code-block >}}
+
+### Flag evaluation details
+
+When you need more than just the flag value, use the detail methods. These methods return both the evaluated value and metadata explaining the evaluation:
+
+* `GetBooleanDetails(key, defaultValue)` -> `FlagDetails<bool>`
+* `GetStringDetails(key, defaultValue)` -> `FlagDetails<string>`
+* `GetIntegerDetails(key, defaultValue)` -> `FlagDetails<int>`
+* `GetDoubleDetails(key, defaultValue)` -> `FlagDetails<double>`
+* `GetDetails<T>(key, defaultValue)` -> `FlagDetails<T>`
+
+For example:
+
+{{< code-block lang="csharp" >}}
+var details = client.GetStringDetails("paywall.layout", "control");
+
+Debug.Log($"Value: {details.Value}");     // Evaluated value (for example: "A", "B", or "control")
+Debug.Log($"Variant: {details.Variant}"); // Variant name, if applicable
+Debug.Log($"Reason: {details.Reason}");   // Description of why this value was chosen (for example: "TARGETING_MATCH" or "DEFAULT")
+Debug.Log($"Error: {details.Error}");     // The error that occurred during evaluation, if any
+{{< /code-block >}}
+
+Flag details may help you debug evaluation behavior and understand why a user received a given value.
+
+## Advanced configuration
+
+The `DdFlags.Enable()` API accepts optional configuration with options listed below.
+
+{{< code-block lang="csharp" >}}
+DdFlags.Enable(new FlagsConfiguration(
+    trackExposures: true,
+    trackEvaluations: true,
+    evaluationFlushIntervalSeconds: 10.0f
+));
+{{< /code-block >}}
+
+`trackExposures`
+: When `true` (default), the SDK automatically records an _exposure event_ when a flag is evaluated. These events contain metadata about which flag was accessed, which variant was served, and under what context. They are sent to Datadog so you can later analyze feature adoption. Set to `false` to disable exposure tracking.
+
+`trackEvaluations`
+: When `true` (default), the SDK tracks flag evaluations and sends aggregated evaluation telemetry to Datadog. This enables analytics about flag usage patterns and performance. Set to `false` to disable evaluation tracking.
+
+`evaluationFlushIntervalSeconds`
+: The interval in seconds at which batched evaluation events are sent to Datadog. Accepted values are between `1` and `60`. Default is `10.0` seconds.
+
+`customFlagsEndpoint`
+: Configures a custom server URL for retrieving flag assignments.
+
+`customExposureEndpoint`
+: Configures a custom server URL for sending flags exposure data.
+
+`customEvaluationEndpoint`
+: Configures a custom server URL for sending flags evaluation telemetry.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://github.com/googlesamples/unity-jar-resolver
+[2]: https://openupm.com/packages/com.google.external-dependency-manager/
+[3]: https://github.com/DataDog/unity-package
+[4]: https://docs.unity3d.com/Manual/gradle-templates.html
+[5]: /real_user_monitoring/application_monitoring/unity/setup
diff --git a/layouts/partials/feature_flags/feature_flags_client.html b/layouts/partials/feature_flags/feature_flags_client.html
index 3d61897bc3c..d9001cb2bb9 100644
--- a/layouts/partials/feature_flags/feature_flags_client.html
+++ b/layouts/partials/feature_flags/feature_flags_client.html
@@ -65,6 +65,13 @@
                     </div>
                 </a>
             </div>
+            <div class="col">
+                <a class="card h-100" href="/feature_flags/client/unity/">
+                    <div class="card-body text-center py-2 px-1">
+                        {{ partial "img.html" (dict "root" . "src" "integrations_logos/rum-unity_large.svg" "class" "img-fluid" "alt" "Unity" "width" "400") }}
+                    </div>
+                </a>
+            </div>
         </div>
     </div>
 </div>