You paid for custom software. But do you actually own it?
Ownership isn't just about having access. It's about control, independence, and the ability to do what you want with what you built.
Here's how to verify you truly own your software.
Code Ownership
✅ Source Code Access
Do you have access to the complete source code?
- Not just "we'll give it to you if you ask"
- In a repository you control
- Current and complete
Test: Can you log in and download the code right now?
✅ Full Repository History
Not just the final files, but the complete Git history.
- Shows how the code evolved
- Enables understanding of changes
- Useful for troubleshooting
Test: Is there commit history, or just a single code dump?
✅ IP Ownership Documented
Does your contract clearly state you own all intellectual property?
- Work-for-hire language
- Transfer of ownership upon payment
- No retained licenses by vendor
Test: Read your contract. What does it say about IP?
✅ No Proprietary Dependencies
Is the code built on standard, open technology?
- No proprietary frameworks
- No vendor-specific libraries
- Standard, well-supported tools
Test: Could another qualified developer work on this code?
Infrastructure Control
✅ Hosting Account Ownership
Do you own the hosting account?
- AWS, GCP, Azure, or other provider
- Account in your name
- Your credit card on file
- Your admin access
Test: Can you log in to the hosting provider as the account owner?
✅ Database Access
Do you have direct database access?
- Admin credentials
- Ability to query and export data
- Backup access
Test: Can you connect to your database right now?
✅ Domain Ownership
Do you own your domain?
- Registered in your name
- Control panel access
- Able to point DNS anywhere
Test: Log in to your domain registrar. Is it your account?
✅ SSL Certificates
Who controls your security certificates?
- Certificates in your name
- Ability to renew
- Private keys accessible
Test: Could you renew your SSL certificate without help?
Third-Party Services
✅ Payment Processor
Is your payment processor account yours?
- Stripe, Square, PayPal, etc.
- Account in your business name
- Funds depositing to your account
- You control API keys
Test: Log in to your payment dashboard. Is it your account?
✅ Email Service
Who controls your email infrastructure?
- SendGrid, Mailchimp, SES, etc.
- Account ownership
- API key control
- Sending domain verification
Test: Could you switch email providers without vendor help?
✅ Analytics
Do you own your analytics data?
- Google Analytics or similar
- Account in your name
- Historical data accessible
- Not dependent on vendor
Test: Can you see all historical analytics without vendor?
✅ Other Services
Review all integrated services:
- Mapping (Google Maps API)
- SMS (Twilio)
- File storage (S3)
- Search (Algolia)
- Any other APIs
For each: Is the account yours?
Knowledge Assets
✅ Documentation
Do you have complete documentation?
- Technical documentation
- User guides
- Admin procedures
- API documentation
Test: Could a new developer understand the system from documentation alone?
✅ Design Assets
Do you have source design files?
- Logo (vector format)
- Design system
- Figma/Sketch files
- Icons and images
Test: Could a designer make changes without starting over?
✅ Credentials List
Do you have all credentials documented?
- Every login
- Every API key
- Every access token
- Stored securely
Test: If vendor disappeared tomorrow, could you access everything?
Operational Independence
✅ Deployment Knowledge
Can you deploy updates without the vendor?
- Deployment procedures documented
- Access to deployment tools
- Someone trained to do it (you or your team)
Test: Could you push an update yourself?
✅ Monitoring Access
Do you have visibility into system health?
- Server monitoring
- Error tracking
- Performance metrics
- Not dependent on vendor dashboard
Test: Would you know if your system was down without being told?
✅ Backup Access
Can you restore from backup?
- Backup locations known
- Ability to download backups
- Tested restore procedure
Test: Could you restore your system from backup?
The Independence Test
Ultimate test of ownership:
If your vendor disappeared tomorrow:
- Could you keep the system running?
- Could you make changes?
- Could you hire someone else to work on it?
- Would you have access to everything?
If any answer is "no," you don't truly own your software — you're dependent.
Getting to Ownership
If you're missing items on this checklist:
- Request what you're missing — Most vendors will provide
- Document the request — In writing
- Verify receipt — Actually check access
- Test it — Make sure it works
- Establish ongoing practice — Don't let it lapse
For Future Projects
Include ownership requirements in your contract:
- Complete source code delivery
- Infrastructure in your accounts
- Documentation included
- All credentials transferred
- Handoff checklist completed
Make ownership explicit from the start.
We build for your independence. Let's talk about your project