What Happens If You
Stop Working With Us?
The biggest fear for founders: "If my developer leaves, my startup dies." We architect your project so you can fire us tomorrow and keep running.
100% Code Ownership
- ✓Your GitHub Repo: We create the repository under YOUR organization account, not ours.
- ✓Full History: You own every commit, branch, and pull request.
- ✓Revocable Access: You can remove us as contributors at any second.
Infrastructure Independence
- ✓Your Cloud Account: Improvements deployed to YOUR AWS/Vercel/GCP account.
- ✓Direct Billing: You pay the cloud provider directly. No markup, no hostage situations.
- ✓Standard Stack: We use industry standards (Next.js, Node, Postgres) that any developer can maintain.
The "Hit by a Bus" Protocol
We document as if we might disappear tomorrow. Every 2 weeks, we update these 3 critical files in your repo:
README.md
Instructions so clear a junior developer could clone the repo and get it running locally in under 15 minutes.
ARCHITECTURE.md
Explains WHY we made technical decisions, data models, and system diagrams. No "black box" logic.
DEPLOYMENT.md
Step-by-step guide to deploying to production. Credentials, environment variables, and rollback procedures.
Deployment Responsibility
Your infrastructure, your control
We deploy to your accounts. You have root access from day one. If we disappeared tomorrow, your deployments would continue working.
Your Cloud Account
All infrastructure runs in your Vercel/AWS/GCP account. You control billing, access, and regions. No shared infrastructure, no co-tenancy.
Root Access From Day 1
You have admin access to every service: database, hosting, CI/CD, monitoring. Our team has contributor access that you can revoke at any time.
Deployment Runbook
DEPLOYMENT.md in your repo: step-by-step production deploy, rollback procedure, environment variables, secrets management. A junior engineer could follow it.
Environment Documentation
Every API key, environment variable, and third-party integration documented. No tribal knowledge. No "ask the previous dev" situations.
Phase-Based Ownership
What you own at each stage
Ownership isn't something we hand over at the end. You own everything from the start — and the list grows with each sprint.