Most people who star your repo never run it.

They read the README, mean to come back on the weekend, and never do. A badge hands them a running copy of your project in one click. No Docker on their side, no support burden on yours.

Add the badge

It points at your project's page here, where a visitor can read what the demo contains and start one. Nothing to install, and nothing for you to keep working.

try itDropLive

Markdown

[![Try with DropLive](https://droplive.io/badge/4gaboards.svg)](https://droplive.io/projects/4gaboards)

HTML

<a href="https://droplive.io/projects/4gaboards"><img src="https://droplive.io/badge/4gaboards.svg" alt="Try with DropLive"></a>

reStructuredText

.. image:: https://droplive.io/badge/4gaboards.svg
   :target: https://droplive.io/projects/4gaboards

That example is 4gaboards, a project we list today. Swap it for your own — it is the last part of your project's DropLive address. The badge only renders for a project we currently list, so if it comes out broken, that is the reason.

Not listed yet?

Tell us the repository and we will look at what it needs. You do not have to be the maintainer to ask. If your project already publishes an image or a Compose file, the recipe is often this short:

version: 1
kind: app

Recipes live in ben-ic/droplive-recipes — read any of the ones that already work before writing yours.

What we are and are not claiming

We do not touch your code.

Demos run your published image from a pinned commit. The recipe only says how to build and start it.

A listing is not an endorsement.

We test that a visitor can use it. We do not audit your code, and every page says so.

Say the word and it comes down.

No argument.