Monetization overview

You can publish any Flow publicly and charge for each run — giving you a friction-free way to monetize your audience.

You setHow it worksYou earn
Set your Flow as public and choose a price for each run.User pays at checkout before the run starts.Full amount is either credited to your organization balance or paid out via your payout account.

1. Public vs. private Flows

Private FlowPublic Flow
VisibilityOnly you/orgAnyone with the link
User paysNoYes (if you set a price)
CostsYour balance covers every stepYour balance covers every step
PayoutsN/AWallet or Payout Account

2. Pricing

ScenarioFee formula
Paid Public Flowrun price × 0.13 + $0.30 + step fees
Free Public FlowFlat $0.28 + step fees
Private Flow$0.01 per run + step fees

Example

Let’s say you have a Paid Public Flow that trains a model for 30 minutes and generates 80 inferences, then zips all the images. You set a run price of $10.

  • Platform fee: $0.30 + 13% of $10 = $1.60
  • Training cost: 30 min × $0.06 = $1.80
  • Inference cost: 80 inferences × $0.02 = $1.60
  • Zipper cost: 80 MB × $0.0035 + $0.01 = $0.29
  • Total costs: $1.60 + $1.80 + $1.60 + $0.29 = $5.29

You receive the full $10 in your payout account or organization balance. Subtracting the fees deducted in real time, your effective earnings are $10 - $5.29 = $4.71.

See the billing documentation for the full pricing table and more examples.

3. Getting paid

There are two ways to receive payouts for your public Flow runs:

Wallet

Revenue goes straight into your organization balance. Set “In-app wallet” as the payout method on your Flow.

Payout account

  1. In Dashboard → Settings → Payouts, click “Connect payout account”.
  2. Complete Stripe’s onboarding (name, bank details, address).
  3. Set payout method to “Payout account” on any Flow you’d like to be paid out directly.
  4. Funds appear in your Stripe dashboard.

If no payout account exists or if it’s invalid, lensless automatically falls back to the Wallet method.

Refunds

Users receive a refund if an error occurs during the Flow run or if they successfully dispute the charge through our payment processor. In either case, you’ll still be charged for the steps that were executed.

To avoid losing money on refunds, always test your public Flows before publishing. Run at least one full end-to-end test with realistic input to make sure everything works and you have a precise idea of the cost. Be very clear to your audience about the expected output and Flow run duration.

4. Supported countries

lensless can be used worldwide, but monetization (setting a price for public Flows) is currently available only in Brazil. We expect to re-enable support for other countries in the coming months. If you’re not based in Brazil, you can use everything except setting a price on public Flows.

Last updated on March 19, 2026