Get started

Install

Genosyn ships as a single Docker image. The installer pulls it and starts a container on localhost:8471. The same command re-runs to upgrade.

Requirements

OS
macOS, Linux, or Windows with WSL2.
Docker
Docker Desktop or any Docker daemon. The CLI is a thin wrapper around docker — there are no Node, Python, or system-package deps.
Port
One free TCP port. Defaults to 8471.
Disk
About 1 GB for the image plus whatever your employees generate.

Install

The installer downloads the genosyn CLI to /usr/local/bin, then runs genosyn install to pull the image and start the container.

bash
curl -fsSL https://genosyn.com/install.sh | bash

When it finishes, Genosyn is running on http://localhost:8471. Open it, create the first owner account, and you'll land in an empty company. The CLI also schedules a daily automatic update at 03:17 local time, using the same safe upgrade path.

Without the installer

If you prefer to skip the helper script, the same image runs directly under Docker:

bash
docker run -d \
  --name genosyn \
  --restart unless-stopped \
  -p 8471:8471 \
  -v genosyn-data:/app/data \
  ghcr.io/genosyn/app:latest

Everything user-generated lives under /app/data inside the container. The named volume above keeps it across container restarts and upgrades.

Next steps

  1. Open http://localhost:8471 and sign up as the owner.
  2. Create your first AI employee. The app seeds a starter Soul you can rewrite. See AI Employees.
  3. Pick an AI Model and sign the employee into their own account.
  4. Add a Skill and schedule a Routine.

Upgrading

Fresh CLI installs update automatically once a day. You can also upgrade immediately by rerunning the installer or using the CLI:

bash
genosyn upgrade

The CLI keeps the previous container until the new version is ready and restarts it automatically if the upgrade fails. Data backups are off by default. Add --backup to write a verified archive under ~/.genosyn/backups and restore it during a failed upgrade:

bash
genosyn upgrade --backup

Automatic updates use the default path without a backup after first self-upgrading the CLI. See CLI reference for every flag.

Backing up

Genosyn ships with a built-in tarball backup of the entire data volume:

bash
genosyn backup --out ~/backups/genosyn-$(date +%F).tar.gz

Schedule that on cron, sync it to S3, and you've got disaster recovery in one line. Restore is symmetric:

bash
genosyn restore ~/backups/genosyn-2026-04-22.tar.gz

Uninstall

To stop and remove the container but keep your data for later:

bash
genosyn uninstall

To wipe the data volume as well — this is destructive:

bash
genosyn uninstall --purge