Information systems, web services, integrations and mobile apps of any complexity. We also take over systems written by others: we work through the code, find what causes the failures and remove it.
We write new software and bring existing software back into working order. The approach does not depend on scale: first understand how the system should work, then make it work exactly that way.
Accounting, document and industry systems built around your processes: roles and permissions, reporting, audit trail, data storage that meets requirements.
Portals, personal accounts and services built for growing load: from an internal portal to a public service for citizens and customers.
We connect systems to each other and to government platforms: data exchange, queues, redelivery, exchange error logs.
iOS and Android apps for customers or for staff outside the office, together with the back end and an admin panel.
We move manual operations into a system: requests, approvals, reconciliations, exports. First we describe the process as it is, then remove the extra steps.
We take on systems written by other teams or left without support for years: restore the build and documentation, close bugs and continue development.
We support systems we built and systems taken over from other contractors. What counts as an incident, response times and how requests are filed are fixed in the contract and SLA.
Requests are logged and classified by severity; response and resolution times are set in the contract.
We reproduce the bug, find its cause in the code or data, fix it and add a test so it does not come back.
New features and changes for regulatory requirements or new processes — estimated before work starts.
Platforms, libraries and dependencies are updated in planned releases — tested and with a rollback plan.
We remove vulnerabilities, set up access rights and logging, and prepare the system for security compliance checks.
We keep documentation current or restore it: architecture, deployment, user and administrator guides.
Recognize the situation? That's usually where we start.
We work through the code and infrastructure, restore documentation and the deployment scheme, and take the system under support.
Support →We take the system over: check that the code builds and matches the running version, then close critical bugs.
Legacy →We set up logging and monitoring, reproduce the failure, find the cause and fix it — instead of a scheduled restart.
Bugs →We design the exchange, implement it via an API or a message bus, and build in retries and an error log.
Integrations →We describe the process and build an app or web service for it, with roles, reports and change history.
Automation →First we cover the key scenarios with tests, then make the changes and ship the update with a rollback plan.
Enhancements →We listen to the task and look at the current system and data. If a system already exists, we start from its code and logs, not from a slide deck.
We fix scope, stages, timeline and cost. Unclear parts are checked with a prototype.
Short iterations with a demo after each. Key scenarios are covered with tests.
We deploy on your infrastructure or in the cloud, migrate data and train users. Every release has a rollback plan.
We take the system under SLA support: fix, enhance, update.
Debug has worked with servers, networks and data centers since 2013. So when a system slows down, you don't have to find out between contractors whether the code, the database or the server is to blame: we look at the whole chain and fix it where the cause is.
A new system, an enhancement or a failure nobody can catch — tell us in your own words. We'll reply within one business day.
