Flow-aware feature flags for modern Next.js teams.
Map routes once. Keep flags, experiments, edge publishing, and Clara observations on the same operating frame so the team can see what changed, where it changed, and what it touched next.
[01] Map
Map routes once and keep the operating model in your repo.
npx @trueclara/next init opens the setup path so you can discover routes, define sections, and save the model next to the app it describes.
{
"app": "demo-workspace",
"sections": [
{
"name": "Acquisition",
"routes": ["/", "/pricing", "/login"],
"flags": ["hero_variant", "signup_prompt"]
}
],
"experiments": [
{
"name": "hero-copy-test",
"route": "/",
"flag": "hero_variant"
}
]
}[02] Publish
Publish the same route-aware model through one workflow.
Draft changes, validate the graph, and publish to the edge from one place so rollout logic stays attached to the routes it affects.
npm install @trueclara/next adds the provider and starts the route-discovery path.npm install @trueclara/next
trueclara scan
trueclara publish[03] Observe
Review the change, then let Clara explain what moved.
Diffs, versions, and observations stay together. Approve the change, publish it, and read the route-level impact in the same surface.
Who this is for
Product, growth, and platform teams shipping real route changes.
Product teams
Route structure gets harder to reason about as flags, experiments, and drafts stack up. TrueClara keeps the graph inspectable while the product changes.
Growth teams
Homepage, pricing, and signup flows become easier to change when experiments stay attached to the paths users actually move through.
Platform teams
Publishing, version history, and edge rollout belong in the same system as the flags and routes they affect.
Start with one route
Start with one route graph.
Open the live demo, inspect how flags and experiments sit inside the route model, then move into a real workspace when you want to wire your own app.