evolveAB docs

evolveAB runs A/B tests and bandits inside your Next.js app. Variants are picked on your server, so pages don't flicker. Raw visitor data stays in your own Postgres; Evolve Cloud gets aggregate counts, does the statistics, and writes AI challengers you approve.

These docs cover next-evolve 0.9.0. New accounts start with a 30-day free trial, no card needed: start one.

Quickstart for developersInstall, run init, connect Postgres, wrap one component and start a test. About 30 minutes.Guide for marketersNo code: read results, approve AI proposals, set guardrails and decide when autopilot runs.

Guides

ConceptsRegions, variants, experiments, the bundle, static and dynamic mode, cookies and bots.Goals & attributionDefine goals, fire events, and how conversions are attributed to variants.Wrap components`npx next-evolve wrap`: turn existing components into optimizable regions, with a diff first and rollback on a failed build.HostingVercel, Docker, plain Node, Netlify and Cloudflare: what's verified and the cache rules that keep variants apart.ProductionEnv vars, app URL, hosts (Vercel, Docker, Node), pull mode, CDNs and firewalls.Stripe recipeCount paid subscriptions, and their revenue, as a goal.

Reference

Configurationevolve.config.ts, environment variables, cookies, CDN routing, database and retention.APIComponents, functions, the CLI and the HTTP routes next-evolve adds to your app.

Help

TroubleshootingSetup errors, nothing tested, nothing measured, results and connection tests.What leaves your serverEvery call the SDK makes and accepts, and what is in it. Visitor data stays in your Postgres.Without an accountWhat the SDK does with no key, no bundle, an outage or a database that's down.