Riffs, built by AI
The small web tool
that should stay small.
Give an AI a single-purpose job and get a standalone URL or embed, with isolated backend code, secrets, state, and files — without starting a repository, framework, or release process.
Riffs fit small standalone tools. Visitor accounts, payments, custom domains, package-heavy apps, team development, and formal releases are the signal to use a full app platform.
"Build a poll so the team can vote on where to eat, and show the running tally."
…and it's live
A real riff, embedded right here — vote and watch the tally update.How embedding works →
Choose the small tool
A live tool, not the beginning of a product.
Use runcurve when the job needs an anonymous URL or embed, a little isolated backend code, and perhaps a secret, shared state, or a file. The work stays legible: plain frontend files and a few backend routes, live whenever they are saved.
Explore four fitting jobs →From idea to live URL.
Three steps, no release process. Drive it from your LLM over MCP, or from the studio.
Ask the AI for an app over MCP — a form, a tracker, a small tool — or open the built-in editor and write it yourself.
runcurve builds it and runs it in a secure sandbox right away. No build step, no deploy queue, nothing to provision.
Every app gets a working address on run.runcurve.com. Keep iterating by chatting with the AI or editing the code.
Everything a small tool needs. Nothing to run.
Each riff is self-contained and secure, with the pieces a small tool needs to do real work.
Instant, no setup
Riffs start in milliseconds and cost nothing while idle. No servers, no containers, no cold-start wait.
Built-in editor
Read and edit any app in the browser. You and the AI work on the same files and hand off in either direction.
Secrets and storage
Every riff keeps its own secrets, documents, and files — build a stateful tool without wiring up a backend.
Fixes its own bugs
When an app breaks, the failure goes straight back to the AI, which reads what went wrong and rewrites the code.
Safe by default
Each app is sealed off from the others and the open internet. Backend calls work only over HTTPS to public API hosts you explicitly allow, including on redirects.
Small on purpose
Riffs are for one-purpose tools. When you need accounts, payments, a team, or releases, move to a full app platform.
Build your first small tool in a sentence.
Point your AI assistant at the runcurve MCP server and ask for what you want — or open the studio and build it by hand. Either way, it's live the moment it's written.
Connect your assistantA tested Claude Code setup path, OAuth handoff, and first-riff prompt.