Back to Updates

From One Prompt to a Live Paid App

ibl.ai Engineering
Applicationiblai/vibe

Ask a Code Mode agent for an app that takes payments and it builds one from the default template with sign-in included, previews it on your machine, deploys it to a live web address on ibl.ai's hosting, and puts a paywall on your own Stripe account β€” with no Stripe keys pasted anywhere and nothing secret passing through the chat.

A Code Mode agent on ibl.ai can now take one prompt and produce a live, paid app: built from the default template with sign-in included, previewed on your machine, deployed to a web address, and gated by a paywall on your organization's own Stripe account β€” and on ibl.ai you own all the code and the data, including the project the agent writes.

Each piece of this shipped separately over the past six weeks. What is new is that they compose into one unbroken run, and that the result is a product rather than a demo.

One prompt to a live app with a working paywall, start to finish.

What happens between the prompt and a working app?

Four steps, in an order chosen so nothing is public before you have seen it.

Step What the agent does Already announced in
1. Build Starts from the default template, so sign-in is already wired in, and works in a folder on your computer with every tool call visible in the chat Agentic Vibe 2.0
2. Preview Opens the app locally first, so you try it before anyone else can reach it Code Mode
3. Deploy Puts it on a live web address on ibl.ai's hosting β€” no extra accounts, no deploy tooling Deploy Your AI App
4. Charge Adds a paywall on your own Stripe account, set up through Stripe's own sign-in Charge on Your Own Stripe

The live address looks like quote-spark.iblai.me, with the platform's sign-in already in place β€” so a visitor creates an account or logs in before they ever reach the paywall.

How does the agent set up payments without any Stripe keys?

It doesn't handle them at all, which is the point. There are no Stripe keys to paste and nothing secret passes through the chat.

The app opens on its own payments page, where an organization admin answers one question: free access, a one-time fee, or a monthly fee, in US dollars. A paid answer turns the button into Connect with Stripe.

That is Stripe's own sign-in. You sign in to your Stripe account β€” or a Stripe test sandbox β€” in the browser, Stripe sends you back to the app, and the connection is done. The ibl.ai platform stores only the account id.

The Payments setup link on the Account page brings you back whenever you want to change the answer. An organization that would rather paste a restricted key can still use one instead of the sign-in.

What does a paying visitor actually see?

One page. The price, a Continue to payment button, and Stripe's embedded checkout in a modal with card entry included. In test mode, Stripe's test card goes through like a real one.

The platform confirms the payment with Stripe and opens the door. A monthly fee is checked as a live subscription, a one-time payment is remembered, and recorded payers stay in even if Stripe is briefly unreachable.

The mechanics behind that β€” no commission, no webhooks, no platform key inside the app β€” are covered in Charge for Your AI App on Your Own Stripe Account.

Who holds the money?

You do. It is a Stripe Standard account linked through Connect with Stripe, not an ibl.ai-managed one, so there is no ibl.ai commission and no marketplace sitting in between.

The platform mints every Checkout Session, verifies the buyer's session, records payments and answers the app's access checks. So the app itself holds no platform key and no payment ledger of its own, and nothing depends on webhooks. A free answer makes no Stripe calls at all.

What do you actually own at the end?

Ordinary code, in a folder you chose. The paywall gate, the setup page, the pay modal and two small admin routes are a Next.js project in your workspace β€” not a hosted configuration you rent.

Open the folder in Finder, read it, change it. Or continue in the same workspace with a different agent: Code Mode runs on ibl.ai's own models or on Codex or Claude Code if you already pay for one, and the project is the same either way.

Phone Access pairs a phone by QR code, so the same session can be driven from another room β€” see Code Mode From Your Phone.

The reference material is open: the app paywall skill and the deploy skill in iblai/vibe, with the desktop app's source MIT-licensed at iblai/os.

Why does this matter more than a faster demo?

Because the usual version of this story ends with a prototype you cannot charge for.

An agent that scaffolds an app leaves you to find hosting, wire sign-in, and negotiate a payments integration. Agentic OS closes all three in the same run β€” and leaves the code, the hosting and the merchant account in your hands rather than a vendor's.

That is the same architecture as the rest of the platform: LLM-agnostic end to end, bring any model and switch anytime, with no per-seat pricing and deployment in your cloud, on-premise, in GovCloud or fully air-gapped.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

Want to ship a paid AI product on your own stack?

We can walk your team from one prompt to a live app charging on your own Stripe account. Book a 30-minute demo or talk to the ibl.ai team β€” ibl.ai is family-owned and operated from New York, NY.