Stage the change, then approve
Curate reads the store and stages each change for a person to approve.
Three modules: Nexus answers, Hive Council routes and approves, Curate prepares a Shopify brand's changes.
Nexus: Internal to Raava for now.
Hive Council: Internal to Raava for now.
Curate: Built for one client.
Works todayHive Council approvals behind two sign-ins, and Curate inside Shopify admin for Fujian.
BuiltNexus, behind a sign-in, in private preview.
Not made yetCurate's Workflows, Ads, Content, Research and B2B screens.
Nexus, Hive Council and Curate are built and run separately. Each carries its own state.
Works todayA question goes in through the web chat and an answer comes back, with one log line.
BuiltAn agent-drafted item sits in the tray until someone approves it.
Works todayCurate is read-only against the store. Each change waits as a plan for a person to approve.
Works todayCurate reads the store and stages each change for a person to approve.
Hive Council holds agent work in one tray until someone approves it.
Curate's data routes answer only inside a signed-in Shopify session, filtered to that shop.
Your team asks Nexus through a web chat; Raava tools reach it through a gateway that needs a key.
Hive Council gives each task an assignee, a reviewer and an approver. You choose which work needs approval.
Curate reads store data without writing to the store. Every change is staged, versioned and waits for approval.
Hands work to agents across the three modules.
Chooses which work needs a person's approval.
Works inside Shopify admin with Curate.
Each store change is staged and waits for approval.
Not your fit if you want agents that run with no approvals and no record.
Nexus and Hive Council stay inside Raava, and Curate runs for one client's store. The free audit is a 45-minute call with a written follow-up you keep.