Where our guardrails come from · Amazon advertising
Auren is a separate product our founder built to run Amazon advertising with AI. Every morning it pulls each account’s data and proposes changes, and a person approves them before a single writer applies them. Unison carries the same discipline into every platform it connects.
Auren runs Alumenza’s Amazon ads. Its site publishes Alumenza’s July to September as a 90-day challenge; the Alumenza page has April to September.
The owner’s words, typos fixed. Times are Eastern.
…what is happening with alumenza ppc, it isn’t going well
Ten agents audited the account and the code. Fixes were tested on a separate copy, and an independent reviewer’s 8 findings were fixed before anything was proposed.
let’s do these
A validate-only run first: 0 rejections. Amazon returned success and the change was logged. Four bid raises found afterwards wait for the next approval.
An AI with write access needs discipline. These are the rules Auren publishes, and the ones Unison is built on.
What an account looked like is saved before anything changes.
Bid raises are capped by percentage and by amount, mass raises are refused, and a bid and a budget are not changed on the same campaign in the same window.
Proposed changes wait for a person. Nothing moves until then.
A single writer applies each approved change and records the result.
Every change is recorded, with what it was before.
The prior day’s spend is reviewed for anomalies every day.
Unison applies Auren’s approach wherever it writes: the change is prepared first, a person approves anything that matters, and the result is read back from the platform.
We start with a free assessment: the systems you use, the first workflow worth building, and what useful progress looks like.
More case studies: Once Legos →Alumenza →