Small AI apps are cheap to build and expensive to run.
AI collapsed the cost of building a narrow tool. The cost of turning that tool into a product — model access, accounts, payments, metering, payouts, distribution — did not move. PortModels shares that cost across a marketplace so a useful app no longer has to become a company to exist.
The gallery, the accounts, and the billing described here are running today.
At a glance
- What it is
- A gallery of small AI apps, each built for one job
- Who pays
- Users, per run, from a single balance
- Who builds
- Independent developers, publishing into that demand
- What we operate
- Model gateway, identity, metering, payments, payouts
- Where we earn
- Usage margin, data-layer subscriptions, the transaction layer
The build got cheap. The business around it didn't.
A developer with a working AI tool still has to sign model contracts, run accounts, integrate a payment processor, meter usage, handle tax and refunds, and find users — before the first dollar. Most narrow tools are not worth that overhead on their own, so they never ship. That excluded class is the market.
Shipping a small AI app alone
- Provider contracts and prepaid model credits
- Accounts, sessions, password resets, support
- A payment processor, invoices, refunds, tax
- Usage metering and abuse limits, built from scratch
- Distribution from zero — every user acquired alone
- A monthly subscription the user won't take for one small tool
Shipping it on PortModels
- One integration for models, identity, billing, and metering
- Users arrive with an account and a balance already funded
- Priced per run — nothing to justify monthly
- Published into a gallery people are already browsing
- App storage and data handled by the platform
- Revenue calculated per call and visible in a dashboard
Two sides, one balance in the middle
Demand and supply share the same account system, so neither side has to be rebuilt per app. That shared middle is the product.
-
1
Users top up once
One card payment funds one balance, and that balance spends across every app in the gallery — no sign-up, no subscription, no card details handed to a stranger's side project.
-
2
Developers publish into demand
One integration gets models, sign-in, billing, and metering. The listing goes through review and then sits in front of users who already have credit to spend.
-
3
PortModels runs the middle
Every call is metered, priced against provider cost and the developer's markup, drawn from the user's balance, and settled to the developer as earnings.
Three lines, all tied to real usage
Nothing here depends on a flat tier someone has to guess at. Each line grows with what the marketplace actually does.
Usage margin
Every model call is metered. Provider cost and the developer's markup are computed per call, and the platform participates in that spread. Revenue scales with runs, not with seats.
App data layer
Apps that need to store user data subscribe to storage packages on the platform. Recurring revenue that tracks the number of live apps rather than the price of inference.
Transaction layer
Balances are topped up through PortModels and paid out to developers through PortModels. The money for the whole marketplace moves across one ledger we operate.
Three things changed at once
Building stopped being the bottleneck
A working narrow tool is now a weekend. Operating and distributing it is what's left, and that is exactly the part that benefits from being shared.
Per-use pricing became viable
As model prices fall, a run costs cents. A subscription is no longer the only way to cover the fixed cost of serving one user occasionally.
Subscription fatigue is real
People will not add a twelfth monthly plan for a tool they use twice a month. They will spend from a balance they already have.
What is already built
The platform is live rather than planned: the pieces below are running in production, not on a roadmap.
Running today
- Public app gallery with a submission and review flow
- One account with a shared credit balance across apps
- Card top-ups through Stripe Checkout
- Connect with PortModels — OAuth sign-in for third-party apps
- Metered model API with per-call pricing
- Storage subscriptions for apps that keep user data
- Developer earnings and payouts
Where new capital goes
- Supply — getting more developers publishing, across more categories
- Catalog breadth — more models and modalities behind the same balance
- Reliability and trust — review, abuse handling, and the payout pipeline at volume
Happy to walk through metrics, unit economics, and the roadmap in detail on a call.
Invest in PortModels
Send a short note and we'll follow up with the detail you need.