Source Code and Accounts
Who owns the source code, domain, and server after project completion?
Source code delivery, software copyright, domain name registrant, and server account are separate matters requiring individual confirmation. We recommend clients hold their own business accounts, with developers granted necessary authorizations only. Custom source code and related rights are transferred per written agreement.
What to verify upon receiving source code
Confirm exactly which components are delivered: frontend pages, mobile clients, backend APIs, database schema—or subsets thereof. Also verify version, dependencies, sample configurations, and build instructions to assess maintainability in the agreed environment.
A runnable installer package and full project source code are not equivalent deliverables. When commercial components, fonts, or images are involved, their license scope and future costs must also be clarified.
Source code delivery and copyright ownership must be separately agreed.
Article 11 of the Regulations on the Protection of Computer Software stipulates that copyright for commissioned software is determined by written contract; absent such a contract or if terms are unclear, copyright belongs to the developer. Therefore, payment or receipt of source code alone does not substitute for explicit rights agreements.
During collaboration, separately confirm rights and usage conditions for custom code, pre-existing code, and third-party components. This article outlines general handover principles—actual projects require verification against contracts and licenses.
Domain name and server registrants must be verifiable.
We recommend clients register domains and cloud services under their own legal entity and accounts, granting developers authorization only as needed for implementation. Verify real-name registration, contacts, renewal dates, and billing ownership—and retain relevant records during handover.
If using the developer’s hosting environment, agree in advance on data export, backup, migration methods and costs, and procedures upon service termination. Hosting does not equate to ownership of cloud accounts or physical infrastructure.
How platform accounts and credentials are handed over
For mini-programs, app stores, and payment platform accounts, verify registrant identity and administrator roles separately. Development permissions and legal identity are distinct—identity verification is performed by the account holder, and authorization should cover only required implementation tasks.
Exchange configurations and credentials via mutually confirmed secure channels. Confirm whether temporary authorizations remain necessary. Never embed passwords, private keys, or API keys in public source code, articles, or demo visuals.
Ready-to-use handover verification checklist
Verify the source code version against the file list; validate build or deployment per instructions; check database schema and convention-based data exports; confirm third-party licenses; verify domain names, cloud and platform accounts; validate backup and recovery responsibilities; document maintenance contacts and handover date.
Shuotang Network will clearly specify the deliverables—including source code, design assets, and deployment documentation—based on the selected service package; the exact scope is defined in writing prior to project commencement. If the client intends to maintain the system internally or hand it over to another team later, this must be communicated during the requirements phase.
Reference basis (verification date: 2026-11-21)
Article 11 of the Regulations on the Protection of Computer Software · National Administrative Regulations DatabaseNeed project-specific evaluation?
View corresponding development services and delivery scope