Simple plans for organisations of all sizes

Frequently asked questions

Who counts as a developer?

A developer is any contributor who has made a commit in the last 90 days to one of the repositories you manage technical debt for using Stepsize.

If you are using Stepsize across multiple repositories, we look at unique active developers based on their Git email address.

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, which includes code metadata that isn’t sensitive information such as file paths and commit hashes, but does not include code.

See our Information Security Guide for more detail.

Why do I need Stepsize when I have Jira?

You need Stepsize to decide what to put into Jira.

Technical debt is contextual — the need to pay it back is a function of business priorities.

Stepsize is designed to help you make strategic decisions that serve your business priorities. Once you’ve commissioned some refactoring work, 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 measure technical debt?

The Stepsize integrations allow engineers to report debt directly from their workflow.

When technical debt has had a clear, tangible cost, engineers can record that. In particular, they can track where they’ve lost time, and the product quality issues that can be traced back to tech debt.

This information is then visible to everyone on the Stepsize web app, organised by team and / or functional area of your codebase, showing the total amount of debt and its historical cost.

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

The notion that you have to choose between shipping features and addressing debt is a false dichotomy.

Every project carries some risk related to technical debt. Stepsize helps you identify these risk factors so you can eliminate them before they derail your plans.

You will ship features faster by addressing technical debt that stands in your way.

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

Stepsize has been meticulously designed to focus your attention on technical debt that matters to your business while letting everything else fade away.

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

Do you need access to our code?

No! When you report some debt from your editor or from a pull request, Stepsize builds a Code Location that references the underlying code using metadata that isn’t sensitive, such as the file path, line numbers, and commit hash.

This means Stepsize can let you access your code without itself having access to it.

How will Stepsize help us save time and money?

Stepsize helps you become more efficient.

This means less development time wasted because of mishandled debt, which results in happier and more performant engineers.

It also means less bugs, downtime, and support requests, which results in happier customers and less wasted resources.

Every software project is impacted negatively by tech debt.

Stepsize puts a spotlight on this issue and helps engineers gain well needed visibility to make the correct calls moving forwards in their planning.

Ready to get started?

Start prioritising tech debt today.