RevTurbine · For builders
Build monetization into your product.
Plans, entitlements, trials, credits, and usage limits. Upgrade, expansion, and retention prompts, decided per user, in real time. Start free.
TypeScript · React · Node · Python
Read the docs →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" />Developer surfaces
One engine. Four developer surfaces.
Everything talks to the same Playbook. Built for developers and their coding agents.
TypeScript SDK
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
- Additive: renders nothing if disconnected
- More languages available on request
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
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
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
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.
$ npx revturbine create [revturbine] ✓ Created a new project (package.json) [revturbine] ✓ Detected npm [revturbine] ✓ Installed the RevTurbine SDK and CLI (CLI pinned to 0.10.0) [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 → verify → launch
Use cases
The monetization moments, as code.
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")
Upgrade promptssee docs
<Slot id="dashboard_banner" />
Server enforcementsee docs
// same API on your server await rt.can("spend_credits")
Architecture
Fast in the client. Authoritative on the server.
pushed and cached
impressions · converts · usage
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.
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.
Get updates, growth tactics, benchmarks, and examples. Join the email list.