OpenTremor

Product tour · IT director / CTO

Your standards applied to every product, at a cost you control, where you choose to run it.

See how goals and standards are checked on every pull request and on the code you already have, then how the cost is capped.

The product tour for your role: PDF·PowerPoint

Engineering director

Track an engineering goal across pull requests

As an engineering director, I want to know if our changes move us toward our goals, not only if they fix single issues.

Goals like customer data isolation or a migration live in a slide deck. Nobody knows the real progress, and nobody sees when a pull request makes it worse.

What to notice

  • A measured step is done when its rules have no open findings left in the product.
  • One pull request never completes the goal by itself. A step is done when its count reaches zero, or when a person marks it as done.

Step 1 of 4

An engineering director sets a goal, with a step OpenTremor can measure.

The goal "Tenant isolation everywhere" has a step that OpenTremor measures: the number of open findings for one rule. A scan found one.

Do it yourself: the step-by-step guide

Platform engineer

Find problems already in your code

As a platform engineer, I want to check an existing repository against our standards, so I can find its problems before they cause an incident.

Pull request review sees only the changed code. Nobody checks the older code, so nobody knows how much of it breaks the rules.

What to notice

  • A scan never blocks a pull request. It only shows the current state of the code.
  • OpenTremor never sends the same code to the AI model twice.

Step 1 of 3

A platform engineer scans the code already on the default branch.

The repository's Scan tab shows what a scan will check. One click scans the main branch.

Do it yourself: the step-by-step guide

Tech lead

Every pull request checked against your team's rules

As a tech lead, I want every pull request checked against our written standards, so reviewers stop repeating the same comments.

Your standards are in a wiki and in people's heads. A pull request follows them only if the reviewer knows them and has time.

What to notice

  • The rule is your team's own, written in plain words. You do not need a special rule language.
  • The finding explains the risk, not only the line of code.
  • The fix is a normal GitHub suggestion. OpenTremor never commits code for you.

Step 1 of 5

A developer opens a pull request.

The pull request adds a list of invoices. Its database query returns the invoices of all customers, not only the caller's.

Do it yourself: the step-by-step guide

Finance lead

Know what AI review costs, and cap it

As a finance lead, I want to cap what AI review costs each month and choose where the model runs, so the bill holds no surprise.

AI tools bill per use. Without a cap, a busy month or a runaway script shows up only on the invoice.

What to notice

  • A hosted provider bills you directly, on your own key. A self-hosted model keeps the code on your network.
  • The cap counts every model call, at the price the platform admin sets for each model.
  • The cap is checked before a review starts: one already running finishes, so a month can end a little over.

Step 1 of 5

Choose where the model runs: a provider with your own key, or a model on your own network.

Two connections: a hosted provider on the company's own key, and a model on the company's network. A test call checks that it answers.

Do it yourself: the step-by-step guide

Try it on your own pull requests.

Connect a repository, write one rule, and open a pull request.

See all the stories