revturbine-go-live-hosted-cutover

Go live — hosted cutover

Local mode proved the integration; hosted mode makes it a product. After this, plans, gates, and nudges change from the dashboard without a redeploy — the reason RevTurbine exists.

This step changes live state and can involve billing. Do not run it autonomously. Prepare and validate everything, then get the builder's explicit go-ahead before the cutover.

1. Connect the tenant

The builder needs a RevTurbine account and a tenant. From the CLI:

npx revturbine login      # browser device-flow; or `signup` to create an account
npx revturbine status     # confirms the resolved tenant + that the token works

The tenant is bound to the token, not to a URL. status must show the tenant you intend to act on before going further.

2. Upload the Playbook and launch it

Ship the local Playbook to the tenant as a reviewable Release, don't hand-recreate it:

npx revturbine validate ./revturbine.playbook.json   # offline, full schema
npx revturbine launch ./revturbine.playbook.json     # upload → submit → approve → deploy

launch moves the config through the Draft → Release lifecycle. This is the irreversible, human-confirmed lever — a rollback is a new forward version, and money may already have moved once real pricing is attached. Confirm before running it.

3. Swap the provider from local to hosted

The component code does not change — only the provider options. Replace localRuntime with the hosted connection:

  const options = useMemo(() => ({
-   localRuntime: { exportedConfig: playbook },
+   tenantId: process.env.REVTURBINE_TENANT_ID!,
+   apiKey: process.env.REVTURBINE_API_KEY!,
+   runtimeMode: 'revturbine_server',
    user: { id: currentUser.id, context: { plan_handle: currentUser.planHandle } },
    uiPathResolvers: { navigate_to_plans: () => { window.location.href = '/pricing'; } },
  }), []);

Put REVTURBINE_TENANT_ID and REVTURBINE_API_KEY in the app's environment, not in source. The public key is safe in the client; the server secret is not — keep server-side re-checks (rtServer.can) using server credentials.

4. Confirm the fallback still holds

Hosted mode adds a network dependency. Verify the additive-only guarantee survives it: if the control plane is unreachable or a placement returns nothing, the app still renders its baseline UI. RevTurbine being down must never take the product down.

After cutover

Config is now live and editable from the dashboard. Point the builder there for the payoff local mode couldn't give: funnels and conversion analytics, experiments, segment targeting, and changing any gate or paywall without shipping code. The integration is complete; iteration moves to the control plane.