Bugsink 1.0 Release

Klaas van Schelven; December 3 - 1 min read

I’m thrilled to announce the release of Bugsink 1.0!

Bugsink is an error tracking tool that notifies you about issues in your application as they happen. It gathers all the information you need to triage and fix problems in one place, and it’s fully self-hosted – you run it on your own servers, giving you complete control over your data.

With 1.0, Bugsink has reached a level of polish that makes it a production-ready choice for anyone who needs a scalable, reliable, and privacy-focused error tracking system. Whether you’re a solo dev or part of a team, Bugsink is designed to work for you, without getting in the way.

Thank you to everyone who has used Bugsink so far, provided feedback, and helped shape its development. Version 1.0 wouldn’t be what it is today without your support.

What’s new

The 1.0 release isn’t about flashy features – it’s about making Bugsink as seamless as possible to use. I’ve focused on removing friction in the setup process, improving documentation, and refining configuration options to make installation a breeze.

There’s now a sample docker-compose file (in addition to the plain Docker and pip install based workflows), specific SDK setup instructions, and clearer error reporting to ensure you can hit the ground running.

Other updates include a friendlier onboarding process, better UI cues, and clearer error messages based on real-world feedback. Bugsink 1.0 is built to work the way developers expect: fast, straightforward, and reliable.

Trying it

If you’re ready to take your error tracking to the next level, follow the installation guide and get started with Bugsink.

Alternatively, just paste the following command into your terminal:

docker pull bugsink/bugsink:latest

docker run \
  -e SECRET_KEY=lQ9cB9OfOhMAe6SEaKuMB6liHrBBrEk7oJ2XZY9aLWf1nkBAlu \
  -e CREATE_SUPERUSER=admin:admin \
  -e PORT=8000 \
  -p 8000:8000 \
  bugsink/bugsink

Visit http://localhost:8000/, where you’ll see a login screen. The default username and password are admin.

Now, you can set up your first project and start tracking errors.