How Terakeet fixed 70% of their technical debt
Read the case study now

Document and fix issues in your codebase

Turn meaningless TODOs into actionable issues that sync with your issue tracker.
Fight tech debt and ship features faster.

Resolve 8x more technical issues

When using Stepsize with your issue tracker and ship up to 3x faster

The best of issues and TODOs

Stay in your editor

Create and view issues directly in your editor. No more context switching.

Share knowledge

Document your code, in the codebase. Everyone knows what there is to know.

Fix key issues

Bring visibility to technical issues. Make codebase health a team priority.

Bring visibility to technical issues

Before Stepsize

Technical issues are hidden in your backlog and in TODO comments.

After Stepsize

Technical issues are visible based on the code and domains you’ll work on.

Nothing short of game changing

Read the case study
Breno da Mata
Senior Software Developer at Terakeet
How one small change allowed Terakeet to fix 70% of their technical debt

“Linking maintenance issues to code was exactly what we were looking for.

We’ve now fixed 70% of our technical issues. Knowing that we can rely on Stepsize for tech debt gives us immense peace of mind!"

Works with your existing tools and workflows

Stepsize works with most code editors and project management tools. We also support all programming languages.

Visual Studio Code
Coming soon
Android Studio
Coming soon
AppCode
Coming soon
CLion
Coming soon
DataGrip
Coming soon
DataSpell
Coming soon
GoLand
Coming soon
IntelliJ Idea
Coming soon
PhpStorm
Coming soon
PyCharm
Coming soon
Rider
Coming soon
RubyMine
Coming soon
WebStorm
Coming soon
Sublime Text
Coming soon
Vim
Coming soon
Visual Studio
Coming soon
Jira
Coming soon
Asana
Coming soon
Azure DevOps
Coming soon
GitHub
Coming soon
Linear
Coming soon
Bitbucket
Coming soon
ClickUp
Coming soon
GitLab
Coming soon
Shortcut
Coming soon
Trello
Coming soon

Frequently Asked Questions

What data is leaving my perimeter and going into the Stepsize cloud? What if I’m not allowed to upload anything to the cloud?

+
-

None of your code goes into the Stepsize cloud.

The Stepsize integrations have been designed with privacy in mind. We store the minimum amount of 3rd party data needed to provide our service, including code metadata that isn’t sensitive information such as file paths and commit hashes (does not include code).

See our Information Security Guide for more detail.

Why do I need Stepsize when I have Jira?

+
-

Tech debt without context, can’t be prioritised.

This creates a vicious cycle in existing backlogs (like Jira).

  1. Issues are logged
  2. Issues lack context
  3. Issues can’t be prioritised
  4. Backlog becomes overwhelming
  5. Repeat

Therefore you need Stepsize to decide what to put into Jira.

Stepsize allows you to gain context by allowing engineers to report tech debt straight from their editors. Once you know which debt you want to fix first, it goes into Jira. But until then, you can keep your backlog free of tickets that say “Refactor xyz” with no clear purpose or context.

How will you help us reduce technical debt while we’re under pressure to ship features?

+
-

Stepsize is designed to fit into your existing workflow, so engineers can report tech debt without sacrificing roadmap efficiency. Once you have a prioritised list of tech debt, you can start fixing it and actually increase your engineering velocity.

Isn’t there a risk we’ll want to refactor everything even though we don’t need to?

+
-

Stepsize has been meticulously designed to focus on context and prioritisation so that you’ll always know which debt is worth your time.

You’ll actually find the opposite — having a clear view of technical debt helps your team focus on impactful work and ignore the rest.

How will Stepsize help us save time and money?

+
-

Stepsize increases your team’s velocity by allowing you to fix your most important tech debt.

This means less time wasted on mishandling debt, bugs, downtime, and support requests, which results in happier customers and engineers.

How can we develop this new habit of tracking technical debt?

+
-

If you’ve been tracking issues in a spreadsheet or in a backlog, you’ve already been doing it. It’s just an easier process as it all happens in an Engineer’s editor.

Plus, Stepsize displays the data you track in the right places at the right moment, so engineers will be reminded to keep tracking debt.