Security
Self-host T-Pot (CrowdSec) on a VPS
A honeypot platform for threat intel.
Deploy honeypots that capture attack data and feed threat intelligence and blocklists.
Why self-host T-Pot (CrowdSec)?
A honeypot gives you visibility into attacks against your infrastructure and can power proactive blocking.
How to install T-Pot (CrowdSec)
- 1
Provision a VPS
Choose a plan with room for your data as well as the app.
- 2
Install the stack
Install Docker multi-honeypot stack.
- 3
Deploy the application
Follow the project’s official install guide for your distribution.
- 4
Enable HTTPS
Serve it on your own domain behind a reverse proxy with a certificate.
- 5
Back it up
Schedule a database dump plus a copy of any uploaded files to an off-box location.
Practical tips
- Give T-Pot (CrowdSec) its own database user with rights only on its own schema.
- Reverse-proxy T-Pot (CrowdSec) and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep T-Pot (CrowdSec) patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does T-Pot (CrowdSec) need?
- Plan on 8 GB for typical use; add headroom if you expect many concurrent users.
- What stack does T-Pot (CrowdSec) run on?
- Docker multi-honeypot stack.
- Can I run other things on the same VPS?
- Yes — size the plan so T-Pot (CrowdSec) plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include CrowdSec, Cowrie, Dionaea — browse all app guides.