A bit of context: I've spent years in enterprise security wrestling with a dozen different tools that don't talk to each other, dealing with insane licensing costs, and being completely locked into vendor ecosystems. I got tired of it. So, over the last few months, I built the platform I always wished existed: Wildbox. The idea is simple: a unified, open-source (MIT license), self-hosted Security Operations Center in a box. It integrates the functionality of multiple tools into one cohesive system:

- SIEM & Log Correlation - Threat Intelligence Aggregation (from 50+ sources) - Vulnerability Management (Guardian) - SOAR & Automated Response (Responder) - Endpoint Monitoring (via osquery) - AI-Powered Analysis (GPT-4 integration)

...and more (11 microservices total).

It's built on a modern stack (FastAPI, Next.js, OpenResty, Docker) and designed to be deployed with a single command (./setup.sh).

I just made the repository public and I'm looking for brutal, honest feedback from real security professionals. Does this solve a problem you have? What's missing? What did I get completely wrong?

No marketing fluff, no "pro" plans. It's just a tool I built out of frustration. Let me know what you think.

Thanks, Fabrizio

Helo and thank you to point out this tool I ignored before.

There is an opportunity to improve the tool then I added this feature as wanted feature in the plan as certmate dev :)

suggestion noted and added to the upcoming major release :)

hello, certmate dev here :)

Custom DNS servers are already supported via certbot-dns-rfc2136 plugin as you suggested!

certmate dev here :)

I came from a decade of certificate management in multiple work contexts and YES, all the people refer to them as SSL and not TLS, while TLS 1.2 is the minimum de facto standard nowadays.

The point of certmate is to have a simple url like https://certmate/domain/tls to grab a valid cert from wherever I am, any time. This because I focused on DNS challenge only.

A good feat btw is the deploymenet check, where the app verify if the cert issued is the same deployed on public FQDN.

Of course some more interesting additional features will be added soon like:

- multiple cloud accounts support - deploy to remote nodes - vault integration/support

Enjoy and contribute!