PricingBlogDocumentationDocs
LoginRegister

GlitchTip 6.1 released

GlitchTip 6.1 is a feature heavy release, while keeping everything optional and simple.

Cold Storage with optional DuckDB

It’s time to reduce your storage costs while keeping old data around longer.

Our competitors use several databases, giving benefits of both row and columnar databases at the cost of operational complexity and sky-high resource needs. GlitchTip 6.1 enables DuckDB by default when either a volume or S3-compatible object storage is present.

The best part is that DuckDB is simple — it’s just part of our Python process and it stores Parquet data cheaply via better compression. Your GlitchTip instance may already be using object storage for source map, minidump, etc. uploads.

New Configuration Settings:

  • GLITCHTIP_EVENT_HOT_DAYS: Number of days to store in fast Postgres storage.
  • GLITCHTIP_EVENT_COLD_DAYS: Number of days to store in cheap Parquet storage, if available.

Enable today and get your hosting bill down. Note that DuckDB does use more RAM (we default to an extra 128MB needed), but it is still well under the 32GB our competitor recommends.

Logging

The open-source sentry-sdk added logging support and it’s now supported in GlitchTip. We strongly recommend using it with DuckDB enabled, as logging storage costs grow quickly.

Model Context Protocol (MCP)

GlitchTip doesn’t force AI on you. We don’t sell it ourselves. But MCP is there if you want it. Use it with tools like Claude Code or Zed or whatever you decide to fit YOUR needs, not our VC funders (which we lack). Ask your own agent to identify slow SQL queries, triage (and fix) issues, or anything else you can imagine. It’s fully optional, disabled by default, and puts you in control of your own data.

Performance Monitoring Improvements

Did I say MCP can identify slow SQL queries? GlitchTip 6.1 refactors our internals for performance monitoring, supporting both transactions and spans. Due to the huge volume of span data, we do require DuckDB to be enabled for spans (transactions will continue to work without). These are available today in our API and MCP server. Frontend and further refinement is coming soon.

Minidump and Source Contexts support

We continue refining our stacktrace enhancement stack. 6.1 now supports minidump and source contexts for Java.

Platform as a Service and Railway support

A core value of GlitchTip is to be fully OSI-approved, open source, and easy to host. To achieve that, we officially support many PaaS vendors and have added an official Railway template. I won’t insist on your trust: if you don’t want me hosting GlitchTip, host it yourself or use one of many PaaS providers such as Railway, PikaPods, and Elest.io.

What’s Next?

We’re going to pivot away from prioritizing donations and toward being clear that we expect for-profit companies to fund the open source that they use. To improve that experience, we'll be working to roll out “license keys”. This will include self-serve sign up for a license key based support plan. When set, we’ll replace the “Support GlitchTip” banner with a support page. This is 100% open source. Nothing will stop you from hacking it and lying about having support, but when you request support in-app, it will attach an ID that lets us check if you're an active user in Stripe and prioritize the support request accordingly.

We’re also working to keep our frontend in sync with backend features, which we typically develop first. We’ll expose features like “Resolve in next release” and the new performance data. Our home page and general lack of dashboards is also on the radar.

Sentry-cli recently switched to a non-free license. So we’re building a drop-in replacement: glitchtip-cli. Most end users can likely keep using either project, though you may want to check with your compliance team. Users who wish to retain using a fully OSI-approved MIT cli are encouraged to try out glitchtip-cli and report bugs. We’ll mark it 1.0.0 when stable for production usage. GlitchTip CLI is also slightly smaller and offers more features for GlitchTip-specific workflows.

Call to Action: Contribute

GlitchTip is 100% built and funded by users. No VC. No one to answer to but you.

Support the project

Community & Social