Skip to content
HAZEL'S AGENTS/Elevate AI

Agents as a Service

Your repo.
Your review.
Your merge.

An extra pair of hands inside your own codebase, built to add the integrations you don't have yet. It writes the connection to a new vendor or system, and keeps the ones you already run working. Your engineers review and merge every line.

Built by Elevate AI
github.com/acme-corp/checkout-integrations/pull/482
$ ci run --pipeline integration-update
install dependencies
lint
type-check
unit tests · 214 passed
integration tests · vendor-api-v3
build
deploy → staging
→ PR #482 ready for review

What is Hazel?

Add what's new. Keep what's already running.

Every new vendor, payment method or system your team wants to add costs engineering time most roadmaps don't have, so it gets deprioritised in favour of what you already have wired up. Hazel's Agents builds the new integration directly in your codebase. It can also maintain the ones you already run, so an API change doesn't turn into unplanned work later.

A new system or tool you want to add
An API you already depend on
A new regulatory requirement lands, and every integration underneath it has to follow
Hazel's Agents adds the integrations you don't have yet, and keeps the ones you do have working. It's added capacity for your integration team, and nothing reaches your main branch without one of your engineers approving it.

How Hazel works

Built to work the way your engineers already do.

Hazel's Agents doesn't sit outside your codebase. It works inside it, in your own repository, in the same CI/CD pipeline your team already runs, whether it's building something new or keeping something you already have working.

01

It builds the integration you need

Point it at a new vendor or system and it writes the integration directly in your codebase, following your existing conventions and tests.

02

It opens a pull request

The agent opens a pull request the same way one of your own engineers would, whether it's a new integration or an update to one you already have.

03

Your engineers review and merge it

Every change goes through the review process you already have. Your team decides what merges into your main branch. The agent never merges anything itself.

04

It can maintain what you already have

The same agent that builds a new integration can also maintain the ones you already run, proposing an update when one needs it.

Not the same as OneHazel

OneHazel uses the same underlying Hazel agent, in a different shape, for teams who'd rather integration wasn't their problem at all. It carries the work for you instead of working inside your own repository.

Hazel's Agents is for teams who want to keep owning their integration code, with that same agent working inside it.

Find your fit

Four questions, and we'll point you at the right one.

We have two products for two different ways of working. Answer four quick questions and we'll point you to the one that fits, Hazel's Agents or OneHazel.

An estimate is fine, and this stays in your browser.

Waiting on you

Four to go.

Answer all four and we'll tell you which product fits, and why.

Ready to see it against your own repo?

Book a call