Docs · Deploy button
Deploy to Doable — one-click button for your README
A visitor clicks the button, lands on Doable with your repo URL pre-filled, and gets a live preview in 30 seconds. No signup, no credit card, no Heroku-OAuth dance.
Preview
About to publish a demo repo? Drop this in the README. Every star on your repo is a potential click.
1. Copy the Markdown
Replace OWNER/REPO with your GitHub path (e.g. vercel/next.js).
[](https://doable.do/r/OWNER/REPO)
2. Or embed raw HTML
For blog posts, landing pages, anywhere that takes HTML:
<a href="https://doable.do/r/OWNER/REPO"> <img src="https://doable.do/deploy-button.svg" alt="Deploy to Doable" /> </a>
3. Done
Visitors who click end up at doable.do/try with your repo URL pre-filled. They see the constraints (8-hour lifetime, read-only until claimed), hit Deploy, and get a live <memorable-slug>.doable.do URL in about 30 seconds. No signup required.
How the short URL works
The /r/OWNER/REPO path is a short-URL that redirects into /try?url=https://github.com/OWNER/REPO. That's the same /try page you can send anyone to manually — we just save you from URL-encoding the full GitHub URL every time.
The button never skips the preview-confirmation screen. Visitors always see the constraints (public-only, 8h, read-only) and click Deploy themselves — no silent auto-deploy that could feel like a scam.
Good practice
- ›Put the button near the top of your README. Below the description, above the install instructions.
- ›Make sure the repo actually builds cleanly on a fresh machine. A failed first-deploy is a terrible first-impression. If your repo needs env vars to run, say so in the README before the button.
- ›The button works on any public GitHub repo — you don't need a Doable account to add it, and neither does the person clicking it.
FAQ
Is there a cost to me (the repo owner)?
No. Previews run on ghost accounts — they're not attached to you. If a visitor loves your repo, they can claim the preview to their own Doable account in one click. You're never billed.
What if my repo is private?
The /try flow is public-only. For private repos, visitors need to sign in and use the authenticated deploy path (GitHub App install or PAT). The button still works for signed-in visitors, but they'll be redirected to auth first.
Can I customize the button?
Not officially — keeping the badge visually consistent is what makes it recognisable across projects. If you want to ship your own styled CTA pointing at /r/OWNER/REPO, you can absolutely do that; we just don't publish a style guide.
Does this replace “Deploy to Heroku” / “Deploy to Vercel”?
They coexist fine. Most README maintainers ship multiple buttons — one per supported platform. Doable's differentiator is the no-signup path, so it's especially useful for drive-by demo repos where visitors aren't ready to create an account on another platform.
Paste a GitHub URL. Live in 30 seconds. No signup.