Simple and predictable pricing
Frequently asked questions
wispbit uses your specific, well-defined prompts for code reviews. Other tools use generic, catch-all prompts. We believe human-in-the-loop where you define the rules on how you want code to be reviewed works better.
Engineers are still conducting code reviews. Before your code makes it to a human for review, the change is ran against the rules you have set up. You can have engineers review code after all the rules have been satisfied.
A rule is a prompt that tells wispbit how code should be reviewed. This rule lives inside the codebase. Your team decides which rules make it into the codebase and which don't.
We charge a flat fee per seat. We can also discuss fixed or flat rate pricing. Please book a demo to learn more.
We use models that do not train on your data. We use cloud providers that are SOC 2 compliant. Your codebase is never retained on our servers.
Linter rules sound like the best solution, but most of the time they end up taking hours and maybe even days to get right. With this tool, you can decide on a rule as a team that will be applied to reviews within a few minutes.
We have a tool that can scan your codebase history and suggest some rules that would be useful to your team. During our white-glove onboarding service, we use this tool to help you come up with some rules if you don't have any in mind right away.
We are currently not SOC 2 compliant, but we are working on it.