> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traffical.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Traffical is parameter-first experimentation, feature flags, and adaptive optimization in one system.

Traffical is a platform for experimentation, feature management, and adaptive optimization. It is built on a single primitive — the **typed parameter** — that unifies A/B testing, feature flags, gradual rollouts, and contextual bandits.

SDKs resolve parameters locally in sub-milliseconds. The optimizer learns from user behaviour and continuously refines allocations. Metrics are computed either from Traffical-native events or directly from your own data warehouse.

## Key capabilities

* **Parameter-first.** Typed values (string, number, boolean, JSON) with defaults and constraints. Experiments, rollouts, and flags are all policies on top of parameters.
* **Layered experimentation.** Mutual exclusivity within a layer; orthogonal bucketing across layers. Run dozens of concurrent experiments without them contaminating each other.
* **Local resolution.** SDKs fetch a config bundle and resolve in-process. Sub-millisecond, works offline, graceful degradation if Traffical is unreachable.
* **Adaptive optimization.** Thompson Sampling, Epsilon-Greedy, UCB1, per-entity bandits, and linear contextual bandits that personalize per user.
* **Warehouse-native metrics.** Define metrics as SQL against your own warehouse — Postgres, BigQuery, Snowflake, Databricks, ClickHouse — or use Traffical-native events. Or both.
* **Governed changes.** Move product initiatives through a measured lifecycle with [Changes](/concepts/changes) — stated intent, computed risk class, approval gates, and a decision record for every transition. Enabled per organization.
* **Honest statistics.** Sequential (anytime-valid) testing, [CUPED](/statistics/cuped) variance reduction, a [measurement progress](/statistics/measurement-progress) readout that estimates how much longer an experiment needs, and a deliberately conservative [program-level impact estimate](/statistics/impact-methodology).
* **Config-as-code.** Manage parameters, events, and metrics in version-controlled YAML — `push`, `pull`, and a `status` check that gates CI on drift. Type-safe event tracking via generated TypeScript types.
* **Visual editor and DevTools.** Author no-code UI experiments via a bookmarklet; inspect SDK state and override parameters live in any browser.

## Who is Traffical for?

Engineering teams who want to:

* Run experiments without adding latency to their application
* Manage configuration as code, alongside the application code that uses it
* Move beyond feature flags into typed parameters and adaptive optimization
* Compute metrics from their existing data warehouse
* Run many concurrent experiments safely

…and the PMs, marketers, and data scientists who work alongside them.

## SDKs

| Package                                         | Environment                                 |
| ----------------------------------------------- | ------------------------------------------- |
| [`@traffical/node`](/sdks/node)                 | Server-side Node.js / Bun                   |
| [`traffical`](/sdks/python)                     | Server-side Python 3.10+ (sync and asyncio) |
| [`traffical/sdk`](/sdks/php)                    | Server-side PHP 8.1+                        |
| [`@traffical/js-client`](/sdks/javascript)      | Browser, framework-free                     |
| [`@traffical/react`](/sdks/react)               | React (browser, RSC, Next.js)               |
| [`@traffical/svelte`](/sdks/svelte)             | Svelte 5 and SvelteKit                      |
| [`Traffical`](/sdks/ios)                        | iOS, macOS, tvOS, watchOS (Swift)           |
| [`@traffical/react-native`](/sdks/react-native) | iOS / Android via React Native              |
| [`@traffical/cli`](/tools/cli)                  | Config-as-code CLI                          |

Every SDK shares the same bucketing, condition evaluation, and resolution logic — the TypeScript SDKs via [`@traffical/core`](https://github.com/traffical/js-sdk), with the [PHP](/sdks/php), [Python](/sdks/python), and [Swift](/sdks/ios) SDKs mirroring it against a shared, language-agnostic conformance spec. Whichever SDK you use, the same user always resolves to the same allocation.

## Next steps

<CardGroup cols={2}>
  <Card title="Why Traffical" icon="lightbulb" href="/why-traffical">
    The parameter-first philosophy.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Up and running in under five minutes.
  </Card>

  <Card title="How it works" icon="gears" href="/how-it-works">
    Local resolution, evaluation modes, the config bundle.
  </Card>

  <Card title="Canonical experiments" icon="book-open" href="/guides/canonical-experiments">
    Patterns for backend, web, mobile, SSR, batch, and more.
  </Card>
</CardGroup>