AI control layer · for Amazon sellers

AI agents propose the work. You keep control of the brand.

HOLONA is an engineering prototype for a control layer above seller tools — designed to coordinate ads, inventory, listing, pricing, and review recommendations into one auditable decision system.

Every recommendation traceable. Every approval explicit. Every risk visible.

7target domains
Ads · Inv · List · Pricing · Reviews · Anomaly · Compliance
R0–R5
Proposed risk tier on every recommendation
Trace-first
Data · reasoning · risk · formula
L0–L4
Proposed operator-controlled automation cap
Live agent activity · Treadway Outdoor demo fixture Demo running
11:30ADS-PACERHold +18% bid · root cause = listingR3
11:30LIST-POLICYDraft sizing chart rewrite · B0CJZK4XYZR2
11:31REV-CONTENTEscalate reply backlog · SLA breach 38%R2
11:32INV-REPLENISHER8 ASIN reorder draft · 30d coverR1
11:34PRX-PRICERMarkdown 12% · CO-SLP-012 phase-outR1
11:38ANO-WATCHERLiquidation eligible · HB-LGY-040 540d agingR5 · ADV
11:42COMP-AUDITTrace verified · 17 actions · 12h cadenceR0
01 · What is HOLONA

Operational decision software for serious sellers.

A control layer above your existing tools. Six promises define the boundary.

HOLONA sits on top of Lingxing, Helium 10, Amazon Seller Central — whatever you already use — and orchestrates fragmented AI agents into a single, traceable, auditable, replayable decision system.

The seller keeps the wheel. The system handles the load.

This is not automation. It is control. The customer is not handing the wheel over to AI — they are gaining a wheel they did not have before.

Every decisiontraced
Every actionreplayable
Risk alwaysvisible
Operatorin control
Confidence is realnot decorative
No data leavesyour scope
What HOLONA is not
×
Not a brand replacement. HOLONA does not compete with the seller's own brand.
×
Not a platform. HOLONA does not host or sell goods.
×
Not a generative tool. Listings and ad copy are not the core offering.
×
Not a single agent. HOLONA is the layer above agents, not an "AI assistant."
×
Not a black-box optimizer. Transparency is the product, not a feature.
×
Not consumer-facing. Every output is for the operator, never for the end shopper.
02 · How it works

A four-layer loop: watch, recommend, execute, decide.

The closed-beta design uses one decision loop. Each layer is intended to remain visible, replayable, and stoppable at an operator-defined boundary.

01 · Perceiveprototype target · adaptive cadence
Watch
24/7 signal stream — ACoS shifts, inventory drift, listing changes, review anomalies.
Design target. Official API polling at adaptive cadence · anomaly detection · cross-agent signal de-duplication.
Current mode · read-only / shadow evaluation
02 · Recommend7 target domains · cross-domain
Recommend
Multi-agents form a recommended action with traced reasoning. Cross-domain attribution in one unified plan.
Prototype design. Rules + LLM reasoning · conflict surfacing · white-box 4-piece schema (data · reasoning · risk · formula).
Coverage · Ads · Inv · List · Price · Rev · CS · Comp
03 · ExecuteL0–L4 · R-cap
Execute
The initial beta is read-only and advisory. External actions require explicit operator approval and a separate readiness gate.
Future gated path. Official API writes · attributable requests · rate limiting · auditable execution records.
R5 · advisory only by design
04 · Decidereplay · override · policy
Decide
The trace is replayable. Every decision is yours to review, override, or codify into policy.
Prototype design. Decision Card archive · policy drafting from trace · periodic review packs.
Retention target · subject to beta validation
03 · Read a trace

An illustrative decision, end to end.

This demo fixture shows the proposed Decision Card structure — data, reasoning, risk, formula, and confidence. It is not production customer data or a measured product result.

Decision Card Raw trace Replay Derive policy
DC-4731 · 2026-05-27 11:30 UTC · ADS-PACER + LIST-POLICY + REV-CONTENT
Action R3 · Caution
Hold bid increase on B0CJZK4XYZ — re-prioritize listing SEO and CS reply backlog before adjusting Sponsored Products.
Data
ACoS 27% → 41% over 7d · BSR rank 24 → 31 · Review backlog 8 pending · SLA breach 38% · Sizing-cluster review share 26%
Reasoning
Spearman correlation between ACoS and BSR rank = −0.78. Raising bid will increase ad spend without recovering ad-attributed conversion, because the conversion drop traces to the listing (review backlog → CS SLA breach → reviewer trust → BSR). Address root cause before symptom.
Formula
recovery_p = α·listing_fix + β·review_clearance − γ·bid_increase  where α=0.62, β=0.31, γ=−0.04 · backtest n=90d
Cross-agent
ADS-PACER · hold +18% bid proposal · LIST-POLICY · draft sizing chart rewrite · REV-CONTENT · escalate review reply backlog — all three suspended until operator review.
Reversibility
Fully reversible · no spend committed · operator may approve, defer, or override individual agent actions independently.
Confidence 0.91 · 7-day projection · backtest 90d · trace-id tr_4731_ed8a The trace is the product.
04 · Compare

Four ways HOLONA is not another seller tool.

This matrix compares intended product boundaries for customer discovery. It is not a benchmark or a claim that the HOLONA targets are already implemented.

CapabilityHOLONAAmazon SAH10 / JSGeneric AI
Independent from AmazonCan recommend stop-spending
Cross-tool orchestrationAds ↔ Inv ↔ List ↔ Price ↔ Revpart
Cross-domain chain attributionRoot cause across 4 agents
White-box decision traceData · reasoning · risk · formulapart
R0–R5 risk classificationEvery action surfaced
L0–L4 automation spectrumUser-controlled execution cappartpart
R5 never auto-executesBrand-level safeguard
BSA + DPP readiness planDesign target; not a certificationtargetpartpart
05 · Proposed beta pricing

Three planning tiers for design-partner conversations.

These are non-binding planning assumptions. HOLONA does not currently accept payment, start trials, or create paid subscriptions.

Tier 1 · Solo
Founder operator
$20K–$150K GMV operators running their own account. Pick one agent — Ads, Inventory, or Pricing.
$25/mo · single agentFull bundle · $100/mo
  • 1 agent · L0–L2 only
  • Full Decision Card trace
  • Weekly ops pack
  • 7-day free trial · no card required
Tier 2 · TeamRecommended
Ops-coordinated
$300K–$800K GMV, 10–20 person teams. All 7 agents + cross-domain orchestration + 5 seats included.
$400/mo · full bundleSingle agent · $40/mo
  • All 7 agents · L0–L4
  • Cross-domain chain attribution
  • 5 team seats · simplified RBAC
  • 14-day free trial · full bundle access
Tier 3 · Enterprise
Multi-team brand
$2M–$10M GMV brands · 50–100 person ops. Multi-workspace, custom Rules Engine, unlimited seats.
$5K–$30K/mo+ $20K–$100K once · half-custom
  • Multi-workspace · org view
  • Custom Rules Engine templates
  • Unlimited seats · dedicated onboarding
  • Closed beta · 6–10 design-partner slots

Full comparison · pricing details →

06 · Data & Security

Amazon BSA readiness is a beta gate.

The items below are architecture targets for a future connected beta. They are not a certification, Amazon endorsement, or claim of current production operation.

Amazon BSA Agent Policy Enforced 2026-06-02

  • Target: attributable official API requests
  • Target: replayable audit records and defined retention
  • Boundary: no browser automation or scraping
  • Target: conservative rate limiting and backpressure
  • Policy target: seller data is not used for model training

Data Protection Policy

  • Target: encryption at rest with managed keys
  • Target: TLS-protected service-to-service traffic
  • Target: explicit PII and operational-data retention schedules
  • Target: per-seller permission scope and tenant isolation
  • Deployment region and operating entity to be confirmed before a connected pilot

R5 is never executed — by design, not by toggle. Decisions classified R5 (irreversible system-wide impact) are presented as advisory only, with a one-click Amazon Seller Central deep-link. No automation level you choose can override this. The wheel stays with you.

07 · About

HOLONA

HOLONA stands for a simple operating principle: every autonomous action should belong to a larger system of control.

Each agent can do useful work on its own, but the product only matters when those agents coordinate across ads, inventory, listings, pricing, reviews, and compliance.

HOLONA is built for operational clarity: fewer blind optimizers, more traceable decisions, and a seller who can still see, replay, and override the work.

ProductHOLONA
Operating entityTo be confirmed before commercial contracting
StageEngineering prototype · closed-beta preparation
First pilot goal3–5 design partners · read-only shadow mode
ContactInbound forwarding active · hosted mailbox pending
Trail Runner Pro Max — chain attribution across four agents in three minutes.
Demo video · Q3 2026 · CM1 walk-through
Closed beta · Q3 2026

Beta applications are temporarily paused.

Inbound mail is active at contact@holona.io. The structured application remains paused until a durable submission endpoint and full hosted mailbox are verified.

Applications are paused. For a direct conversation, email contact@holona.io.
No form data is transmitted or stored while applications are paused.