Who Owns the Code of Your Website or Application?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

GitHub · LinkedIn.

Published: · Last technical review:

For websites I develop, the code and content belong to the client. For applications and other software developments, ownership or usage licensing is agreed on a project-by-project basis. I suggest specifying what you receive and what you may use before finalising the scope, without inferring an automatic assignment.

Criteria: first identify what you are commissioning

The question about code requires context. Commissioning a website is not the same as commissioning an application or other software development. My published answer distinguishes those cases. To help you decide, I maintain that distinction from the start instead of using a generic phrase suggesting that everything will be yours.

I suggest starting with the object of the commission: a new website, a new application, or work on an existing tool. This is an editorial preparation guide, not an exhaustive contractual classification. The key point is that the conversation does not conflate the deliverable you want with terms applicable to another type of project.

Project under review Terms I do publish What remains to be agreed
Website Code and content belong to the client Deliverables of the commission
Application or other development Ownership or licence on a case-by-case basis Specific agreement
Evolution of existing PHP Maintenance and evolution service Scope of work on the existing system

Code, content, and usage do not answer the same question

When commissioning software, it is advisable to distinguish three levels: ownership of content, transfer of source code ownership, and the licence to use the application in your company. That distinction helps formulate questions, but it does not replace the terms agreed for your project nor does it claim to provide legal advice.

For a website, the published terms expressly mention code and content. For an application, you should not extrapolate the answer by analogy. If you require ownership of the code, state it as a requirement in your inquiry. If what you need is to use a tool, clarify the terms of use you wish to review.

Proof of my own: what my published terms state

On my homepage, I explain that for websites, the code and content belong to the client. That is the verifiable claim of this article. I also explain that, for applications and other software developments, ownership or usage licensing is agreed on a project-by-project basis.

I do not add a universal inventory of materials you would receive here. An ownership clause alone does not enumerate what a specific delivery entails. To prepare the scope, it is best to separate what is already published from what we need to describe for your commission.

My process also specifies that we define the concrete deliverables, deadlines, and quote in writing before starting development. That is the practical link: your requirement for ownership or licensing must form part of a conversation about an identifiable project, rather than remaining hidden behind a commercial label.

Limits: when you should NOT take ownership for granted

You should not decide based on an ambiguous phrase like «the solution is yours» without knowing what it refers to. As a commissioning recommendation, I suggest requesting a description you can read alongside the scope. It does not mean there is a problem; it means you need an answer that fits your specific case.

Nor should you assume that maintenance includes any subsequent development. My PHP offering separates security updates, backups, and bug fixes from new features, which are quoted separately. That operational distinction does not automatically answer all questions regarding deliverables or contractual conditions.

If what you want is to change hosting, ask about hosting. If you need to modify a feature, describe the feature. These are related project matters, but an answer about ownership does not on its own address how they will be handled. Keeping questions separate makes it easier to agree on them without implicit promises.

What I would prepare before discussing the quote

I propose a decision checklist. This is supporting editorial guidance, neither a contract nor an additional feature already included:

Project objective
Describe which website, application, or existing tool you want to review.
Code requirement
Explain whether your requirement is full ownership or reviewing a usage licence.
Content
Identify what materials you expect to include and what must be clarified before starting.
Deliverables
List the concrete outcomes you want to be able to review when defining the scope.
Open questions
Highlight what you do not yet know; do not mark it as agreed simply from reading a general explanation.

When preparing your inquiry, indicate from the outset whether your business requires code ownership or a usage licence, and what concrete deliverables you expect to receive. You can bring both answers to the consultation to explain what is clear and what remains open, without treating them as a contractual acceptance.

If prior code exists, describe it as the starting point

If you already have a PHP/MySQL system running, my offering allows inquiring about its maintenance and evolution. To prepare for that conversation, I suggest indicating that an existing tool is in place and what changes you need, without sending me credentials or private data in the initial inquiry.

Do not assume that all existing code originates from the same commission or carries the same terms. This is a general technical precaution, not a claim about your application. If you need me to review a specific case, the available information and scope will need to allow for a concrete answer.

How I separate the ownership decision from the service choice

You may need a website to attract inquiries, an application for operations, or PHP maintenance. Choosing one of those paths helps contextualise your inquiry, but you should not use the price of a service as proof of what you will receive regarding the code.

I would start from your requirement and the project type to review the corresponding published terms. If anything remains undefined, I prefer to keep it as an open question rather than writing a universal answer not supported by the sources.

How we establish ownership or licensing before starting

When you send me your inquiry via the form, I reply within 24-48 business hours to assess your case. Before starting development, we define in writing the concrete deliverables, the applicable ownership or licensing framework, the timeframe, and the quote with VAT explicitly stated.

Thus, from day one you know what code and content you receive in ownership for a website (from €1,500 + VAT*) or what ownership or licensing terms we agree on for your custom application (from €3,500 + VAT*) or PHP maintenance (from €60/month + VAT*).

Frequently asked questions

Is the website yours?

Yes: for websites, my published terms state that the code and content belong to the client. That answer does not replace defining the concrete deliverables of the commission. Before starting development, we define the scope, deadlines, and quote in writing to establish what website we will build.

Do applications follow the same agreement?

No. For applications and other software developments, I agree on ownership or usage licensing with you on a project-by-project basis. I do not automatically transfer the terms published for websites to any tool. If you need to own the code, include that in your inquiry so we can expressly review that requirement alongside the project scope.

Web applications and PWAs

Web applications and PWAs

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Lead generation websites

Lead generation websites

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

PHP maintenance and evolution

PHP maintenance and evolution

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.