Your documents. Your server. Your rules.
Deploy TheTerms on your own infrastructure in minutes. Full feature parity with the cloud version, zero artificial limits, and complete data sovereignty.
Deploy in three commands
# Clone and configure
git clone https://github.com/ashwineaso/theterms.git
cd theterms && cp apps/web/.env.example .env
# Edit .env with your secrets, then start everything
docker compose up -d --build
# Migrations run automatically — the app is ready at :3000That's it. Database migrations run automatically on container startup. Full guide →
Cloud vs Self-Hosted
| Aspect | Cloud | Self-Hosted |
|---|---|---|
| Setup time | Instant (sign up) | 10 minutes (Docker) |
| Data location | Our infrastructure | Your infrastructure |
| Updates | Automatic | Manual (git pull + docker compose up) |
| Maintenance | Fully managed | You manage backups, HTTPS, monitoring |
| Compliance | Standard | Full control over data residency |
| Cost | Per-user pricing | Free (AGPL) or enterprise license |
| Support | Included in plan | Community or enterprise license |
| Feature set | Full | Full (no artificial limits) |
Architecture
Browser
↓
Reverse Proxy (HTTPS)
↓
TheTerms App (:3000)
↓
PostgreSQL
↓
Redis
All services run in a single Docker Compose stack.
Frequently asked questions
What are the system requirements?
A server with at least 1 CPU core, 2 GB RAM, and 10 GB disk space. Docker and Docker Compose must be installed. Any Linux distribution, macOS, or Windows with WSL2 works.
How do I set up HTTPS?
Place a reverse proxy (nginx, Caddy, or Traefik) in front of TheTerms. Caddy provides automatic HTTPS with Let's Encrypt. We provide example configurations in the documentation.
How do I back up my data?
Use pg_dump to back up the PostgreSQL database. The Docker volume for postgres_data contains all persistent data. We recommend automated daily backups with a retention policy.
Can I migrate from cloud to self-hosted?
Yes. We provide data export tools for cloud users, and import tooling for self-hosted instances. Your documents, signing records, and team configuration transfer cleanly.
Do I need to comply with AGPL-3.0?
If you run TheTerms as-is for your organisation, you only need to provide the source code to users who access it over the network. If you modify the code and deploy it as a service, you must make your modifications available under AGPL-3.0.