> ## 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.

# Traffical documentation

> Parameter-first experimentation, feature flags, and adaptive optimization with sub-millisecond local resolution.

Traffical is an experimentation, feature management, and optimization platform built around a single primitive: the **parameter**. Define typed parameters with defaults; run A/B tests, progressive rollouts, and adaptive bandits as policies on top of them; resolve values locally in your SDK with sub-millisecond latency.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Install the SDK, resolve your first parameter, track an event — under five minutes.
  </Card>

  <Card title="Core concepts" icon="book" href="/concepts/parameters">
    Parameters, layers, policies, projects, assignments, warehouse-native.
  </Card>

  <Card title="SDKs" icon="code" href="/sdks/overview">
    Server (Node, Python, PHP) and client (browser, React, Svelte, iOS, React Native).
  </Card>

  <Card title="Canonical experiments" icon="book-open" href="/guides/canonical-experiments">
    Patterns by surface — backend, web, mobile, SSR, batch, contextual.
  </Card>

  <Card title="Changes & governance" icon="waypoints" href="/concepts/changes">
    Run initiatives through a governed, measured lifecycle — risk classes, approvals, audit trail.
  </Card>

  <Card title="Statistics" icon="square-root-variable" href="/statistics/overview">
    Significance, sequential testing, CUPED, measurement progress, impact methodology.
  </Card>
</CardGroup>

## Why Traffical?

Most experimentation tools start from the feature flag — a boolean. Traffical starts from the **parameter**: a typed value with a default. A/B tests, rollouts, feature flags, and adaptive optimization are all policies that override parameter values for selected users.

This means a single system handles colour tests, price experiments, algorithm changes, gradual rollouts, and personalized content — through the same SDK, the same dashboard, the same primitives.

<Card title="Read why" icon="lightbulb" href="/why-traffical">
  Typed parameters, local resolution, warehouse-native measurement, and governance built in.
</Card>