Open Arawa
Use the embedded Arawa window in the builder, or start from your Arawa Cloud workspace.
Arawa sits in the builder as an embedded window. Ask it to create pages, refine components, and publish—with approval on destructive changes. Claude and ChatGPT can connect to the same tools.
Arawa turns what you describe into explicit website operations on Arawa Cloud.
Use the embedded Arawa window in the builder, or start from your Arawa Cloud workspace.
Share the audience, pages, and structure. Arawa creates components, templates, and content.
Preview changes, approve destructive actions, then publish when the site is ready.
The protocol matters less than the confidence it gives your team.
Grant access to the right workspace and websites, then revoke it whenever needed.
Read setup guide →Agents call explicit CMS actions instead of guessing at a hidden interface.
Explore tools →Component code and structured data are checked before changes reach page previews.
See safeguards →Review page and component previews before publishing production changes.
Explore workflow →Agent actions carry actor, client, target, result, and timing context.
Security overview →The dashboard remains the control plane for access, approvals, billing, and recovery.
For teams →Arawa is the conversation window in the Arawa Cloud builder. You can also start from your workspace at ar.arawacloud.com.
Yes. Compatible clients can connect to the same website tools through MCP. Arawa remains the built-in way to work in the builder.
Arawa can prepare and validate work. Destructive changes ask for approval. Teams can still keep publishing behind review and permissions.
No. The editor stays the control plane for websites, approvals, modules, teams, billing, and recovery.
Create a workspace, open the builder, and use Arawa to draft and publish websites.