Reviews
A senior engineer reads one release, within a scope agreed in advance, and gives you a decision you can act on.
These are the stacks we can read well enough to give you a review worth paying for. If yours is not listed, ask — we will tell you honestly whether we can do it justice.
We would rather decline a review than give you a shallow one.
We aim to return eligible reviews within one working day, and we will tell you the expected time when you request one. A fixed service level will be published once we have enough operating history to commit to it.
You can hand the findings to your own AI, implement them yourself, or ask Progity to implement the fix. A reviewer does not automatically get the work of fixing a change they rejected.
Available in beta
Sometimes the honest answer is that a change needs a person to look at it.
