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

How to self-host the full Vicoa stack with Docker with Vicoa

Run the Vicoa backend, web app, and database on your own infrastructure using Docker.

Who it is forA team or individual that wants to keep sessions and account data on its own servers instead of a hosted service.

The problemTeams that need control over where agent sessions and messages are stored have no hosted-only option they can accept.

The outcomeThe full stack runs on your own machine or server, reachable through the Vicoa web app and clients you configure.

What you need first

  • At least one supported agent CLI installed and signed in on the machine that runs agents
  • A Vicoa account for the desktop and mobile apps
  • Node.js 18+ for the npm CLI, or pip on Intel Macs or old glibc systems

Steps

  1. Clone the repository with git clone https://github.com/vicoa-ai/vicoa and change into the vicoa folder. (inferred, check the README)
  2. Run cp .env.example .env and set passwords and public URLs in the .env file.
  3. Run ./backend/scripts/generate-jwt-keys.sh selfhost/keys to create the signing keys.
  4. Run docker compose -f docker-compose.selfhost.yml up -d to start the stack.
  5. Follow SELF_HOSTING.md for the remaining configuration and checks.

Prompt for your agent

Using the vicoa-ai/vicoa repo, self-host the Vicoa stack on <server-address> by following SELF_HOSTING.md. Confirm that the Docker containers started with `docker compose -f docker-compose.selfhost.yml ps` and that the web app loads at the URL you set. Report the running services and the URL.

Caveat. The README gives only the core Docker commands and points to SELF_HOSTING.md for the full setup, so plan for that file's steps.

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