Loading...
Loading...
Put an AI team to work across the RapidStart Apps you already use.
RapidClaw for RapidStart Apps deploys OpenClaw into your Azure, securely connects it to Dataverse, detects your installed CRM, Project, and Field Service apps, and adds the right specialist Agent Packs. Arcy and RapidClaw Command Center help you configure agents, models, schedules, connectors, Teams, email, approvals, and safety controls without becoming an OpenClaw expert.

RapidClaw for RapidStart Apps now runs on one shared RapidClaw foundation: the base runtime, wizard, Command Center, Arcy, Teams, email, model controls, backup, secure connectors, and safety controls are common across the product line.
The RapidStart Apps layer adds governed Dataverse access and business-specific Agent Packs. During setup, RapidClaw detects which RapidStart CRM, RapidStart Project, and RapidStart Field Service solutions are installed, then adds only the matching capabilities for that environment.
Dataverse remains the system of record for RapidStart business data: accounts, contacts, opportunities, projects, tasks, work orders, service activity, custom tables, and the other records your RapidStart Apps use to run the business.
RapidClaw no longer treats Dataverse as the broad system of record for deployment history and operational runtime state. Those live in RapidClaw shared PostgreSQL and runtime services. The RapidClaw Dataverse connector supplies governed access to standard and custom Dataverse tables so agents can work from business context without owning the business database.
RapidClaw presents specialist capabilities based on the RapidStart Apps actually installed. Persona names may appear in the experience, but the authoritative unit is the business capability each agent provides.
End users normally work through the RapidClaw orchestrator in Teams. Behind the scenes, the orchestrator selects the right specialist capability for the app, record, and task at hand.
Arcy is the Command Center assistant for configuring and improving the AI team. The older separate builder responsibility has moved into Arcy, giving administrators a guided way to shape agents, skills, connectors, instructions, and scheduled work without becoming OpenClaw experts.
Arcy works with the models actually deployed in the customer environment. It can recommend an available Microsoft Foundry/Azure AI model, draft reviewable instructions, and help operators activate a change now or save it as a draft.
RapidClaw gives users one governed Teams surface while allowing selected agent workflows to participate in email when appropriate. The CRM Agent Pack can recommend mailbox-enabled agents, but operators create and manage mailboxes later through the shared Command Center Email page.
Email setup is consistent across Agent Packs: verified tenant domains, test mode, test email, approvals, and deletion controls all stay under operator control. Agents do not all receive mailboxes by default, and outbound communication remains approval-aware.
RapidClaw for RapidStart Apps receives the same shared Command Center capabilities as the base product. Administrators can manage runtime health, Agent Packs, model assignment, scheduled tasks, Teams readiness, approvals, policies, usage, costs, email-enabled agents, backups, connectors, and activation controls from one Microsoft-aware console.
Emergency Stop freezes agents, schedules, and Teams activity while Arcy remains available for diagnosis and recovery. Backup and migration are encrypted, credentials use protected dialogs and Key Vault-backed handling, and the installed OpenClaw extended-stable channel provides a managed upgrade path rather than unexpected runtime changes.
RapidClaw is deployed safely first, then activated intentionally. SetupOnly, Pilot, and Live activation modes let administrators decide which agents, schedules, connectors, email flows, and live behaviors are allowed in production.
Agents can prepare work, explain what they found, and queue protected actions for review. Write-capable Dataverse tools, outbound messages, and sensitive connected-system actions remain permission- and approval-controlled.
RapidClaw does not replace OpenClaw, Microsoft Copilot, or Microsoft Agents. OpenClaw remains the runtime. RapidClaw adds the Microsoft-aware deployment, Command Center, Arcy, Dataverse connector, Agent Packs, governance, and support layer around it.
Organizations can use RapidClaw instead of Microsoft agent technologies or alongside them without conflicts. The difference is that RapidClaw is focused on governed business work inside the RapidStart Apps and Azure environment the customer controls.
Yes. RapidClaw for RapidStart Apps is designed for environments running RapidStart CRM, RapidStart Project, or RapidStart Field Service. RapidClaw detects which solutions are installed and adds only the matching Agent Packs.
No. The shared RapidClaw Base is common, but CRM, Project, and Field Service Agent Packs are added based on the RapidStart Apps installed in that environment.
Dataverse remains the system of record for RapidStart business data. RapidClaw shared PostgreSQL/runtime services own deployment history and operational runtime state, and the RapidClaw Dataverse connector supplies governed access to standard and custom tables.
Only when the connector, tool, permissions, and approval policy allow it. RapidClaw does not grant open-ended Dataverse write authority; sensitive and write-capable actions remain permission- and approval-controlled.
End users normally interact with the RapidClaw orchestrator in Microsoft Teams. The orchestrator coordinates the right Agent Pack capability behind the scenes rather than exposing every specialist as a separate chat persona.
The CRM Agent Pack can recommend mailbox-enabled agents. Operators create and manage mailboxes later through the shared Command Center Email page, with verified tenant domains, test mode, test email, approvals, and deletion controls.
Arcy helps administrators create and edit agents and skills, build scheduled tasks, configure secure connectors, turn short descriptions into reviewable instructions, and choose from Microsoft Foundry/Azure AI models deployed in the customer Azure subscription.
RapidClaw deploys an OpenClaw runtime into customer-owned Azure, connects it to the shared RapidClaw services, configures Microsoft identity and Teams access, and enables the matching RapidStart Apps Agent Packs. Azure infrastructure and model-token usage are billed through the relevant Microsoft or model-provider services.
No. RapidClaw is deployed safely first. Administrators decide which Agent Packs, agents, schedules, connectors, email flows, and live behaviors to activate in Command Center.
No. RapidClaw runs independently of Microsoft Agents. You can use RapidClaw instead of Microsoft Agents or alongside them in the same Microsoft environment without conflicts.