DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to self-host a private team design canvas with Docker with Doop

Run Doop's production build with Docker so your team designs on infrastructure you control.

Who it is forA team lead or ops person who needs a private shared design space and does not want to use the hosted service.

The problemTeams that want shared AI-assisted design often cannot send work to a hosted tool they do not control.

The outcomeDoop running on port 4400 with app and Postgres in containers, ready for invited collaborators.

What you need first

  • Git and bun installed (the README says Doop builds and installs with bun, and the server runs on Node)
  • Claude Code or another MCP client, for connecting an agent over OAuth
  • Docker, only if self-hosting the production build
  • An ANTHROPIC_API_KEY, only if you want the built-in Doop Agent to run

Steps

  1. Run git clone https://github.com/kgoedecke/doop && cd doop
  2. Run BETTER_AUTH_SECRET=$(openssl rand -hex 32) docker compose up -d
  3. Open http://localhost:4400 in a browser
  4. Sign up, create a canvas, and invite collaborators by email
  5. Optionally set DATABASE_URL to a real Postgres, as the README describes

Prompt for your agent

In the repo kgoedecke/doop, start the production stack with `BETTER_AUTH_SECRET=$(openssl rand -hex 32) docker compose up -d`. Confirm the app answers on http://localhost:4400 and report the HTTP status code returned for the root URL.

Caveat. The README gives no guidance on backups, TLS or upgrades, so plan those yourself before putting real client work on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page