Omnigo

Omnigo, a leading provider of incident management software for public safety and security teams, serves over 2,700 organizations with mission-critical solutions. Their software platform enables end-to-end incident handling, from planning and response to reporting, investigation, and resolution. With distributed development teams maintaining this essential platform, Omnigo transformed their code quality management by switching to DeepSource. Within two months of implementation, their engineering teams achieved unprecedented quality improvements, successfully addressing technical debt while strengthening the reliability of their public safety software.

About Omnigo

Omnigo's engineering organization consists of five product teams with approximately 50 developers spread across the United States, Canada, India, and Brazil. Each team averages eight developers and two to three QA specialists, working on multiple projects that power their comprehensive incident management platform. The teams maintain both legacy systems and modern Angular applications that provide features like real-time resource coordination, automated report generation, and predictive analytics for risk mitigation.

The Challenge

For an organization providing mission-critical public safety software, maintaining high code quality is paramount. While using SonarCloud, Omnigo faced significant challenges managing their extensive codebase:

Our core codebase is about 23 years old. There's just a lot of old practices in there, a lot of tech debt that's never been repaid. With SonarCloud, we couldn't get an effective handle on it.

The challenges were particularly acute in several areas:

• Code Quality: "One project had 63,000 issues across different categories. Some problems had 1,900 instances of the same issue, but with SonarCloud, we couldn't effectively address them."
• Coverage Reporting: "Our code coverage reporting was breaking all the time. For our Angular projects, combining coverage reports from Angular and C# tests was impossible - we had to use two separate pipelines and figure out averages manually."
• Issue Management: SonarCloud's file-first approach made it difficult to address systemic problems
• Limited Automation: No automated fix capabilities to help tackle the large volume of issues
• Pipeline Complexity: "Everything in SonarCloud was done through pipeline steps. It became very difficult and fragile to work on the pipelines."

Why DeepSource

After evaluating various options, Omnigo chose DeepSource, finding it distinctly superior to SonarCloud in several key areas:

1. Intuitive Issue Management: "SonarCloud groups issues by file first - I don't want to go through one file at a time and fix five different things," explains Flynn. "DeepSource groups by problem type instead, which is so much more intuitive. If I have 100 instances of the same problem, that's what I want to know. I want to address the problem systematically."
2. Powerful Autofix Capabilities: "The Autofix feature is beautiful - something SonarCloud doesn't have. The PRs that Autofix generates are really clean, they pass code review, they get through everything. We're seeing a big increase in the action we've been able to take based on the engine that detects code quality."
3. Streamlined Code Coverage Integration: "DeepSource handles our Angular and C# code coverage reporting seamlessly. You just send all the coverage reports to DeepSource and it figures it out. It's so much easier than our previous solution where we needed multiple pipelines."
4. Superior Code Analysis: "One of our project teams has gotten several of their projects to where DeepSource reports zero issues - something we never achieved with SonarCloud. We're finally getting some sunlight on what our technical debt looks like and how to fix it."

Implementation and Results

The rollout was gradual and strategic, reflecting the critical nature of Omnigo's software:

Immediate Impact

Within two months of implementing DeepSource:

• Two newer projects achieved zero reported issues — "something we never achieved with SonarCloud"
• Teams began systematically addressing issues in their 23-year-old core codebase
• Developers across all global teams embraced the platform
• Seamless integration with existing Azure DevOps workflows maintained their quality gates

Quality Improvements

DeepSource's approach to issue management transformed how Omnigo tackled code quality:

• Systematic Problem Solving: "The PRs that Autofix generates are really clean - they pass code review, they get through everything."
• Efficient Issue Resolution: Starting with 63,000 issues in one project, teams could now systematically address and resolve them
• Coverage Maintenance: Teams maintain their 80% code coverage threshold across both Angular and C# codebases with ease

Developer Experience

The transition to DeepSource was met with universal approval across Omnigo's global development teams.

The reaction was pretty universal across all our developers in the U.S., Canada, India, and Brazil — they love it. They like being able to get in and see how easy it is to fix issues.

As a manager, Flynn found the new approach particularly valuable for team oversight: "I can now see when I have a developer who's consistently using an anti-pattern and address that directly. The way DeepSource presents issues makes it much easier to identify and correct problematic patterns across the codebase."

Technical Debt Management

DeepSource's approach to technical debt management proved particularly valuable for maintaining and improving Omnigo's mission-critical software. The platform's ability to identify and categorize issues helped them:

• Clearly visualize technical debt across their codebase
• Prioritize and systematically address issues
• Enable developers to take immediate action through autofix capabilities

Looking Ahead

As Omnigo continues to serve their 2,700+ organizations with critical public safety and security solutions, they're expanding their use of DeepSource. Plans include leveraging upcoming features like software composition analysis (SCA) for third-party dependency management, further strengthening the security and reliability of their platform.

Other teams considering DeepSource should go into it with an open mind. What you're going to get is much easier to use, provides more valuable information, and makes it easier to fix the issues it finds. It's a better engine, it's a better user interface, it's a better approach to code health.