RevTurbine · For builders

We built monetization.
You ship it.

One SDK for plans, entitlements, usage limits, AI credits, and upgrade prompts. RevTurbine decides what each user can do and see, in real time. Your coding agent sets it up with our skills, and pricing changes never touch your code. Works with your existing Stripe billing.

Decides locally in milliseconds
Local mode free, no account needed
Connected mode free through your first $20K in new MRR

$npx revturbine create

TypeScript · React · Node · Python · Rust

Read the docs →

app/Export.tsx

// Gated feature example
const { can, limited } = useCan("generate_video")

// Renders when entitled; upgrade placement on denial
<Gate id="generate_gate" can="generate_video">
  <GenerateButton />
</Gate>

{/* RevTurbine decides what fills the slot */}
<Slot id="dashboard_banner" />

Use cases

What you can build with a line or two of code.

The rules behind it live in your Playbook, one config file for all your monetization logic. Your agent configures it using our skills, RevTurbine validates every change, and versioned releases go live without a redeploy.

Upgrade promptssee docs

// RevTurbine picks what each user sees
<Slot id="dashboard_banner" />

Feature gatessee docs

<Gate can="batch_export">
  <ExportButton />
</Gate>

Entitlement checkssee docs

await rt.can("batch_export")

AI creditssee docs

rt.update({ usage:
  { ai_credits_used: 42 } })

Usage limitssee docs

const { can, limited } =
  useCan("recording_minutes")

Free & reverse trialssee docs

await rt.getTrialStatus()

Seat limitssee docs

await rt.can("add_seat")

Server enforcementsee docs

// same API on your server
await rt.can("spend_credits")

One command

From zero to first gate in minutes.

npx revturbine create installs the SDK, CLI, Playbook, and Agent Skills. Your agent wires the rest.

terminal

$ npx revturbine create

[revturbine] ✓ Created a new project (package.json)
[revturbine] ✓ Detected npm
[revturbine] ✓ Installed the RevTurbine SDK and pinned the CLI exactly
[revturbine] ✓ Added a starter playbook (revturbine.playbook.json — local mode, no account needed)
[revturbine] ✓ Installed the RevTurbine Agent Skills

RevTurbine is set up.
  Run the skill:  /revturbine-start-here
  Docs: revturbine.com/docs

Playbook → app wiring → billing → validate → launch

Developer surfaces

One engine. Four developer surfaces.

Everything talks to the same Playbook. Built for developers and their coding agents.

01 · SDKs

SDKs for TypeScript, Python, and Rust

One API for plans, entitlements, trials, credits, and usage limits, in the browser and on the server.

// the same call in the browser and on your Node server
const result = await rt.can("batch_export")

Typed end to end
Decides locally, in milliseconds
Our availability never affects your product
Same results in every language

02 · React

React components & hooks

Monetization-aware UI that sits inside your existing design system. Headless by default.

const { can, limited } = useCan("team_members")

<Slot id="team_page_banner" />

<Gate> and <Slot> components
useCan and usePlacement hooks
Headless when you want control
Works with your component library

03 · CLI

CLI

Your Playbook is a portable config file. Pull it, edit it, and ship it through a reviewable draft → release lifecycle.

# 1. pull the live playbook as your starting point
revturbine download --live --save ./config.json
# 2. edit it — by hand or with your agent (see skills)
# 3. validate locally before uploading
revturbine validate ./config.json
# 4. stage it as the draft
revturbine upload ./config.json
# 5. take it live
revturbine launch --draft

Config as code
Reviewable, rollback-able releases
Offline schema validation, always
diff · show · history · evaluate

04 · Agent Skills

Agent Skills

Installable skills that give your coding agent RevTurbine's context, workflows, and guardrails. Bring your own agent.

> Add AI credits to this product.
> Make batch exports a Pro feature.
> Migrate hard-coded plan checks to RevTurbine.

Bring your own agent
Job-level skills, not micro-ops
Config and code updated together
The agent drafts, you launch

Architecture

Fast in the client. Authoritative on the server.

Your application

<Gate> · <Slot> · rt.can() · rt.update()

RevTurbine SDK: local decision engine

decides in ms · no network round trip

one SDK, client and server

Playbook, targeting, scores
pushed and cached

telemetry and interactions
impressions · converts · usage

RevTurbine control plane

your Playbook: plans · entitlements · trials · targeting · placements · experiments · caps · analytics

subscriptions and billing events

Stripe

prices and billing stay where they are

decisions in the app, instantlyserver confirms billing-critical callsconfig lives outside product codechanges reviewed and deployed safely

Starter

Start from a working SaaS app.

Clone a Next.js reference app with auth, Stripe billing, AI credits, usage limits, feature gates, and upgrade prompts already connected to RevTurbine.

Coming soon

Run one command. Start building.

Add your first gate, limit, or upgrade prompt without rebuilding your monetization stack. Start free: no credit card, and free through your first $20K a month in new revenue.