Publish your pipeline as an app. No installs, no infrastructure, no payment integration to build — your customers pay, and we handle hosting, billing and scale.
01 · The format
A pipeline definition in JSON, and one or more JavaScript files. That's the app. There is no backend server to deploy, no frontend web server to stand up, no container to build, no orchestration to manage.
And because nothing is running when nobody's using it, an idle app costs virtually nothing to host. Your token budget isn't quietly draining while you sleep.
.pipe definition and your .js. No repo scaffolding, no build step.Publish on a conventional app hosting platform and you're deploying multiple services: a container image, web server, backend server, database, load balancer, … You pay for a portion of that capacity whether or not a single customer shows up that month. Scale up and the bill grows before the revenue does; scale down and you eat cold starts.
They host a running service. We run a file when someone calls it.
02 · Revenue sharing
Every other marketplace charges you for shelf space. The big consumer app stores take up to 30%. Most enterprise marketplaces take 15–25% — for a listing, and the privilege of being found.
You keep 90% of every dollar your app earns. No listing fee. No revenue-share tier that shrinks as you grow. No cut for distribution.
Your app revenue
You set your own price for your customers. They pay through RocketRide. We take 10%, cover the Stripe transaction fees and other app hosting costs out of our side, and pay you the rest. You never integrate a payment processor, never chase a failed card, never build invoicing.
Your compute rebate
Apps that drive high token consumption on RocketRide Cloud earn a share in the RocketRide revenue from that consumption. This is the part that makes our business model different from every other marketplace; we're not only taking less, we're paying you for the consumption your app generates.
Straight, because you should be able to model this before you build.
Publishing requires a RocketRide Cloud subscription at Builder tier or above, and your app consumes compute like any other pipeline. Usage is prepaid: subscriptions bill for the coming cycle, and metered usage draws down a credit balance on your account. If that balance reaches zero without auto-reload enabled, your app stops serving. Nothing is billed in arrears.
03 · The honest comparison
You're a developer. You could rent a box, containerize the pipeline, wire up Stripe, handle webhooks and dunning, add monitoring, and figure out GPU capacity the first time someone posts about you. None of it is beyond you.
But none of it is your product either. Every hour spent on billing edge cases is an hour not spent on the thing customers are actually paying for — and infrastructure work never finishes, it just becomes maintenance you own forever.
The trade is straightforward: 10% of revenue for all of it, and you go back to building.
04 · Real App Examples
Built by us and the RocketRide community, these will be running on the Marketplace when we launch in August — each one a different pattern for what an app-less app can be.
Judging a hackathon on real technology adoption is slow, manual and inconsistent. Judge Hack reviews every contestant’s GitHub repo, evaluates how effectively a given product or technology was actually used, explains where and how, visualizes it, and scores against criteria the judge defines. Setting up those criteria is built into the app, so a judge is running in minutes.
New-hire onboarding connected to HR and IT systems, role-relevant tools and data sources. The new hire gets a clear checklist and guidance; the hiring manager and HR get a dashboard and progress updates. It improves itself after every run, so the flow never goes stale.
Marketplace launching soon
Already have a pipeline running? Publish it, set your price, and we handle the rest.
Have the idea but not the code? Start on the open-source runtime — free, MIT, on your laptop today.
