The business layer for Livepeer apps

Identity, metering, and payment signing — so you ship product, not infrastructure.

The gap

Livepeer runs the network. Metering, billing, and payments are still on you.

Usage tracking, subscriptions, and payment signing eat months before your first customer. Most teams rebuild the same stack — or never ship.

The promise

pymthouse handles all of it — hosted, open, and Livepeer-native.

Get a network key in minutes as an Explorer, or ship a full product as a Builder. Same platform. Clear path to value in your first session.

What you get

Three capabilities. One platform.

Everything between your users and Livepeer compute — without bolting on three vendors.

Identity

OIDC for humans and machines. Scoped tokens, white-label login, and standards that plug into what you already ship.

  • OIDC + token exchange
  • Web & M2M clients
  • Branded sign-in

Billing

Usage-metered plans with a Starter allowance. See spend and requests without building a billing stack.

  • Per-request metering
  • Plans & allowances
  • Owner dashboards

Payments

Remote signing for Livepeer tickets — authenticate, sign, and meter through one managed path.

  • Managed signer DMZ
  • Per-user cost tracking
  • Live usage monitoring

How you start

Pick the path that matches today

Explore the network — your network, upgrade to Builder when you're ready to launch your own platform!

From signup to your first paid request

Three steps to the moment the product proves itself.

01

Choose your path

Explorer: get a personal network key on the shared app. Builder: create your own product with plans and users.

02

Connect and sign

Use your API key or SDK token against the remote signer. First successful sign is the ah-ha moment.

03

Grow with metering

Watch usage, set plans, and add billing when customers arrive — without rewriting your payment path.

For builders shipping product

From first key to paying customers

Create your own app, mint keys, set plans, and grow users on Livepeer — without standing up OAuth, Stripe plumbing, or a payment signer.

  • Own your app, plans, and user namespace
  • Mint signing keys in minutes
  • Upgrade billing when you are ready
sign.py

# One key. Real network access.

client.sign(

token=os.environ["PYMTHOUSE_KEY"],

pipeline="text-to-video",

)

For platforms & multi-tenant apps

One backend. Many products.

Register developer apps under a single pymthouse instance. Each gets isolated clients, plans, and optional white-label login — managed from one place.

  • Isolated OIDC clients per app
  • Independent billing per tenant
  • White-label login when you need it
Usage this month↑ 24%

Requests

128,430

Spend

$1,284

For Livepeer-native teams

Payments that match the network

Wire your app to a remote signer endpoint. pymthouse authenticates the caller, signs Livepeer payments, and meters usage — so your product stays focused on video, not wallets.

  • One endpoint replaces a custom signer stack
  • Per-user, per-app cost visibility
  • Built for Livepeer payment tickets
Your App
ph
pymthouse
Livepeer

On the network

Trusted on the network

Products already shipping on pymthouse

View all →

First session

Make your first paid request today

Free during beta. Choose Explorer or Builder, create a wallet, and mint a key — then watch your first request go through.

Start Building Now