In a Russian IT company bankruptcy, separate customer-owned data and deliverables from the debtor’s services and rights, preserve authorised access, export tested backups and review the contractual chain through which source code was created. An app may run in a third-party cloud, the domain may be registered to an employee, contractors may have written the code, and the customer may control the data. Payment alone does not always prove transfer of exclusive rights.
Code and title differ
Files in a repository do not by themselves prove ownership of exclusive rights.
Export and test the data
Backup format, completeness and restoration matter more than a promise to keep the service online.
Infrastructure is distributed
Cloud, domain, certificates, app stores and payments may belong to different accounts.
Quick self-check
- Contract, specification, acceptance records, transfer terms and employee or contractor documents are located.
- Repositories, branches, builds, documentation, keys and dependencies are mapped without exposing secrets.
- Customer data is exported in a usable format and backup restoration is tested.
- Owners of domains, cloud accounts, certificates, app stores and devices are identified.
- Development, support, subscription, uptime and delivery claims are calculated separately.
Title to Code and Deliverables
Review the contract, specification, acceptance records, employee-work provisions and contractor agreements. Possession of source code does not equal exclusive title, and payment does not replace agreed transfer language. Open-source components and licence restrictions require separate mapping.
Repositories, Keys and Documentation
Map Git repositories, CI/CD, package registries, containers, APIs, certificates and administrative roles. Do not disclose or copy secrets without authority. Transfer should include key rotation, an action log and least-privilege access testing.
Customer Data and Backups
Determine data format, volume, currency and processing basis. Before shutdown, perform an agreed export, test readability and restoration, record the snapshot date and remove unnecessary copies. A database may combine records of several customers and rights in its software structure.
Cloud, SaaS, Domains and Continuity
Identify owners of cloud accounts, domains, DNS, certificates, email, analytics and app listings. A subscription payment does not guarantee SaaS continuity during insolvency. Build a migration plan covering export, parallel environment, domain switch, integration tests and user notice.
- inventory services;
- export data;
- verify rights;
- rotate authorised keys;
- document transfer.
Equipment, Staff and Claims
Laptops, servers and licences may be debtor-owned, leased or customer-provided. Record return with serial numbers and safe data handling. Calculate fees, damages and incomplete work separately; neither product operation nor completeness of title can be guaranteed in advance.
| Asset | Review | Practical outcome |
|---|---|---|
| Source code | Authorship and contract chain | Rights and file set |
| Repository | Owner and roles | Controlled access |
| Customer data | Basis and format | Tested export |
| Cloud and domain | Account and payer | Migration plan |
| Equipment | Owner and stored data | Return or transfer record |
Frequently Asked Questions
Does paid code automatically belong to the customer?
Not always. Review transfer terms, acceptance and the creation chain.
May the entire repository be collected?
A legal or contractual basis is required, with separation of third-party components, secrets and data.
Must the cloud provider keep the service running?
Its duties follow a separate contract and payment; continuity of the debtor’s product is not guaranteed.
Does a domain enter the estate?
Review registrant, registrar terms, payment and nature of the right; branding alone is insufficient.
How is this different from online-school bankruptcy?
This guide owns software development, code, repositories, infrastructure, data and IP rights.
Legal Sources
- Federal Law No. 127-FZ.
- 2026 Amendments to Federal Law No. 127-FZ.
- Russian Civil Code Part Two.
- Russian Civil Code Part Four.
- Federal Bankruptcy Register.
Related guides: Russian online school bankruptcy, Russian advertising agency bankruptcy and delivery of company records to a Russian insolvency administrator.
Could Code, Data or Cloud Access Be Lost?
We can review contracts, title chain, infrastructure, backups and claims without promising service continuity.
BOOK AN INITIAL CONSULTATIONGeneral information as at 28 August 2026. Treatment depends on contracts, creation chain, licences, access authority, data set and insolvency stage.