1. Our commitment
We don't believe in technical lock-in. When you pay us to build something, the result is yours. This document explains exactly how ownership works — both what you receive, and the small set of things that remain ours so we can keep operating.
2. Custom code (you own it)
All code, designs, configurations, and other materials we create specifically for your project under a signed Statement of Work are assigned to you upon full payment of fees due under that SOW. You own:
- Application source code written for your project.
- UI and design assets created for your project.
- Database schemas, migrations, and seed scripts.
- Infrastructure-as-code definitions specific to your deployment.
- Project-specific documentation and diagrams.
You are free to modify, distribute, sublicense, sell, or open-source these materials however you see fit. We claim no ongoing rights over your custom code, except as set out below.
Portfolio & marketing rights. Notwithstanding your ownership of the custom code, we retain a non-exclusive, perpetual, royalty-free right to reference your engagement — including the project name, a high-level description of the work, screenshots of public-facing surfaces, and outcomes achieved — in our portfolio, case studies, presentations, proposals, and marketing materials. We will respect any reasonable confidentiality requirements specifically agreed in writing in the SOW. Public-facing material that is already available to the general public is not subject to confidentiality.
3. Pre-existing materials
Some things we bring to the table are not created for any single project — internal utilities, generators, code patterns, and methodology we've developed across our practice. These remain our property ("Pre-Existing Materials").
To the extent Pre-Existing Materials are incorporated into your deliverables, we grant you a perpetual, worldwide, non-exclusive, royalty-free, sublicensable license to use, modify, and distribute them as part of your deliverables. In practice this means: if our code is in your codebase, you can do anything with that codebase, forever, with no further payment to us.
What we do not grant: the right to repackage and sell Pre-Existing Materials standalone (i.e., extracted from your project and resold as a product).
4. Open-source components
Modern software is built on open-source. Your project will include OSS dependencies. Their use is governed by their respective licenses (MIT, Apache 2.0, BSD, ISC, etc.). We make reasonable efforts to:
- Choose dependencies with permissive licenses suitable for commercial use.
- Document the OSS components used and their licenses.
- Avoid copyleft licenses (GPL, AGPL) unless explicitly approved by you.
You are responsible for license compliance once the project is in your hands (e.g., including required attribution in your application).
5. Third-party libraries & SaaS
Some projects integrate paid third-party libraries or SaaS services (analytics, payment processors, mapping APIs, etc.). Their use is governed by the third-party's terms. Where possible, accounts and licenses are registered in your name and billed to you directly. If we register on your behalf during development, ownership is transferred to you at handover.
6. Source delivery
At project handover, you receive:
- Full source code in a Git repository under your control (typically GitHub, GitLab, or a self-hosted instance you specify).
- Complete commit history during the engagement.
- All build, deployment, and configuration artifacts needed to operate the system.
- A handover document covering architecture, environment variables, deployment steps, and any operational notes.
7. Documentation
Documentation produced for your project — including diagrams, runbooks, architectural notes, and API references — is yours under the same terms as the source code.
8. IP warranties
We warrant that, to the best of our knowledge, the custom code we deliver does not infringe third-party intellectual property rights. We will defend you against third-party IP-infringement claims relating to our custom code, subject to prompt notice and reasonable cooperation, and the limits in our Master Services Agreement.
You warrant that materials you provide to us (logos, content, data, designs) do not infringe third-party rights, and you will defend us against claims arising from those materials.
9. Questions
For specific questions about IP terms in your engagement, email wava2980@gmail.com.