terms.

01using this site

The content here — service pages, case studies, cost studies and benchmarks — is published for information. We keep it accurate and we correct it when it is wrong, but it is provided as-is and without warranty.

You are welcome to quote or reference our writing with attribution and a link. Republishing whole articles is not permitted.

02engagement terms

Nothing on this site is an offer or a contract. Work is agreed per project in a written scope of work that sets out what is being built, what it costs, what each side is responsible for, and how either side can end it.

Where a scope of work and this page disagree, the scope of work wins. It is the document both parties signed.

03ownership of the work

You own the code we write for you, along with the repository, cloud accounts and keys it lives in. That is true from day one of the engagement rather than on final payment.

Open-source components keep their own licences, and any third-party service the system depends on keeps its own terms. We name those in the scope so there are no surprises later.

04figures and case studies

The numbers we publish — processed volume, Core Web Vitals scores, engagement lengths — come from real production systems, and are shared with the agreement of the clients involved.

They describe what happened on those projects. They are not a forecast of what will happen on yours, and we will not pretend otherwise on a call.

05liability

To the extent the law allows, we are not liable for loss arising from your use of this website or from reliance on the general information published on it.

Liability in respect of work we are engaged to do is dealt with in the scope of work for that engagement, where it can be set against what is actually being built.

06questions

If you are reviewing Appycodes as a supplier and need our engagement terms or further information, write to hello@appycodes.com.