Steps
With qURL, run qurl payments setup with your app’s resource ID (CRID) and a price. Connect Stripe in your browser when prompted. Then share the link the command prints. Buyers use a passkey and pay through Stripe Checkout.
Install the qURL CLI
On macOS, install it with Homebrew. On Linux and Windows, download the package for your platform from the latest release; the CLI page lists each one. Nothing asks you to sign up.
brew install layervai/tap/qurl qurl --versionCheck: qurl --version prints 4.1.0 or later: qurl payments setup needs it.
Check that the app answers on 127.0.0.1
For a local app, qURL connects to it on the loopback address of this machine. Use your app’s port in place of 8501 here and below. Skip this step for a remote app.
curl --fail http://127.0.0.1:8501/Check: curl prints your page and exits without an error.
Publish your app
Use your app’s address. Copy the resource ID (CRID) from the output. If you already published the app, use its CRID. If it has an access policy, run
qurl inspecton the CRID and add --version to the setup command. For example, add --version 2 if the current policy version is 2. Replacing a policy can end access you already granted.qurl publish http://127.0.0.1:8501 --name "Forecast explorer"Check: For a local app, the output says Status: serving and ends with a CRID: line.
Set a one-time price
Replace PASTE_YOUR_CRID_HERE with the full CRID. This example charges $5 USD once and grants access for the life of the resource. If prompted, approve the connection in your own Stripe account and return to the CLI.
qurl payments setup PASTE_YOUR_CRID_HERE --price 5.00Check: The command prints the https://qurl.link/ payment link. Setup has made the CRID private.
Or set a monthly subscription
Use the same CRID and run this command instead to charge $9 USD per month. Each payment covers one month of access. For an annual subscription, use --interval year.
qurl payments setup PASTE_YOUR_CRID_HERE \ --price 9.00 --interval monthCheck: The command prints the https://qurl.link/ payment link. Setup has made the CRID private.
Test the payment link as a stranger
Open the payment link in a private window or a browser that has never opened it. Stop before checkout: these are live prices, so completing it charges real money.
Check: You see the app’s name and Pay for access, and not the app itself.
Check that your first buyer gets in
When your first buyer has paid, ask them to open the link again with the same passkey.
Check: They reach the app after Stripe confirms payment. A subscriber who returns with the same passkey can also select Manage subscription.
What the recipient sees
The buyer opens the resource in a browser and selects Continue to payment.
More
They use a passkey, pay in Stripe Checkout, and can open the app after Stripe confirms payment. A subscriber can return with the same passkey and select Manage subscription.
Which walkthrough fits who should get in
Pick the row that matches who should reach the app.
| Who should get in | Walkthrough |
|---|---|
| People who ask, after you approve each one | Let a client request access to your app, and approve them |
| Only the email addresses you name, with no requests | Give a contractor temporary access to your app |
| Anyone with a verified mailbox in your company domain | Let only your company’s email addresses open an internal dashboard |
| Buyers who pay through Stripe | This guide |
Troubleshooting
| If you see | Do this |
|---|---|
| Stripe asks for more information | Complete the steps Stripe shows to enable live payments. Then run the same setup command again. |
| A buyer can open the app at a different address | Paid access applies to the qURL address. Keep the app’s original address private if every buyer must pay through qURL. For a local app, remove any public tunnel or port forward that reaches it directly. |
Frequently Asked Questions
How do I charge for access to a Streamlit or Gradio app I run myself?
Publish the app with qurl publish and a public name, then run qurl payments setup with its CRID and a price. Buyers pay in Stripe Checkout, and qURL checks the payment before it opens the app. The app stays on your machine with no public address.
Can a coding agent set up paid access for me?
Yes. Paste the agent prompt above into an agent that can run commands on the machine with the app. It asks you to approve the Stripe connection and the price before it enables payments.
Can someone else use my purchase?
Sharing the same public IP address does not give someone paid access. Buyers use their own passkey and need a confirmed payment. Anyone can still open the app at its original address if that address is public.
What fees apply to paid access?
LayerV collects 3% of each payment, including subscription renewals. Publishers also pay Stripe processing fees.
How do I handle refunds and cancellations?
Manage refunds and cancellations in Stripe. Before you disconnect Stripe, cancel active subscriptions or arrange refunds there. A LayerV account freeze blocks access while subscriptions continue.
Set a price for your app
Replace PASTE_YOUR_CRID_HERE with your app’s resource ID to set a $5 one-time price.