See  everything happening in your running Django app

Install Kolo

Debug your Django app 10x faster, get instant access to all the context you need, and ramp up quickly on unfamiliar code.

Built for

Runtime data

Input arguments, return values and local variables from the selected request are shown right next to your code, giving you a strong mental model of exactly what happened at runtime

HTTP Requests

Inspect all outbound HTTP requests that were made during the request, including request and response bodies, timing information, and headers. This all happens inside of VSCode, so you can quickly find what you need and copy-paste.

SQL Queries

See all the SQL queries that were executed during the request, dig into specific queries, and see exactly what the database received from Django

Celery Background Tasks

Kolo will show you all celery background tasks that were enqueued during the request. The branches that begin with a green line indicate the beginning of a celery task execution.

Looking for assistance? We're here to help with your Kolo set up!


Kolo is in Beta. What does that mean?
How is Kolo different from a regular debugger?
  • Debuggers don't help when it's not clear where a breakpoint should be set
  • When a specific breakpoint is not getting hit, debuggers don't tell you why it wasn't hit (and what happened instead)
  • If you want to know what happened before a breakpoint, you're out of luck. If you want to know what happened after a breakpoint you have to slowly and carefully step through your code using the debugger's interface
  • Debuggers can help you gather context for a specific point during the code execution, but they aren't great at giving you an overview of everything that happened. If you don't know exactly what you're looking for and where to find it, debuggers can be surprisingly unhelpful
  • If you make a mistake with using the often confusing debugger interface of weirdly shaped arrows, then you need to start all over and hopefully do the right thing this time around
Can I use Kolo in production and staging or just locally?
How much does Kolo cost?
Who is building Kolo?
How is Kolo different from Django Debug Toolbar?
What data is being shared with Kolo?
Where can I find more information about how to install and set up Kolo?
Does Kolo only work with VSCode or does it work with other editors and IDEs?

Kolo is the tool I always wanted during the last seven years of building Django apps (and during the one year I was working on the Rails app!). It always felt like the context I needed to make progress was so close, yet so hard to actually get to. Surfacing this context is the core aim of Kolo.

We use Kolo for developing Simple Poll and have done so for the past year. Simple Poll is one of the most popular apps for Slack with millions of users each year and Kolo has helped us iterate and build more quickly. I'm excited to see how Kolo helps you and your team!

Wilhelm Klopp, Creator of Kolo and Simple Poll

Stay in the loop

You're subscribed!
Oops! Something went wrong while submitting the form.