Now launching · source control for Boomi

Source control discipline,
built for Boomi.

Weave gives your integration team branches, visual diffs, reviewed pull requests and AI assistance over Boomi — without changing how anyone builds on the canvas.

Free to put your projects under source control. Pay only for the AI tokens you use.

Built for Boomi integration teams Branches & commits Visual diffs Pull requests Automated review Ask AI Full audit trail

Version control and review, made for Boomi

Weave brings the version-control workflow your developers already know from code to your Boomi projects. Every change is captured, comparable, and reviewable before it ships — while the team keeps building right on the Boomi canvas.

01

Version every change

Branches, commits, tags and rollback for your Boomi folder. A content-addressed store keeps year-old comparisons instant — no Boomi API calls to look back in time.

02

Review before merge

Component-level visual diffs and rule-based code review on every pull request. Critical findings block the merge until they are resolved or an owner overrides them.

03

AI that proposes, never applies

Ask AI about any process, and let it draft changes. Every AI write is staged in an approval queue and applied only after a human approves it — fully audited.

Your canvas, plus a real repository

Git separates the working tree you edit from the repository where history lives. Weave makes the same split for Boomi: developers keep building on the canvas, while Weave holds the branches, commits, diffs and audit trail beside it.

Boomi Build canvas The working copy — where developers edit, as before. live Weave repository Branches · commits · tags Pull requests · diffs · audit instant · offline diffs commit · snapshot write to Boomi preview first
import manual commit auto checkpoint safety commit merge (pull request) cherry-pick

Everything a Boomi team needs to ship with confidence

Version control

Branches, commits and rollback for Boomi

Snapshot the whole folder as an immutable commit, branch instantly, tag releases, and roll back when something breaks. Every commit records its kind, so history reads at a glance.

  • Instant branches, tags and cherry-picks — all local to Weave
  • Content-addressed store: compare any two points in time instantly
  • Works alongside Boomi's own branches
history — main
8f2a1cMerge PR #12 — orders revampv1.2
3b9d77Add retry around Salesforce call
c1740aCherry-pick: null-guard in mapping
a1c4e0Automatic checkpoint
0095e1Initial import from Boomi
Visual diff

Diffs that read like the process, not the XML

The diff viewer adapts to the component type. Processes diff on the canvas with changed shapes highlighted in place; maps diff semantically as mapping changes; everything else falls back to a clean side-by-side XML view.

  • Process diffs classify added, deleted, rewired and config-changed shapes
  • Semantic map diffs — added, removed and remapped fields
  • Position-only moves never count as changes
Order_Sync — v4 → v5
Start Map Decision Notify
6 added 3 changed 1 removed
Pull requests & review

Reviewed, confident merges

Open a pull request between two branches and get a live diff, conflict resolution and comments. Rule-based review runs automatically on every changed process — built-in whole-graph checks plus custom JavaScript rules you write per organization.

  • Automated review gates merges on critical findings
  • Starter rule library installs in one click, then edits like your own
  • Merging writes a commit; Boomi only changes on an explicit checkout
Pull request #12
feature/orders main 1 critical — blocking
Naming convention — passed on 6 processes
Error handling present — passed
Orphaned branch in  Route_Order — must resolve
Ask AI

Ask anything about any process

Every process gets an Ask AI workspace backed by a knowledge graph of the components it touches. The model receives the parsed structure — shapes, connections, scripts, referenced maps and profiles — so answers cite real step names instead of guessing.

  • Grounded in the actual process graph, not a guess
  • Keep sensitive processes on a local model
Claude Gemini Ollama · local MiniMax GitHub Models
Ask AI — Order_Sync
Process Map Profile Connection Subprocess
Where are errors handled in this process?
Errors route through the Try/Catch around the Salesforce send; failures hit the Notify step and return via the Return Errors path.
Agent changes

A pull request for every AI write

When the AI proposes a component change, a new component, or a deployment, the proposal is staged — never applied. An admin reviews the full diff and approves or rejects it; applying is a separate, deliberate step, and every transition is recorded in the audit log.

  • Nothing reaches Boomi without an explicit approve-then-apply
  • Component-level guardrails for AI-initiated writes
Agent changes — queue
Update map: add retry flag staged · not applied
<operation name="Send">
- <retry max="0" />
+ <retry max="3" backoff="2s" />
</operation>

One loop your team already trusts

The same edit, commit, review and merge cycle your developers already know from code — now running across your Boomi projects.

01
Edit in BoomiBuild on the canvas, exactly as before
02
CommitSnapshot the folder in Weave
03
ReviewDiffs and rules gate the merge
04
Merge & write backPush the reviewed result to Boomi

Questions, answered

Do we have to change how we build in Boomi?
No. Developers keep editing on the Boomi Build canvas exactly as before. Weave records history beside it — committing never changes the canvas, and writing a branch back to Boomi is always an explicit, previewed action.
Does Weave write to my Boomi tenant automatically?
Never automatically. Writes to Boomi are explicit and preview only the components that differ. AI-proposed writes are staged in an approval queue and applied only after a human approves them — every step is audited.
What is included in the free tier?
All of source control: projects, branches, commits, tags, rollback, visual diffs, pull requests and rule-based review. Ask AI works on the free tier too when you bring your own provider key or run a local Ollama model.
How does AI billing work?
Hosted AI features are pay-as-you-go, metered by token usage and billed monthly — no seats, no minimums. You only pay when you use hosted Ask AI or agent proposals. Bring your own key and you pay $0 to Weave for AI.
Which AI providers are supported?
Anthropic Claude, Google Gemini, a local Ollama instance, MiniMax and GitHub Models — selectable per conversation, so sensitive processes can stay on a local model.
Can several teams share one Boomi tenant?
Yes. Each project is anchored to one Boomi branch and folder subtree, scoped per team with per-organization roles and isolation, so teams work independently in the same tenant.
How do we get started?
Sign in, connect your Boomi account, and create a project — your first commit is the current folder snapshot. Existing projects convert their branch history into commits in one step.

Ship Boomi changes with confidence.

Visual diffs, automated reviews and full version control — for the way your team already builds in Boomi. Tell us about your team and we'll be in touch.

Rejoining the server...

Rejoin failed... trying again in seconds.

Connection lost.
We'll restore your session as soon as you're back online.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.