Handover, Ownership & Support

Full access to the complete source code repository transferred to you — including the complete version history, all branches and all documentation in the repository. You own the code from the first commit, and at handover it is cleanly organised, documented and ready for any developer to continue working on.

• Repository transferred to client-owned GitHub or GitLab account
• Complete version history included
• README and setup instructions included
• Code reviewed and cleaned before handover
• All branches and tags properly organised
• Any temporary or development scaffolding removed

All intellectual property rights in the code, design and documentation created for your project are formally transferred to you upon final payment — as documented in the project contract. You own what was built for you; we retain no licence to use it for other clients.

• IP transfer documented in the project contract
• All custom code owned by client upon final payment
• No licence back to StringLogix for other use
• Open-source component licences documented
• Third-party library and dependency licences listed
• IP transfer confirmation in writing at handover

Every credential, API key, hosting account, domain account and third-party service login handed over securely and completely documented — so your team has full control of every service the system depends on, with no hidden dependencies on our accounts.

• Hosting and server access credentials
• Database access credentials
• API keys for all third-party services
• Domain and DNS management access
• Email service and SMTP credentials
• CI/CD and deployment tool access
• Credentials delivered via secure password manager or transfer method
• Credential inventory document provided

Comprehensive documentation covering the system architecture, database structure, deployment process, environment configuration, maintenance tasks and known operational considerations — so any competent developer can work on the system without needing to ask us how it works.

• System architecture overview document
• Database schema and data model documentation
• Deployment and environment setup guide
• Environment variable and configuration reference
• Cron jobs, scheduled tasks and background process documentation
• Third-party integration reference (endpoints, auth, data mapping)
• Known limitations and future development notes
• Operational runbook for common maintenance tasks

Training sessions for the team members who will manage and use the system — covering administration, day-to-day use, content management and any operational tasks. Training is practical, conducted in the live system, and followed up with recorded sessions or written guides.

• Admin and system management training
• End-user training for operational staff
• Content management and update guidance
• Recorded training sessions for future reference
• Written user guide per role where appropriate
• Q&A session and post-training support period

A defined post-delivery warranty period covering defects in the delivered system — plus clear options for ongoing support, maintenance and feature development after the warranty period ends. You are never left with a system and no one to call.

• Warranty period for defects in delivered scope
• Defect vs new feature distinction documented
• Monthly maintenance retainer option
• Priority support agreement option
• Feature development engagement available post-handover
• Security patch and dependency update service available
• Response time commitments documented
• Long-term relationship — not a one-off transaction