Skip to content

AI code review by a council that never marks its own work.

Studio Northstar in The Hague reviews code with a specialist council from ARCS, our agentic platform. One model reviews the code, another checks the findings, and you get every finding with the check it rests on.

Request a code review

We reply within three working days.

Three kinds of review

You choose what the council looks at. We write it down before the review starts.

  • Security

    A council with security as its specialism reviews your code for security risks.

  • Legacy software

    We assess older software: what is there, what still holds and where the risk sits before you build on it.

  • Preparing for an audit

    We check a delivery that has to survive an audit, before the auditor arrives.

How the council works

Ask a model to check its own work and it agrees with itself. So the reviewing and the checking are done by different models.

  1. Scope

    We write down which code we review, for which kind of risk, and when the review counts as done.

  2. Review

    A council from ARCS with the right specialism reviews the code and writes down its findings.

  3. Check

    A different model checks every finding, and a correction is checked again.

  4. Deliver

    You get a report with every finding and the check it rests on. Every run keeps a checkpoint, so you can trace how a finding came about.

Confidential code stays in-house

When your code may not go to an outside AI provider, the review runs on Northstar One: our own machines with models we host ourselves, reachable over a private network only. Where the review runs is agreed in advance.

About Northstar One

Our own code goes through the same councils

Every one of our products is reviewed with ARCS. The same councils review your code.

  • ARCS

    Seventeen specialist councils, covering strategy, codebase, security, production readiness and more.

    See ARCS
  • Forenta

    Turns an idea, plan or existing codebase into a reviewed product route, with the assumptions and risks made explicit first.

    See Forenta
  • Plens

    Route-aware rain advice for cyclists, runners and walkers, built and reviewed with ARCS.

    See Plens

Questions we get.

What is an AI code review?

In an AI code review, AI models assess your code for risks and errors. With us, a specialist council from ARCS does that, a different model checks every finding, and you get the findings with the checks they rest on.

Is an AI code review reliable enough for an audit?

A review does not replace the audit; it prepares you for it. Because every finding comes with the check behind it, your team and your auditor can see what it rests on. What the audit asks for is written down before we start.

Does our code go to an outside AI provider?

Where the review runs is chosen in advance and recorded. When your code may not go to an outside provider, the review runs on Northstar One, our own machines on a private network that is not reachable from the public internet.

What does an AI code review cost?

That depends on the size of the code and the kind of review, so we name no amount here. After the first conversation we write down your goal and what counts as done in a brief. We reply to your request within three working days.

How is this different from a code review tool in your pull requests?

Such a tool looks at every change as it comes in. We review the code as a whole, against a question written down in advance, such as security or an audit. A different model checks every finding, and you get a report with the checks behind it.

Put a council on your codebase.

We reply within three working days. After the first conversation we write down which code we review, for what, and when the review is done.

Request a code review