metahead automatically synchronizes your repositories across your codebase and code hosts so dev teams can focus on engineering great software instead of fixing code. Start with as few as two repos, scale into the thousands.
No more disconnected code.
No more manual code synchronization.
No more downstream code breaks.
We promise to never spam you! By submitting this form, you confirm that you acknowledge the collection and processing of personal data by metahead, as further described in the Privacy Policy.
metahead combines all your code in one metarepo so that changes are instantly propagated across the entire codebase with feedback on the impact before you merge.
Designed to combine the best elements of monorepos and multirepos, metahead empowers organizations to build software sustainably, at scale, and with high velocity.
metarepos make large scale refactorings and changes possible. Code reuse is substantially improved, making it easier to maintain and change larger codebases.
Easier dependency management: one synchronized version. Atomic changes to complex dependency graphs are possible.
Flexible structure of code organization helps to prevent “silos”. There’s no need to coordinate changes across multiple repositories and code hosts, and no intermediate broken state.
metahead maximizes engineering flexibility, increases codebase transparency, and streamlines development processes. Ideal for engineering teams who want to take back control.
Make changes atomically across repos by connecting your favourite code forge and aggregates CI results, giving you a clear view of the impact of your changes. Once you’re satisfied, you can let metahead update all relevant repos with your new code.
Maintaining an open-source library as part of your proprietary codebase? You can use metahead to publish and synchronise part of your code in its own public repo. Accept external contributions and check them against your internal usage of the library. You have the choice to make as much or as little as you want public, with file-granularity filters.
Moving code to a new repository is as easy as creating a new view containing what you need. Keep the old one in sync, or use metahead to refactor it out. The choices of repos you made a long time ago don’t pin you down anymore.
metahead offers a GraphQL API allowing you to query information about your codebase, such as the SHA of a subset of your files. This can be used to optimise your CI, triggering builds only when needed. You can also get rid of side effects by allowing it to check out exactly what is needed to build, and nothing more.
By creating views tailored to developers use-cases, you can make working with your codebase easier and faster. Only check-out what you want to see, nothing more.
With metahead, you can merge multiple PRs atomically. metahead acts as the source of truth, and all of the related commits will translate to one commit in the metarepo. No need to worry about the complexity of merging wide-reaching changes anymore.
metahead helps dev teams focus on building quality software instead of spending countless hours making the simplest changes.
The way metahead approaches source code management is unlike anything I have seen before. To me, metarepos are extremely promising if you want to achieve maximum control and development velocity.
The technology powering metahead has already helped esr_labs develop software faster and with more control. I am excited for metahead to bring this tech to the masses.
metahead looks to be the most promising approach to combining the productivity of monorepos with the flexibility of multirepos.
metahead is a tool which provides a new way to store and work on code. It allows you to combine all of your code in a metarepo, which can be used to synchronize together related repositories.
metahead is powered by our open source git history transformation engine called josh. It takes full advantage of the git data model, and uses a range of techniques to achieve great performance.
The metarepo is a repo of repos. It is where all of your repositories get synced. It can be sliced any way you want, to produce views adapted to what you need.
A projection is a view of the metarepo which includes the code of a selected number of components, as well as their history. It is what metahead syncs out to the external code hosts. For example, a projection related to an application could contain the application code, as well as the libraries it uses, and the relevant history.
While it can be used like a monorepo, metahead’s metarepo is more flexible as it enables a mixed approach where code that has been synced to the metarepo can still be used as its own repository. metahead also enables the creation of synced repos on the fly, containing exactly what is required. For example, you could have one big repository per application, with the code of all libraries contained and shared between those repositories.
For now, metahead works with github. We are working on adding support for more platforms.
Yes, with metahead you can atomically produce commits across a range of repositories. This can be used to upgrade correlated microservices, or atomically upgrade an API used in multiple places.
No, metahead works with git. It produces views which are fully-fledged git repositories. Use all of your usual tooling for building and deploying code.
If you’re using git submodules, metahead can enable big improvements to your workflow. The usual loop with submodules is to make a commit in a submodule, then to update the repos containing the submodule. By replacing submodules with metahead, you can make the code truly part of all the repos using the module, and a commit to the module repository will be seamlessly synchronized to all the users of this module. With one PR, update all the repos which use this code.
metahead triggers the CI of all your synced repositories, and collects the results in the PR you’re opening. This way, you have direct feedback on the impact of your change. When you merge, you know your change will not break any of its users.
Today, you can set up standard repository-level access control using github settings. We are working on ACL (Access Control Lists) support for metahead. Using the josh filtering technology, this will provide you with file-level granularity access control.
Metahead only impacts the way your code is stored and updated. It connects and triggers your Continuous Integration pipelines, but building the code can be done as before.
metahead allows you to integrate the code of your dependencies directly in the repositories where they are used. It keeps the code in sync between all of the dependencies repositories and the users of them.
It depends on the way you are currently building code. In most cases, it’s a matter of pointing to a local checkout of the dependencies rather than a remote repository.
Yes! metahead provides a GraphQL API which can tell you the SHAs of any subpart of your repositories. This can be integrated in your CI to only rebuild what’s strictly necessary. What’s more, when you open a PR to a synced repository, metahead will only trigger the CI of relevant repositories which are impacted by this change.
We promise to never spam you! By submitting this form, you confirm that you acknowledge the collection and processing of personal data by metahead, as further described in the Privacy Policy.
