Turkish Software Developer Refuses to Hand Over Source Code: What Can a Foreign Customer Do? 2026 Updated Guide

A Turkish software developer refuses to hand over source code to a foreign customer. Learn how contracts, copyright ownership, delivery obligations, termination, injunctions, damages and source-code escrow may affect the dispute in Turkey.

A foreign company may spend substantial amounts developing customized software through a Turkish developer only to discover, at the end of the project or after a commercial dispute, that the developer refuses to provide the source code. The customer may possess a functioning application, administrative credentials or executable files while remaining completely dependent on the original developer for updates, security fixes, integrations and future development. Under Turkish law, the customer’s rights cannot be determined merely from the fact that it paid for the software. The development agreement, intellectual-property provisions, scope of the commissioned work, delivery obligations, termination clauses and actual performance of the parties must be examined together. The first legal question is therefore whether the customer is contractually entitled to receive the source code; the second is what rights the customer has to use, modify or transfer the software after receiving it.

Paying for Software Does Not Automatically Resolve Source-Code Ownership

One of the most common mistakes in software-development disputes is assuming that payment for development automatically means that every intellectual-property right belongs to the customer.

Payment, source-code possession, copyright ownership and licensing rights are separate issues.

The contract should therefore be examined carefully before demanding transfer of the code.

Start With the Software Development Agreement

The agreement is normally the most important starting point. Review provisions concerning deliverables, milestones, acceptance, intellectual-property rights, licensing, source-code delivery, repositories, documentation, termination and post-termination assistance.

If source code is expressly listed as a deliverable, the customer’s contractual position may be substantially stronger.

Is Source Code Expressly Included in the Deliverables?

The contract may require delivery of source files, repositories, database structures, build instructions, technical documentation, credentials or deployment materials.

A developer that delivers only a functioning application may not necessarily have completed its contractual obligations if the agreement separately requires delivery of the underlying development materials.

What If the Contract Is Silent About Source Code?

The dispute becomes more complicated.

The parties’ negotiations, project specifications, proposals, statements of work, invoices, emails and actual course of performance may become relevant when determining what the developer promised to deliver.

The commercial purpose of the project may also matter.

Custom Software and Standard Software Should Be Distinguished

A foreign customer that commissioned a completely customized business platform may have a different contractual position from a customer that merely purchased access to the developer’s pre-existing software product.

The company should identify which parts of the system were specifically developed for it and which components existed beforehand.

Background Intellectual Property Can Create Major Disputes

Developers frequently use pre-existing libraries, frameworks, modules, templates and internal tools.

Even where the customer obtains extensive rights in the newly developed software, the developer may retain rights in its pre-existing technology.

The contract should distinguish background technology from project-specific development.

Copyright Ownership Must Be Examined Separately

Software can receive copyright protection under Turkish intellectual-property law. The fact that a customer commissioned development does not by itself answer every question concerning economic rights in the resulting work.

The contractual transfer or licensing of relevant rights should therefore be reviewed carefully.

Source-Code Delivery and Copyright Transfer Are Different

A customer may have the right to receive a copy of the source code without owning all intellectual-property rights.

Conversely, a contract may contain broad intellectual-property provisions while failing to establish a practical process for repository and credential delivery.

Both issues should be addressed.

Review the Scope of the License

If ownership remains with the developer, determine whether the foreign customer has a license allowing it to use, reproduce, modify, maintain or develop the software through another provider.

A license that permits only ordinary use may leave the customer dependent on the original developer.

Can the Customer Hire Another Developer?

This depends on the customer’s contractual and intellectual-property rights.

Before transferring code to another software company, determine whether modification, reproduction and third-party maintenance are permitted.

Confidentiality obligations should also be reviewed.

Repository Access Can Be as Important as Source-Code Files

Modern software projects frequently use hosted version-control repositories.

Receiving a compressed folder containing some source files may not provide the customer with the complete development history, branches, configuration files and other materials necessary to continue the project.

The contractual delivery obligation should therefore be analyzed practically.

Ask for the Complete Development Environment

Where contractually required, delivery may need to include more than application source files.

Depending on the project, relevant materials can include database schemas, deployment scripts, configuration information, API documentation, build instructions and technical documentation.

Credentials Are a Separate Risk

Determine who controls hosting, cloud infrastructure, domain accounts, application stores, databases and administrative accounts.

A foreign customer can face severe operational risk if critical systems remain under credentials controlled exclusively by the developer.

Preserve Evidence Before the Dispute Escalates

Download and preserve contracts, statements of work, invoices, payment records, project-management records, emails, repository notifications, technical specifications and correspondence concerning source-code ownership or delivery.

Digital evidence can disappear quickly after the relationship deteriorates.

Preserve Repository Evidence

If the customer currently has partial access to a repository, preserve legally accessible records showing project structure, commit history, contributors and relevant dates.

Do not exceed existing authorization or attempt to bypass access controls.

Identify Who Actually Wrote the Code

The contracting Turkish company may have used employees, freelancers or subcontractors.

This can create additional intellectual-property questions concerning whether the developer itself obtained the rights necessary to transfer or license the software as promised.

Request Evidence of Subcontractor Rights

Where material portions of the software were created by third parties, review whether appropriate rights were secured.

A customer receiving code without adequate intellectual-property rights may later face claims from another developer.

Open-Source Components Must Be Identified

Customized software commonly incorporates open-source libraries.

Receiving ownership or broad rights in custom code does not eliminate the licenses governing third-party open-source components.

A software inventory can therefore be important before demanding unrestricted ownership of the entire codebase.

Send a Formal Notice Before Litigation

If the developer is refusing delivery despite a contractual obligation, a formal notice can identify the relevant contract provisions, outstanding deliverables and deadline for performance.

The notice should also reserve rights concerning damages, termination and other remedies.

Specify Exactly What Must Be Delivered

A vague demand for “all source code” can create further disputes.

Where possible, identify repositories, source files, documentation, database materials, credentials and other contractual deliverables specifically.

What If the Developer Claims It Has Not Been Fully Paid?

Payment disputes are common defenses to source-code demands.

The customer should compare amounts paid with milestones, acceptance conditions, disputed invoices and any contractual rights to suspend performance.

The developer’s entitlement to withhold delivery should not be assumed merely because an invoice remains disputed.

What If the Software Is Defective?

Source-code disputes frequently accompany allegations that the software is incomplete or defective.

Document crashes, missing functions, security problems, performance failures and deviations from specifications separately from the source-code issue.

Independent Technical Examination May Be Necessary

For a complex platform, an independent software expert may need to determine whether the delivered code is complete, compilable and consistent with the operating application.

A folder labeled “source code” does not necessarily contain a usable development project.

Evidence Preservation Can Become Urgent

If there is a genuine risk that repositories, servers or development records will be deleted, urgent evidence-preservation measures should be evaluated.

Once technical evidence disappears, proving the state of the software at the time of the dispute can become substantially harder.

Can the Foreign Customer Seek an Injunction?

Depending on the contractual rights, urgency and circumstances, interim judicial protection may need to be considered.

The objective may be to preserve evidence, prevent potentially irreversible conduct or protect rights while the underlying dispute is resolved.

The appropriate measure depends on the facts and relief legally available.

Can the Customer Demand Specific Performance?

Where delivery of particular materials is a contractual obligation, the possibility of requiring performance should be examined alongside other contractual remedies.

The precise remedy depends on the agreement, nature of the obligation and circumstances of the breach.

Can the Contract Be Terminated?

Potentially.

If failure to deliver source code constitutes a sufficiently serious contractual breach, termination rights may arise under the contract and applicable law.

Notice and cure provisions should be followed carefully.

Termination Does Not Automatically Solve the Technology Problem

A foreign customer may successfully terminate the agreement but still lack the technical materials required to keep its business operating.

Legal strategy should therefore address both contractual termination and operational continuity.

Can the Customer Claim Damages?

Potentially, if the developer’s breach causes provable losses.

Possible categories may include replacement-development expenses, emergency migration costs, additional technical work and other losses with an adequate causal connection to the breach.

The recoverability and amount of each claim require case-specific analysis.

Lost Profits Require Strong Evidence

Claims that the company “could have earned millions” are substantially more difficult than documented direct expenses.

Preserve customer contracts, project schedules, revenue records and evidence connecting the developer’s breach with the claimed loss.

Cybersecurity Risks Should Be Addressed Immediately

A hostile developer that retains exclusive control over production systems can create a cybersecurity and business-continuity risk.

The customer should identify legally controlled accounts, review access permissions, change credentials it is authorized to control and preserve logs.

Do Not Illegally Access the Developer’s Systems

A contractual dispute does not authorize unauthorized access to another company’s servers or accounts.

Technical recovery should remain within the customer’s lawful access rights.

Personal Data Can Complicate the Dispute

If the software processes personal data, determine where the data are stored, who controls them and whether continued developer access creates data-protection concerns.

Source-code litigation should not distract from immediate obligations concerning personal-data security.

Business Data Belonging to the Customer Should Be Secured

Source code and customer data are different assets.

Even where intellectual-property ownership is disputed, the foreign company should determine its rights concerning its own commercial data, customer information and operational records stored within the system.

Source-Code Escrow Can Prevent Future Disputes

For business-critical software, future contracts can require source code to be deposited with an agreed escrow mechanism and updated periodically.

Release events can include insolvency, prolonged failure to provide maintenance, business closure or other specified circumstances.

Repository Ownership Should Be Negotiated at the Beginning

Foreign customers commissioning bespoke systems should consider requiring development to occur in a repository controlled by the customer or through an agreed shared-access structure.

This reduces dependence on a single vendor.

Define Intellectual-Property Rights Precisely

Future contracts should specify separately:

ownership of newly developed code; rights in pre-existing technology; third-party components; modification rights; sublicensing; source-code delivery; documentation; repository access; and post-termination rights.

A generic statement that “all rights belong to the customer” may not address practical technical issues adequately.

Use Milestone-Based Source-Code Delivery

Do not necessarily wait until the end of a long project.

Contracts can require repository access or source-code delivery at defined milestones so that months or years of development are not controlled exclusively by one supplier.

Foreign Companies Should Address Governing Law and Jurisdiction

International software contracts should clearly identify governing law, courts or arbitration arrangements and notice mechanisms.

A foreign customer should determine where proceedings must be brought before taking emergency legal action.

Arbitration Clauses Must Be Checked

If the contract contains an arbitration agreement, the dispute may need to proceed through arbitration rather than ordinary court litigation.

The availability of emergency or interim relief should be examined separately.

Review Limitation-of-Liability Clauses

Technology contracts often limit recoverable damages.

The customer should review liability caps, exclusions, carve-outs for intellectual-property breaches, confidentiality violations and other relevant provisions before quantifying its claim.

Immediate Action Plan for Foreign Customers

When a Turkish software developer refuses to hand over source code, the foreign customer should immediately preserve the contract and project correspondence, determine whether source code is an express deliverable, review intellectual-property ownership and licensing provisions, secure its lawful access to repositories and infrastructure, identify missing technical materials, investigate subcontractors and third-party components, document payments and software defects, send an appropriate formal demand, preserve technical evidence and evaluate specific performance, interim measures, termination and damages.

Frequently Asked Questions

Does paying a Turkish developer mean the foreign customer automatically owns the source code?

Not necessarily. Payment, physical possession of source code and ownership or licensing of intellectual-property rights are separate questions that should be determined from the contract and applicable law.

Can the customer demand source code if the contract expressly requires delivery?

A clear contractual source-code delivery obligation can provide a strong basis for demanding performance, subject to the remaining terms and facts of the dispute.

What if the contract never mentions source code?

The agreement, specifications, negotiations, commercial purpose and other evidence should be examined to determine the parties’ obligations.

Can the customer give the code to another developer?

That depends on the intellectual-property and licensing rights obtained under the agreement.

Can the Turkish developer withhold the code because an invoice is unpaid?

The contract, payment status and any contractual suspension or withholding rights must be examined. An outstanding invoice does not automatically resolve the issue in every case.

Can the foreign company terminate the development agreement?

Potentially, where the contractual and legal requirements for termination are satisfied.

Can damages be claimed?

Potentially. The customer must establish breach, legally recoverable loss and the necessary causal relationship.

Can the customer request urgent court protection?

Depending on the circumstances, interim measures may need to be considered where there is a serious risk concerning evidence, systems or contractual rights.

What if the source code delivered is incomplete?

An independent technical examination may help determine whether the delivered materials correspond to the functioning software and whether another developer could realistically continue the project.

How can foreign customers prevent this problem?

The development contract should expressly regulate source-code delivery, repository access, intellectual-property rights, modification rights, documentation, infrastructure credentials, subcontractors, open-source components, termination assistance and source-code escrow before development begins.

Client-Focused Legal Support for Software Development Disputes in Turkey

Software disputes involving source-code delivery, intellectual-property ownership, licensing, defective development, repository access, termination, injunctions and damages can threaten the operational continuity of a foreign company doing business with a Turkish technology provider. Fırat Fesih Kaya Law Office assists foreign companies and international customers in contractual and commercial disputes with Turkish software developers. Lawyer Fırat Fesih Kaya provides legal assistance in reviewing development agreements, protecting source-code and intellectual-property rights, preparing formal demands, preserving digital evidence, evaluating interim measures and pursuing contractual claims and damages in Turkey.

Phone:
+90 312 434 22 22

Mobile:
+90 532 769 22 22

Email:
info@firatfesihkaya.av.tr

Address:
Mevlana Boulevard No:221, Yıldırım Tower, Office No:148, 06520 Balgat, Çankaya, Ankara, Turkey