Who Owns Code Written in Ukraine? Three Regimes and Five Clauses That Do Not Travel

Technology 15 min read Share

The short answer to who owns software written in Ukraine is on our IT contracts page: the employer or the customer, unless the contract or the law says otherwise. This article is for counsel who need the longer answer, because two questions keep coming back in transactions. The first is when the code was written. Ukrainian law has moved its default twice in five years, and a codebase of any age straddles more than one regime. The second is what happens to an IP clause drafted in London or New York when it meets the Ukrainian Civil Code. Several familiar formulas work less well than their drafters assume, and one of them, the present assignment of future rights, runs into an express statutory prohibition.

Source code with line numbers on a dark screen — who owns code written in Ukraine
Contents
  1. 1 The default did not flip in 2023. It moved twice
  2. 2 Five clauses that do not travel
  3. 3 Choosing English or New York law does not settle it
  4. 4 Code nobody wrote
  5. 5 Drafting checklist
  6. 6 Frequently asked questions

In short: Ukrainian law has given commissioned code to the customer, and software written by employees to the employer, since 14 August 2021, not 2023; code commissioned earlier without an IP clause is, as a rule, jointly owned. A day-one assignment of future rights runs into Article 1113(1) of the Civil Code, a licence covers only the uses it names, and an IP transfer must be in written or electronic form. Choosing English or New York law does not reliably take a transfer outside these rules where the rights will be enforced in Ukraine.

The default did not flip in 2023. It moved twice

Most summaries date the change to 1 January 2023, when the new Law on Copyright and Related Rights (No. 2811-IX) came into force. For software, the first move came some sixteen months earlier, and it came from an unexpected place: Law No. 1667-IX, better known as the Diia City law, which in its final provisions amended the Civil Code for everyone, not only for Diia City residents. The result is three regimes, plus a fourth for the military.

Code createdWritten by an employeeWritten to order (commissioned)
Until 13 August 2021Civil Code (from 2004), Art. 429: joint ownership of employee and employer unless the contract provides otherwise; the 1993 Copyright Law in its later wording, Art. 16, pointed towards the employer, and the two were never cleanly reconciledCivil Code (from 2004), Art. 430: joint ownership of developer and customer unless the contract provides otherwise
14 August 2021 – 31 December 2022Civil Code, Art. 440(3) as added by Law No. 1667-IX: computer programs and databases belong to the employer unless the contract provides otherwise; other works (documentation, interface graphics, texts) remain jointly ownedCivil Code, Art. 440(4) as added by Law No. 1667-IX: the customer, unless the contract or a law provides otherwise; the customer acquires the rights at the moment following creation
From 1 January 2023Law No. 2811-IX, Art. 14, and Civil Code, Art. 440(3): all works pass to the employer in full from the moment of creation, unless the contract or the law provides otherwiseLaw No. 2811-IX, Art. 15, and Civil Code, Art. 440(4): pass to the customer in full from the moment of creation, unless the contract or the law provides otherwise

The fourth regime is narrow but matters in defence work. Since 12 December 2025, works created by servicemen in the course of their official duties belong to the State (Article 14¹ of Law No. 2811-IX); since 1 February 2026 the Civil Code refers that question to the law (Article 429(2), as restated by Law No. 4671-IX). We cover it in Who Owns Ukrainian Defence Technology?.

Two exceptions run through all these periods, in slightly different words. Moral rights belong to the individual author, save where the law provides otherwise, and cannot be transferred except as the law allows. And a commissioned work of fine art, such as an illustration or a logo, stays with its author unless the contract or the law provides otherwise (Article 1112(3) of the Civil Code). Since 14 August 2021 that rule has not covered a work created specifically as an element of a computer program (Article 440(4) of the Civil Code until the end of 2022; since 2023, Article 15(2) of Law No. 2811-IX). The icon set your designer drew for the app is an element of the program; the brand logo drawn under the same contract may not be.

Neither the 2021 nor the 2022 law says anything about works created before it. Law No. 2811-IX has no transitional rule on ownership; its transitional provisions deal with terms of protection and other matters (Section VI). In our view, ownership of a work is governed by the law in force when the work was created, which follows from the rule against retroactivity in Article 58 of the Constitution. In due diligence this becomes a dating exercise. Commit history is not proof of the moment of creation, but it is usually the best evidence available, and it should be preserved before any repository is migrated. The real exposure is code commissioned before August 2021 without an IP clause. Its customer is a co-owner, and under Article 428 of the Civil Code jointly owned rights are exercised jointly unless the co-owners agree otherwise. In our view, such a customer cannot grant an exclusive licence or assign full title without the developer. The cure is a confirmatory assignment from the developer. Because that code already exists, the prohibition discussed next does not stand in the way.

Not sure which regime your codebase falls under? Send us the development contracts and the repository timeline — we will date the layers and mark where a confirmatory assignment is needed.

Five clauses that do not travel

1. “Hereby assigns” all future rights

English law expressly allows an assignment of future copyright, signed by the prospective owner, which vests in the assignee when the work comes into existence (Copyright, Designs and Patents Act 1988, section 91). The US Court of Appeals for the Federal Circuit treats “does hereby assign” as a present assignment of rights that do not yet exist, with equitable title passing at once (FilmTec Corp. v. Allied-Signal Inc., 939 F.2d 1568 (Fed. Cir. 1991); Board of Trustees of Leland Stanford Junior University v. Roche Molecular Systems, 583 F.3d 832 (Fed. Cir. 2009), both patent cases). Ukrainian law says the opposite. Under Article 1113(1) of the Civil Code, the subject of a contract for the transfer of economic IP rights cannot be objects and rights that did not exist when the contract was concluded. The rule is not new: the 1993 Copyright Law, in its later wording, said the same of contracts transferring rights to use a work (Article 33(3)). The Civil Code itself has said it expressly only since 2023; in our view, a day-one assignment signed in 2021 or 2022 should not be relied on for code written after signature either.

A standalone IP assignment signed with a Ukrainian contractor on day one therefore does not, on its terms, carry code written on day two.

JVS Law viewIn our view, the answer lies in the structure rather than the wording. A contract whose subject is creating code to the customer’s requirements within a set time is a commissioning contract (Article 1112(1) of the Civil Code), and under Article 15 of Law No. 2811-IX the rights pass to the customer by force of law at the moment of creation, unless the commissioning contract provides otherwise, so no assignment of future rights is needed.

Whether a contract qualifies depends on its terms: the creator must undertake to create the work to the customer’s requirements within a set time (Article 1112(1)). In our view, a time-and-materials or open-ended services arrangement may not pass that test. Many contracts with Ukrainian sole proprietors (FOPs) are drafted instead as services agreements with an IP assignment attached. If that form is kept, the rights in each deliverable should be transferred by a signed acceptance act that identifies the code, so that each transfer concerns rights that already exist.

2. Rights not listed are rights not granted

A Ukrainian licence is read narrowly. Uses that the licence does not define are deemed not granted (Article 1109(6)). Without a territory clause the licence covers Ukraine only (Article 1109(7)). A licence is non-exclusive unless it says otherwise (Article 1109(4)). Terms contrary to the Code are void (Article 1109(9)). A catch-all such as “all media now known or hereafter devised” therefore does little work in a Ukrainian licence. The uses that matter should be named: reproduction, modification, distribution, making available online, sublicensing. An assignment is less exposed, because rights may be transferred “in part or in full” (Article 1113(1)). An assignment should therefore say “in full” and still name the key uses.

A commissioning contract has its own requirement: it must define the ways and terms on which the customer will use the work (Article 1112(2)). In our view, a contract that relies on the Article 15 default should still describe the intended use. Otherwise the developer can argue that the parties “provided otherwise” and agreed a narrower purpose.

3. Form is a validity requirement

A contract disposing of economic IP rights must, save where the law provides otherwise, be in writing; otherwise it is void (Article 1107(2) of the Civil Code). Since 2023 the Code has said expressly that electronic form will do. Electronic form is enough, and electronic signatures work for this. But an IP transfer agreed in an e-mail exchange, a ticket comment or click-through contributor terms is exposed: an exchange of e-mails may satisfy the written-form rule (Article 207(1) of the Civil Code), but proving who agreed to what, and that it was signed, is another matter. For code from contributors outside a signed contract, the gap is in the chain of title, not in the paperwork.

4. Restraints on the creator are void

Terms that restrict the creator’s right to create other works are void, both in a commissioning contract (Article 1112(4)) and in an assignment (Article 1113(2)). In our view, a broad non-compete or exclusivity covenant in a development agreement with an individual developer is exposed to this rule, at least where it restricts creative work as such rather than the use of confidential information or the solicitation of clients and staff. In our view, there is one statutory route around it. A Diia City resident may agree a non-compete with any of its “specialists”, which include sole proprietors engaged for qualifying activities, if the covenant is paid, in writing, limited to 12 months after the relationship ends and specific as to territory and competing activities (Articles 1(1)(15) and 27 of Law No. 1667-IX). An NDA is unaffected in either case.

5. Nominal consideration

Where economic rights pass to an employer or customer, the author is entitled to remuneration (Articles 14(2) and 15(3) of Law No. 2811-IX). Terms of a transfer agreement that worsen the creator’s position compared with the law are void (Article 1113(2) of the Civil Code). The contract should say that the fee includes remuneration for the creation of the work and the transfer of rights; for employees whose duties expressly include creating such works, Article 14(2) allows it to be included in salary by agreement. A US-style recital of “one dollar and other good and valuable consideration” is, in our view, an invitation to a remuneration claim rather than a defence to one.

Choosing English or New York law does not settle it

The Ukrainian Law on Private International Law lets the parties choose the law of an IP contract: transactions concerning IP rights follow the ordinary conflict rules for contracts (Article 36). Two provisions limit what that choice achieves. Ukrainian mandatory rules apply whatever law the parties have chosen (Article 14(1)). The protection of IP rights is governed by the law of the state where protection is sought (Article 37). Whether Articles 1107(2) and 1113(1) of the Civil Code are mandatory rules in that sense is open. Whether a Ukrainian copyright exists and can be transferred is, in most systems, treated as a question for the law of the protecting country rather than the contract law (compare Article 5(2) of the Berne Convention). In our view, an English-law assignment of future works from a Ukrainian developer should not be the only link in the chain for rights that will be enforced in Ukraine.

Code nobody wrote

Ukraine is one of the few jurisdictions with a statutory answer for machine output. Article 33 of Law No. 2811-IX creates a sui generis right in non-original objects generated by a computer program without the direct participation of a natural person. The right lasts 25 years, carries no moral rights and may belong to the owners of rights in the program or to its lawful users. The contract may determine who holds it (Article 33(2)). Works created by people using computer technology are not such objects; they are ordinary works. Most AI-assisted code, where a developer prompts, selects, edits and integrates, is therefore likely to be an ordinary work under Articles 14 and 15.

The gap is in the remainder. In our view, the employer and customer defaults in Articles 14 and 15 speak of “works” and may not capture sui generis objects, while Article 33(2) points to the lawful user of the generating tool, who is often the developer and not the customer. The fix is one sentence in the contract:

Sample clauseSui generis rights in objects generated in the course of the engagement belong to the customer.

Article 33(7) adds a condition that no contract can remove: the right is enjoyed only if the rights in the material used to generate the object were respected.

Re-papering a development agreement with a Ukrainian team? Send us the IP clauses — we will mark the ones Ukrainian law rewrites.

Drafting checklist

  1. Date the code: before 14 August 2021, the period to 31 December 2022, or from 1 January 2023; for the oldest layer, obtain confirmatory assignments of existing code.
  2. Frame development as a commission to the customer’s requirements, or transfer each deliverable by a signed acceptance act; do not rely on a day-one assignment of future rights.
  3. Assign “in full” and still name the key uses; in licences, name every use, the territory and exclusivity.
  4. Describe the intended use of commissioned code, even where you rely on the statutory default.
  5. Put every IP transfer in a signed written or electronic document, including contributions from outside the core contract.
  6. State that the fee includes the author’s remuneration for creation and transfer.
  7. Keep non-competes out of development agreements with individuals, or use the Diia City route where it is available.
  8. Allocate sui generis rights in generated output to the customer.
  9. Check whether the code is dual-use: the transfer of such code abroad is an export of technology and needs a permit if it is on the control lists, whoever owns it.
  10. Close the second link: rights that vest in a Ukrainian company reach a foreign parent only through a contract, such as a licence or assignment.

Frequently asked questions

We commissioned code from a Ukrainian developer in 2020 and the contract has no IP clause. Do we own it? Probably jointly with the developer. Before 14 August 2021, commissioned works were jointly owned by the creator and the customer unless the contract provided otherwise (Article 430 of the Civil Code), and joint rights are exercised jointly (Article 428). The fix is a confirmatory assignment in writing with stated remuneration. Because the code already exists, the ban on assigning future rights in Article 1113(1) does not apply.

Does an English or New York governing-law clause avoid Article 1113? Not reliably. The Ukrainian Law on Private International Law allows the parties to choose the law of an IP contract (Article 36), but it also preserves Ukrainian mandatory rules (Article 14(1)) and applies the law of the protecting state to the protection of IP (Article 37). For rights enforced in Ukraine, structure the transfer so that it works under Ukrainian law as well.

Who owns AI-generated code under Ukrainian law? Code that a developer writes with AI assistance is usually an ordinary work and follows the employer and customer defaults. Output generated without the direct participation of a person attracts a separate 25-year sui generis right (Article 33 of Law No. 2811-IX), which may belong to the owner or lawful user of the generating program unless the contract allocates it. Allocate it expressly.

Can we bind a Ukrainian contractor with a non-compete? A term restricting a creator’s right to create other works is void in commissioning and assignment contracts (Articles 1112(4) and 1113(2) of the Civil Code). Separately, a Diia City resident may agree a paid, written non-compete of up to 12 months with its specialists, including sole proprietors engaged for qualifying activities (Articles 1(1)(15) and 27 of Law No. 1667-IX). NDAs remain available in both cases.

We act as Ukrainian counsel alongside the client’s lead firm; see our pages on IT contracts and software transactions and technology transfer, R&D and investment. This note is not legal advice. Ukrainian law is stated as of 17 November 2026.

Share