You own the code
Everything we build for you, from source code to design files, belongs to your company, and this page explains how that works in practice.

When you hire an offshore team, one of the first questions is simple: who owns what we make together? The short answer is that you do. The work created for your project is yours, and the way we set up repositories and access is meant to make that obvious from the first day.
What ownership covers
Ownership is more than the final source code. For a typical project it includes:
- Application source code and configuration files
- Database schemas, migration scripts and seed data
- Design files, icons and style guides made for the project
- Documentation, test suites and deployment scripts
- Domain names, cloud accounts and app store listings
Open-source libraries are the exception. They stay under their own licences, which we note in the project so you know what is included.
Repositories that sit in your account
The simplest way to avoid confusion is to keep the code in your own space from the start. We work inside repositories hosted in your organisation on the platform you prefer, such as GitHub, GitLab or Bitbucket. Nothing important lives only on our machines.
The same applies to cloud hosting, CI pipelines, error tracking and other tools. Accounts are created under your name, and our developers are invited as members with the access they need.
How access is arranged
Access is given by role and removed when it is no longer needed. You stay the administrator, so you decide who can read, write or deploy. Shared secrets are kept in a password manager or secrets store rather than in chat or email. For more on how we handle sensitive material, see security and NDA.
Handover
Because the code is already in your account, handover is mostly about knowledge rather than files. At the end of a project, or whenever you change teams, we provide:
- A readme explaining how to run, test and deploy the project
- A list of services, accounts and environments in use
- Notes on key design decisions and known limitations
- A walkthrough session with your next developers if you want one
Checklist: confirm ownership at the start
Go through these points before the first sprint begins:
- The contract states that you own all work created for the project.
- Repositories are created in your organisation, with you as owner.
- Cloud, domain and store accounts are registered to your company.
- Each developer has a named account, not a shared login.
- Third-party and open-source components are listed with their licences.
- Design tools and file storage belong to you or are exported regularly.
- You know who to contact to add or remove access.
Where to go next
Ownership works best when it is agreed alongside the working model. Our guide to engagement models shows how different setups affect day-to-day control, and the how we work overview covers the rest. If you have a specific question about your project, get in touch.