Start for free today

Promyze has no limit in the set of practices that can be defined. Linters won't be able to identify most of them. Promyze is, therefore, complementary to these tools.

We support all programming languages.

Technical rituals are sometimes complex to organize and lead. Promyze supports these workshops to allow developers to daily identify discussion topics that will be addressed during the workshop retrospective.

Wikis are challenging to maintain and rarely the result of a collaborative team effort. The examples are often theoretical and difficult to apply in the context of the teams. With Promyze, the repository of practices evolves every week according to the topics discussed during development. The examples are taken directly from the source code on which the team is working. Moreover, the team built this repository, facilitating its application and making each person an actor.

Even if pair / mob programming sessions allow knowledge sharing, it is crucial to capitalize on the best practices implemented during these sessions by catching them within Promyze. If the team changes, onboarding will be more efficient. Promyze also allows sharing those practices with other teams.

We recommend organizing a 1-hour workshop at least once per month.

Getting started is fast, just create your account, get one of our plugins, and create your first best practices!

You’ll need Docker to deploy Promyze by yourself.

Promyze allows teams to build a repository of best practices, which can be used during code reviews, thanks to the Promyze code review plugin. During a code review, comments target a single team member and will be lost when the pull request will be closed. Promyze allows teams to capitalize on technical exchanges during Craft Workshops. A collective appropriation of practices will reduce the time spent during code reviews on these subjects.