Uninstall

The installer ships a matching uninstaller. From the install directory (default ~/.deepsql/self-host):

./scripts/uninstall.sh

Or fetch and pipe:

curl -fsSL https://install.deepsql.ai/uninstall.sh | bash

Reinstall: just run uninstall, then install

As of v1.0.1, this works correctly with no extra flags:

curl -fsSL https://install.deepsql.ai/uninstall.sh | bash
curl -fsSL https://install.deepsql.ai/install.sh | bash

Why this is worth calling out

Before v1.0.1, uninstall preserved Postgres + Valkey volumes by default. Reinstalling on top of those volumes failed with confusing credential errors — the new install generated a fresh ENCRYPTION_KEY but the volume still held data encrypted with the old key, so the backend couldn’t decrypt stored credentials and login failed.

v1.0.1 flipped the default to purge volumes. A clean uninstall + install now produces a clean install. If you’re on an older self-host install and hit the bug, the workaround is:

docker volume rm \
  deepsql-selfhost_dba-agent-postgres \
  deepsql-selfhost_dba-agent-valkey \
  deepsql-selfhost_dba-agent-logs 2>/dev/null
curl -fsSL https://install.deepsql.ai/install.sh | bash

What it removes

• All DeepSQL containers (docker compose down)
• All DeepSQL volumes — including the internal Postgres data volume
• The ~/.deepsql/ directory (the extracted bundle)

What it does NOT remove

• Docker itself (you installed it, you keep it)
• The @deepsql/mcp global npm package
• MCP config entries in Claude Code / Codex / Cursor — remove those manually if you want a clean slate
• Any cloud resources (EC2, IAM, etc.) created via CloudFormation — delete that stack separately

This destroys data

Uninstall wipes the internal Postgres volume. Back up anything you care about first.

Preserving data across reinstalls (advanced)

If you’re iterating on the install script and want to keep the existing Postgres + Valkey data across a reinstall of the same version, pass --keep-data:

./scripts/uninstall.sh --keep-data

Don't mix this with a version change

Each install auto-generates a fresh ENCRYPTION_KEY and DB_PASSWORD. If you --keep-data and then reinstall, the new install will get new secrets but the volume will still hold data encrypted with the old key — the backend will fail to decrypt stored credentials and login will fail.

Only use --keep-data when reinstalling the same version with the same .env preserved. For any version change or fresh install, use the default (which purges volumes).

Tearing down the CloudFormation stack

If you deployed via CloudFormation, the cleanest way to remove everything is:

aws cloudformation delete-stack --stack-name deepsql-selfhost --region <region>

This removes the EC2 instance, IAM role, support user, Secrets Manager secret, and security group in one shot.