Home

Wildbox Wiki

Self-hosted security operations platform: eleven services behind one API gateway, started with a single docker compose up.

This wiki is the orientation layer. Wildbox has a lot of documentation, spread across wildbox.io, the root of the repository, and docs/, and it is not always obvious which document answers the question you have. The wiki exists to point you at the right one and to record the things that are only visible by reading docker-compose.yml.

In this wiki

• Service map: what each of the eleven services does, what it is built with, which port it listens on, and which ones start by default
• First run: the actual sequence from clone to a working login, including the secrets you must generate before the first start
• Where the documentation lives: which file answers which question, across the repository, docs/ and the website
• FAQ: scope of the platform, requirements, the open pull requests, and what "in development" means for a service

Reference material

• wildbox.io: the documentation site
• SETUP_GUIDE.md: deployment
• TROUBLESHOOTING.md: common failures, and the longest single document in the repository
• SECURITY.md: security policy and private disclosure
• CONTRIBUTING.md and the CHANGELOG

Two things worth knowing before you start

Only the gateway is reachable from outside. Every other service publishes its port on 127.0.0.1 only, and PostgreSQL and Redis publish nothing at all. That is deliberate. If you are trying to reach a service from another machine and cannot, this is why: go through the gateway.

Vulnerabilities do not go in the issue tracker. Use the private disclosure route in SECURITY.md. This is a security platform holding credentials for your cloud accounts.