buggregator.dev

What It Is

Buggregator is a free debugging server for development environments, built around the idea of “one UI that aggregates multiple local debugging tools.” It runs independently alongside your application in a Docker container and covers use cases such as exception tracking, SMTP email capture, XHProf performance profiling, VarDumper, Ray, Monolog logs, HTTP request inspection, HTTP Proxy, and SMS testing. Its core philosophy is not to add another intrusive dependency stack to your project, but to let existing SDKs or protocols send data to a local endpoint.

Core Features and Ecosystem

For exceptions, it implements Sentry-compatible endpoints, allowing it to receive stack traces, breadcrumbs, tags, request data, and more by changing the DSN. For email testing, it provides a local SMTP server with support for HTML previews, attachments, headers, and raw MIME. Performance profiling is based on XHProf, with flame graphs, call graphs, function tables, and profile comparisons. The HTTP Proxy can capture outbound requests and responses, while the SMS feature can recognize formats from 40+ providers such as Twilio, Vonage, and Plivo. Its strongest support is around PHP/Laravel/Symfony/Spiral, but through standard interfaces such as Sentry SDKs, SMTP, and HTTP Proxy, it also works across ecosystems including JavaScript, Python, Ruby, Go, Java, and .NET.

Deployment, Open Source, and Pricing

The website clearly lists MIT License, Open source, Free forever, No paid plans, and No feature gates. Deployment options include Docker, Docker Compose, and Binary, and it also mentions team-oriented capabilities such as Kubernetes, external PostgreSQL/MySQL, Prometheus, Webhooks, and Auth0/Kinde SSO. A typical setup starts with a single docker run command, followed by changes to .env values such as Sentry DSN, MAIL_HOST, VAR_DUMPER_SERVER, or HTTP_PROXY.

Pros and Cons

The main advantages are that it is free, runs locally, and is privacy-friendly: debugging data does not leave your machine. It also reuses existing SDKs, which means fewer project dependencies and less code change. It can replace a whole chain of common development-time tools such as Mailhog, Mailtrap, Ray, Blackfire, RequestBin, and mitmproxy. The limitation is that it is clearly positioned for development environments and should not be understood as a full production monitoring SaaS. Performance profiling still requires the XHProf extension and framework packages. The text does not show information about commercial SLAs, hosted cloud services, or formal enterprise support.

Who It’s For and Access from China

It is suitable for PHP backend teams, local multi-project development, microservice debugging, and teams that need to avoid the cost or risk of sending real emails, SMS messages, or API calls. The text does not provide information about access from China, so real-world testing is required. Since it can be fully self-hosted, even if the official website or image pulls are affected by network conditions, it should theoretically be possible to work around this through source code, image caching, or a private image registry. Alternatives include Sentry, Mailhog, Mailtrap, Blackfire, Ray, Charles, Fiddler, and mitmproxy.