Software ownership in Mexico when employees or contractors write the code.
In Mexico, a program that an employee creates as part of the job or on the employer's instructions belongs to the company unless agreed otherwise (article 103 of the Ley Federal del Derecho de Autor, Mexico's Federal Copyright Law). A program written by an independent contractor passes to the company that commissioned it only if the contract says so in clear and precise terms, because when in doubt the law favors the author (articles 83 and 83 bis). That is why we recommend a written employment contract with job duties and an intellectual property clause for every employee, and a written, paid assignment of rights for every contractor and every founder. An assignment that is not in writing is void (article 30).
The initial consultation lasts 30 minutes, takes place by video call and costs from MXN 1,500 plus VAT. If you engage us, that payment is credited toward your fees. We charge it to reserve that time for people who already have a specific matter. Bookings require at least two days' notice.
Technology and data collection, number 3
GuideCurrent as of November 2026
Programs created by employees
Mexican law defines a computer program as the original expression, in any language or code, of a set of instructions meant to make a computer perform a task. It protects programs as literary works, both as source code, the code the programmer writes, and as object code, the code the machine runs (articles 101 and 102 of the Federal Copyright Law, known in Spanish as the LFDA). Since the amendment of May 14, 2026, article 102 expressly mentions artificial intelligence programs.
When one or more employees create a program and its documentation as part of their job or on the employer's instructions, the economic rights (derechos patrimoniales, the rights to copy, modify and distribute the program, article 106) belong to the company unless agreed otherwise (article 103). For other works made by employees, the law splits those rights in half and, without a written employment contract, leaves them with the employee (article 84). In our opinion article 103 governs software, because it is the specific rule.
You will need to prove that the code came from the job's duties or from your instructions. A written employment contract that describes those duties and covers intellectual property and confidentiality does that work. A weekend project unrelated to the job and done without instructions falls outside article 103.
Contractors and commissioned works
For an independent developer or an agency, the general rule for commissioned works governs. Whoever commissions the work holds the economic rights unless agreed otherwise, as long as the contract is clear and precise, and when in doubt the reading most favorable to the author prevails (articles 83 and 83 bis of the LFDA). That is why, on top of the commission itself, we include an assignment that meets the requirements explained below.
If the contractor works set hours, under your direction and personally, the law may treat that person as an employee, because it presumes an employment relationship between whoever performs personal work and whoever receives it (articles 20 and 21 of the Ley Federal del Trabajo, the Federal Labor Law). We explain this in our guide on contractor or employee status in Mexico.
Moral rights the author keeps
Even when the company holds the economic rights, the programmer keeps the moral rights, which cannot be assigned or waived (articles 18 and 19 of the LFDA). They include being recognized as the author, objecting to distortion of the work, modifying it and withdrawing it from commerce (article 21). In our opinion the contract should acknowledge the programmer's credit, for example in a credits file, and state in writing that the code was made to be integrated into and modified within a company product.
Requirements for an assignment of software rights
An assignment of the economic rights in a program must meet these requirements of the LFDA:
- Be in writing. Otherwise the law declares it void (article 30).
- Be paid, with either a proportional share of the revenue from exploiting the work or a fixed and determined fee, a right the author cannot waive. If the parties do not agree on the amount, the courts set it (articles 30 and 31).
- State its term. Without an express agreement it is deemed to last five years (article 33). Article 103 says the term of an assignment of rights in computer programs is not subject to any limit. Because that paragraph sits next to the employee rule and article 30 requires every transfer to be temporary, with contractors we put the term in writing.
- Describe the work, because the law voids blanket transfers of future works (article 34).
- Be recorded with the Registro Público del Derecho de Autor, Mexico's public copyright registry, to be effective against third parties (article 32).
The program is protected from the moment it is fixed in a medium, even if it is never registered (articles 5 and 162). Recording the work and the assignments creates a presumption that what is recorded is true, unless proven otherwise (article 168).
Code written with the help of artificial intelligence
The law recognizes as an author only the individual who creates a work (article 12 of the LFDA). On July 2, 2025, the Second Chamber of Mexico's Supreme Court unanimously denied amparo directo 6/2025, a constitutional challenge against the judgment of the Tribunal Federal de Justicia Administrativa (the Federal Court of Administrative Justice) that upheld the refusal of the Instituto Nacional del Derecho de Autor (INDAUTOR, Mexico's copyright office) to register an image generated with artificial intelligence. According to INDAUTOR's statement, works generated autonomously by artificial intelligence cannot be registered as copyright works in Mexico.
Neither the law nor that ruling says how much human input is enough when a programmer asks an AI system for code and then reviews, corrects and integrates it. In our opinion, the part your team designs or transforms with its own judgment can be protected as the work of whoever made it. We suggest addressing this in every contract and keeping a record of the human contribution in the code's change history. We go further in our guide on AI at work in Mexico.
Trade secrets and confidentiality
Copyright protects the code, but not ideas, methods or processes as such (article 14, section I, of the LFDA). Business logic and internal processes are protected as trade secrets. The Ley Federal de Protección a la Propiedad Industrial (the Federal Industrial Property Law) defines a trade secret as confidential information that gives a competitive advantage and that its holder safeguards with sufficient means to preserve confidentiality and restrict access (article 163, section I).
If you do not safeguard the information with those means, the law does not treat it as a trade secret. Anyone who has access to it through a job or a business relationship, and was warned that it is confidential, must refrain from disclosing it (article 166). Disclosing or using it without consent to obtain an economic benefit or cause harm carries two to six years in prison and a fine (articles 402 and 403). In addition, since the amendment of April 3, 2026, the administrative violations listed in article 386, including misappropriation of a trade secret, are also sanctioned when committed through artificial intelligence.
We suggest confidentiality agreements that specify which information is confidential, and restricted access to the place where you store your code.
Who owns the code, by who created it
| Who created it | Holder of the economic rights | What to sign |
|---|---|---|
| Employee, as part of the job or on instructions | The company, unless agreed otherwise (article 103 of the LFDA) | Written employment contract with job duties, intellectual property and confidentiality |
| Employee, outside the job and without instructions | In our opinion, the employee, because article 103 does not cover it | Written, paid assignment (articles 30 and 31) |
| Contractor or agency | Whoever commissioned the work, if the contract is clear and precise; when in doubt, the author (articles 83 and 83 bis) | Commissioned work contract with a written assignment, payment and term |
| Founder, before the company is formed | The founder, as author (article 12) | Assignment to the company, written and paid (articles 30 and 31) |
| Artificial intelligence, autonomously | Not registrable as a work (INDAUTOR statement, 2025) | Internal record of the human contribution |
An investor's review
Before investing in a software company, an investor checks that the company owns the code it sells. When we prepare a funding round, we ask for the contracts of everyone who has written code, the founders' assignments, proof of payment for each assignment, registry records if there are any, and the confidentiality agreements. A missing assignment can delay the round or change its terms, and negotiating it costs more once the author has left.
Your options, with their cost and risk
Sign assignments with every author
The cost is drafting the contracts and paying each author a fixed and determined fee or a share of revenue. If the assignments meet articles 30 to 34 of the LFDA, you reach a funding round or a sale with the ownership of the code documented.
Bring developers onto payroll
Code they write as part of their job belongs to the company (article 103). You pay wages, social security contributions and benefits, and you lose the flexibility of hiring by project.
Register the code and the assignments
It is optional, and what is recorded is presumed true unless proven otherwise (article 168). The risk is registering in the company's name before every assignment is signed.
Keep things as they are
It is an option and the decision is yours. Code with no written contract may still belong to whoever wrote it, and the problem usually surfaces in a funding round, a sale or a programmer's contentious departure.
In our opinion the first step is an inventory of who wrote each part of the code and under which contract. If your employment and services contracts need drafting or fixing, with us they start from $4,500 MXN plus VAT, as published on our labor and REPSE page. The full intellectual property practice is under technology and data.
Frequently asked questions about software ownership
Does code my cofounder wrote before we formed the company already belong to the company?+
Not on its own. The author is the individual who creates the work (article 12 of the Ley Federal del Derecho de Autor, Mexico's Federal Copyright Law), and the author's economic rights pass to the company only through a written, paid assignment (articles 30 and 31). We recommend signing it before the first funding round.
Is an intellectual property clause in the contractor's agreement enough?+
It is enough if it is clear and precise, in writing, sets payment and term, and describes the work (articles 30, 31, 33, 34 and 83 bis of the Federal Copyright Law). A generic clause covering everything the person may ever program is fragile, because the law voids blanket transfers of future works.
Do I have to register my software with INDAUTOR, Mexico's copyright office?+
It is not mandatory, because the program is protected from the moment it is fixed in a medium (articles 5 and 162 of the Federal Copyright Law). Registering it creates a presumption that what is recorded is true, unless proven otherwise (article 168), and recorded assignments are effective against third parties (article 32).
Can I patent my software in Mexico?+
Computer programs are not considered inventions when the application claims them exclusively as such or in themselves (article 47, section V and last paragraph, of the Ley Federal de Protección a la Propiedad Industrial, the Federal Industrial Property Law). That is why software is usually protected through copyright and trade secrets.
Is the code we generate with artificial intelligence ours?+
A work generated autonomously by artificial intelligence cannot be registered in Mexico, according to INDAUTOR's statement on the 2025 Supreme Court ruling. Neither the law nor that ruling sets how much human input is enough, so we recommend documenting what your team designed, reviewed and modified.
We review your case
If you are raising capital or selling your company, send us the list of everyone who has written your code and their contracts. We tell you what we found and what we would do, and you decide.