← Directory

Buggregator

Buggregator is a free, self-hosted debugging server for PHP (Hypertext Preprocessor) applications, with optional support for other languages through its…

  • Development
  • Monitoring & Logging
  • Tools & Utilities
Buggregator is a free, self-hosted debugging server for PHP (Hypertext Preprocessor) applications, with optional support for other languages through its integrations. It collects debugging payloads, logs, variable dumps, profiler data, and incoming email captures in a local web interface, helping developers inspect runtime issues without paid tools.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

45/100 Fair

Maintained
79last commit 59 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
0
Open issues
0
Last commit
2026-08-17
Activity
stale

Checked 13 days ago - source: GitHub (markuszeller/buggregator)

Resources & Compatibility

Requirements not published yet.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up Docker Compose with port 8000 Before starting, use the Docker Compose example (the file that starts the app's container) that maps the app's port 8000 to 127.0.0.1:8000 (your own computer) and mounts ./buggregator.yaml into the app. Without port 8000 you cannot open the web interface, and without the mounted config your project list is not preserved. source
  • Start Trap to get debugging data Trap (the PHP debugging server) should be started with the --ui flag, usually by running vendor/bin/trap --ui in your project. If Trap is not running, your PHP code cannot send debugging sessions to Buggregator. source
  • Send PHP logs to port 9913 For PHP logs, point Monolog (a PHP logging library) to 127.0.0.1:9913. If this port is not configured correctly, warning and error logs will not appear in Buggregator. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which ports should be exposed for Buggregator?

Expose port 8000 for the web interface, 1025 for SMTP capture, 9912 for VarDumper, and 9913 for Monolog logs. The Docker example maps these ports to the host.

How do I keep the project list in Docker?

Mount the application's buggregator.yaml configuration file into the container. Without the mounted config, the project list is not preserved.

Why does Trap not send debugging sessions to Buggregator?

Trap must be started in the project with the UI enabled, usually with vendor/bin/trap --ui. If Trap is not running, PHP code cannot send debugging sessions to Buggregator.

Does Buggregator keep debugging data after a restart?

The embedded SQLite database is in-memory by default for instant startup. A file-based persistence option is available if you need the data to survive restarts.

Answers sourced from docs.buggregator.dev, github.com, github.com

Community

Collected 16 days ago - public community threads