How we work
Your GitHub. Our infrastructure. Your code.
Every client project lives in your GitHub organization from day one. We work in our infrastructure during development, then transfer everything to you when we are done. You never lose access to your own code.
The process
How client projects work.
Three phases. At each step, the code lives in your GitHub.
Set up your repository
You create a GitHub organization or repository for your project. We do not require you to use ours. If you prefer to keep everything under your own account from the start, we can work that way too.
You own the repo from day one. We get added as collaborators or you grant us access to a dedicated team.
We build in our infrastructure
During development, we work in our own cloud environment connected to your repository. Code is committed to your repo as we go and not held in a private ByteWorthy repo until the end.
Pull requests, code reviews, and CI/CD run against your repository. You can follow every change as it happens.
Transfer when we are done
When the project is complete, you own the full repository, all infrastructure configuration, deployment pipelines, and documentation. We provide a transition handoff with everything another developer needs to continue.
No lock-in. No exit fees. If you decide to stop working with us, you keep everything and can hire any developer to continue.
At handover
What you get when we are done.
More than code. A complete system that a developer can pick up and run with.
Full repository access
Your GitHub repo with complete commit history, all branches, and documentation. Any developer can clone it and continue.
Deployment documentation
Step-by-step guides for deploying to your own cloud account, setting up CI/CD, and managing the system without us.
Security configuration
All environment variables, secrets configuration, and security settings documented so you control access permanently.
Architecture decision records
Why we made the technical choices we did, what alternatives we considered, and what to consider before major changes.
Common questions
Questions about this model.
If you have more, send us a message.
What if I already have a GitHub org?
No problem. We can work within your existing organization. You add us as a team member or outside collaborator. We never require you to create a new org.
Can I see the code while you are building?
Yes. Every feature branch is a pull request against your repository. You can review code, comment on it, and see exactly what is being built as it happens.
What if I want to stop working together before the project is done?
You own the code. You can stop at any time. We will hand over everything in its current state with documentation on what was done and what remains.
Do you offer ongoing hosting?
We can continue to host and maintain your project after the initial build. This is a separate retainer arrangement. You are never required to continue hosting with us.
What about open source components?
Any open source components we use are attributed and licensed correctly. If the project includes code we want to open source ourselves (with your permission), we discuss that separately.