Need a capability that doesn't exist yet in an open source project you depend on? DepKeep engineers work directly with upstream maintainers to design, implement, and land the features your business needs — reducing long-term fork risk.
Forking and maintaining private patches is expensive and gets worse over time. DepKeep's upstream-first approach gets your features into the project itself — so the community maintains them for you.
We design solutions that align with upstream project goals, maximising the chance of acceptance and eliminating the need to maintain private forks.
DepKeep maintains active working relationships with hundreds of upstream maintainers — giving your feature requests genuine momentum inside the project.
Our engineers write code to the standards of the project — with full test coverage, documentation, and adherence to the project's contribution guidelines.
You follow the development through public pull requests and shared project boards. No black box — your team can review, learn from, and contribute to the work.
When upstream timelines don't match business needs, we deliver a private, production-hardened patch that can be merged upstream once accepted.
Features merged upstream are maintained by the community going forward — dramatically reducing the engineering cost of keeping your customisations alive across versions.
We translate your business requirement into a precise technical specification, validating scope, feasibility, and alignment with upstream project direction.
We open a design issue or RFC with the upstream maintainers, incorporating their feedback early to maximise the chance of a clean first-pass acceptance.
Our engineers implement the feature with full tests and documentation, iterate on maintainer feedback, and manage the code review process through to approval.
We deliver a production-ready private build for your use immediately, while the upstream merge process completes in the background.
Your workload hits a database or message broker bottleneck that requires a custom data path, index type, or protocol extension not yet in the upstream release.
Adding LDAP, SAML, or fine-grained RBAC support to open source tools that only have basic auth — contributed upstream so the whole community benefits.
Implementing structured audit logging in open source components to satisfy SOC 2, HIPAA, or financial compliance requirements.
Extending a messaging broker, API gateway, or data pipeline to support proprietary protocols, cloud provider APIs, or legacy enterprise systems.
Our engineers are active contributors across the open source ecosystem — not just readers of documentation.
Tell us which project you need enhanced and what capability your business requires. We'll assess upstream feasibility and come back with a plan.