Rocketbot vs C TWO (2026)

Saturn Studio agents act in other systems through more than 500 standard apps and components, among them SAP, Salesforce, Microsoft 365, Google Workspace, Oracle, ServiceNow, HubSpot, Zendesk and WhatsApp, plus databases and any REST API, with credentials kept in an encrypted vault and shared by person or team. Where a system has no API, RPA Studio robots work through its screens, and Ai Studio can send an email, a WhatsApp message or an API call once it has read a document. Custom apps for systems outside the catalog come in a limited form on Standard and Enterprise and in full on Corporate.

Sourcedocs.rocketbot.com/2026/06/17/saturn-studio-conectores-e-integracionesread 2026-10-13

C TWO builds no robots or agents of its own and works through the platforms a customer already owns, naming UiPath, SS&C Blue Prism, Automation Anywhere and Microsoft Power Automate beside custom AI agents and direct API calls. It acts inside them, starting, stopping and restarting processes, moving work between resources and, through the Bot Agent on each robot machine, rebooting a frozen or offline machine before resuming the work.

Its connector for Power Automate, Power Apps, Logic Apps and Copilot Studio runs both ways, so a flow starts when C TWO dispatches a session, and those platforms can create, lock, retry and defer items in C TWO's queues. Incidents open tickets in the customer's support tools. Beyond those four platforms, which others C TWO supports is shared with customers only.

Sourcectwo.com/amp/universal-orchestration, the C TWO Microsoft Marketplace listing, the C TWO Bot Agent post and the Microsoft Learn C TWO connector referenceread 2026-10-12

In Saturn Studio each agent is a flow of steps that loads its variables and vault credentials, runs with loops, branches and retries, pauses where a person must act and logs how it ended, and one agent finishing can start the next. A Tool Agent step lets an AI model choose among the tools a builder gives it. The Orchestrator queues runs of robots, Python scripts, applications and other RPA platforms and assigns each to the best available machine by tag, capacity and priority. Each Saturn run is capped at between 10 minutes and an hour depending on the plan.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

Universal Orchestration routes every work item on its own to whichever robot, AI agent, API, Power Automate flow, virtual machine or person fits best on live performance, availability, cost and SLA pressure, and reroutes it as conditions change.

Universal queues give each item a known state, priority and deadline, with custom states a team defines, and items can be locked, retried as a new attempt or deferred to a set time. When a step fails, the platform recovers it and moves the work elsewhere, and governance rules apply SLA priorities, security requirements and operational limits across every process. How a robot or agent carries out its step stays in the platform that runs it, since C TWO decides who does the work and when.

Sourcectwo.com/amp/universal-orchestration, ctwo.com/solutions-universal-orchestration and the Microsoft Learn C TWO connector referenceread 2026-10-12

Agents start from a webhook, a cron schedule, a form submitted in Xperience, an embedded chat widget, another agent finishing, a new record landing in the datastore, or by hand, and a webhook can answer at once or hold the call open until the agent is done. Ai Studio reads incoming email, documents, images and audio and can set a robot or flow going on what it finds, and WhatsApp and Telegram messages reach flows through their connectors. On the robot side, the Orchestrator schedules runs by cron, webhook or chaining.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

Work starts on events and service levels, not a fixed timetable. Runs fire from API calls, time, Power Automate and human input, and the prioritization engine starts and stops processes to protect each deadline as volumes and priorities shift.

Outside systems add work by creating items in a universal queue through the API or the Power Automate connector, and a C TWO task exposed as a flow starts a Power Automate flow whenever C TWO dispatches a session.

Failures start their own path, so a frozen or offline machine, a terminated process or a session running too long sets off recovery, and a problem that persists raises an alert and bars the process from taking more work. Planned downtime moves work to other resources on its own.

Sourcectwo.com/amp/universal-orchestration, ctwo.com/amp/autonomous-operations and the Microsoft Learn C TWO connector referenceread 2026-10-12

Ai Studio reads each email, document, image or audio file a flow hands it and returns structured fields that follow a template the team defines, so an agent works from the data its flow fetches on each run. Saturn Studio's Pinecone module creates a vector index, generates embeddings and upserts and queries them, and Rocketbot's own recipes pipe Gmail and PDF content through OpenAI into Pinecone so a question and answer agent can search a company's documents. That index sits in the customer's own Pinecone account, assembled from the recipe, and Rocketbot keeps no knowledge index of its own.

Sourcerocketbot.com/en/ai-studio.htmlread 2026-10-13

C TWO holds operational data, not documents. Universal queues, item states, credentials, governance rules and execution history drive its routing, forecasting and reporting, and its process intelligence reads that telemetry to flag SLA risks and likely failures before they land. A customer has nowhere in C TWO to load documents for an agent to search, so any grounding belongs to the AI agents C TWO routes work to, which the customer builds elsewhere.

Sourcectwo.com/amp/real-time-intelligence and ctwo.com/amp/autonomous-operationsread 2026-10-12

The question and answer agent can keep conversation history under an ID the builder sets, such as a chat, a channel or a user, holding the last messages up to a History Size the builder picks, and a datastore makes that history persist between runs. Global variables are set once for the account, readable by every agent and kept between runs, while local variables reset on each run, and Nexus's internal database holds records flows read and write. How long kept history lasts beyond that message window is up to the builder.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

What C TWO keeps is the record of the work. Each queue item carries its data, tags, attachments, item logs and every attempt, a retry resets the data to its original value under a new attempt, and history stays available for compliance and reporting. An agent picking up an item gets that item's data, and anything it remembers between items lives in the agent's own platform.

SourceMicrosoft Learn C TWO connector reference and ctwo.com/amp/enterprise-governance; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

A flow can stop and wait for a person, for example sending an approval request by email, Teams or an Xperience form and carrying on only once it is approved, and common recipes hand a case to a human when the AI's confidence is low. Agents act within rules the builder sets, with every decision and action logged for audit. Human in the loop steps come with every plan.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

People share the queues with robots and agents, so a work item can be routed to a person as its handler. When a robot or flow needs help, it opens a human in the loop form in C TWO with a title, an introduction, the fields to fill and a deadline, tied to the work item, and assigns it to a user, who completes it before the digital worker carries on. Forms can be reassigned and searched by status, policies block unauthorized actions before they run, a process that keeps failing is barred from taking work until someone steps in, and every approval is logged.

SourceMicrosoft Learn C TWO connector reference, ctwo.com/amp/enterprise-governance and ctwo.com/amp/universal-orchestration; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

The Orchestrator is the suite's single identity point, with a role and permission matrix by module, two factor sign in and Google sign in on every plan, and Active Directory sign in and SCIM on Corporate.

Credentials sit in an encrypted vault, can be shared with a person or a team and revoked at once, robot steps are encrypted, and audit logs record who did what, kept from 90 days up to 12 months with SIEM export on Corporate.

Rocketbot holds an ISO/IEC 27001:2022 certificate from NYCE, with an IQNet counterpart, covering its cloud infrastructure, development and support, issued in May 2026, valid to May 2029 and held since June 2023.

Sourcedocs.rocketbot.com/2024/06/05/certificado-iso27001read 2026-10-13

C TWO has held SOC 2 Type II since 2024. Access to the platform is role based, and a central store holds every robot, agent and system credential with rotation and an audit of its use. Policies enforce security requirements and operational limits across every process and block unauthorized actions before they run. Whether staff can sign in through the company's own identity provider is not public.

Sourcectwo.com/amp/enterprise-governance, ctwo.com/amp/autonomous-operations and the 2024 C TWO SOC 2 Type 2 announcementread 2026-10-12

The Orchestrator keeps four kinds of log, robot, process, user and instance, records the input data and the component where a run failed, and shows the live status, metrics, alerts and history of every automation. Saturn Studio keeps each agent run with detailed logs, full text log search and analytics dashboards, holding from 1,000 to 100,000 runs and logs for 7 to 365 days by plan. Older history has to be exported, since retention runs first in, first out, and Rocketbot's terms say the logs carry no forensic evidentiary integrity.

Sourcerocketbot.com/en/orchestrator.htmlread 2026-10-13

Every action, change, execution, escalation and exception is logged across technologies, so each process and task carries an end to end trail, and flows write their own session and item logs into C TWO as they run.

Live session telemetry and SLA tracking sit beside a real time digital twin of how work moves across robots, APIs, AI agents and people, with throughput, success and failure rates and average handling time for every process. Hundreds of prebuilt dashboards can be tailored by audience, exported as CSV or PDF or sent by email on a schedule. What an agent reasoned inside its own platform stays in that platform's logs.

Sourcectwo.com/amp/enterprise-governance, ctwo.com/amp/real-time-intelligence and the Microsoft Learn C TWO connector referenceread 2026-10-12

Cloud plans run on the AWS public cloud, where the Orchestrator uses a database across several availability zones watched by Amazon CloudWatch, and the Orchestrator can also run on premises on the customer's own servers. RPA Studio robots always run on the customer's machines or virtual machines. Ai Studio is cloud only, though a customer can point it at its own model hosted on premises. Saturn Studio runs only in Rocketbot's cloud and cannot reach a local network, and no AWS region is named.

Sourcerocketbot.com/en/terms-and-conditions.htmlread 2026-10-13

A customer runs C TWO in C TWO Cloud, on a C TWO hosted address, or on its own servers on premises, and each tenant's API is addressed by division in both shapes. The Bot Agent on each robot machine reaches the platform over outbound connections only, so robots in the cloud or on premises need no inbound firewall rules, and C TWO supports high availability for large estates. C TWO Cloud's hosting region is not public.

SourceMicrosoft Learn C TWO connector reference, the C TWO Bot Agent post and ctwo.com/amp/autonomous-operations; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

The Saturn Studio template market is a catalog of prebuilt agents a team previews read only and adds to its workspace with one click, grouped by category and showing the modules each one uses, and administrators can publish their own. Access to templates widens by plan, with a custom set on Corporate.

Sourcedocs.rocketbot.com/2026/03/20/saturn-studio-market-de-templatesread 2026-10-13

C TWO ships orchestration, governance and intelligence as one platform, and the working parts are the customer's own, such as SLA requirements per process, governance rules, queue states and underperformance profiles. The reporting comes with hundreds of prebuilt dashboards. Beyond those dashboards, a team sets C TWO up from its own processes, with no ready made agents or automations to switch on.

Sourcectwo.com/amp, ctwo.com/amp/real-time-intelligence and the Microsoft Learn C TWO connector referenceread 2026-10-12

A builder picks the model for each AI step in a flow, from OpenAI, Anthropic's Claude, Google's Gemini, Mistral AI, Groq, DeepSeek, xAI's Grok and Hugging Face to models on Azure OpenAI and AWS Bedrock, or any model ID available on OpenRouter, using the team's own keys. Ai Studio runs on Rocketbot's internal model on every plan, and from Standard up a company can connect its own model in the cloud or on its own servers.

Sourcedocs.rocketbot.com/2026/06/25/saturn-studio-changelogread 2026-10-13

C TWO chooses which worker handles an item, and when that worker is an AI agent, the agent runs on whatever model its own platform uses. C TWO's prioritization and forecasting models are unnamed, and a customer cannot pick or swap the model behind them.

Sourcectwo.com/amp and ctwo.com/amp/autonomous-operationsread 2026-10-12

API keys created in Saturn Studio let outside software start robots and read account data through the platform API, each key with a name, an expiry, a last used date and instant revocation, and Orchestrator API keys last two years. Inbound webhooks give each agent its own endpoint, and an MCP server lets AI clients such as Claude or Copilot build bots and run tasks in the account. Developers have no public endpoint reference for the platform API.

Sourcedocs.rocketbot.com/2026/03/10/saturn-studio-api-keysread 2026-10-13

C TWO exposes a REST API on each customer's own host, addressed by division, with bearer token authentication through service account tokens for production and personal access tokens for testing, both issued in the product and shown once. C TWO's own connector for Power Automate, Power Apps, Logic Apps and Copilot Studio, in preview, covers session triggers, completion and failure reporting, session logs, timeouts and graceful stop checks, universal queue items, states, tags and attachments, and human in the loop forms. The wider API reference sits in a knowledge base open only to customers.

Sourcelearn.microsoft.com/en-us/connectors/ctwo, the C TWO connector referenceread 2026-10-12

Builders test a flow by running it and reading its logs, with log search and console output from custom JavaScript for debugging, and the Orchestrator versions robots with rollback.

Neither Saturn Studio nor the Orchestrator offers separate development, test and production environments inside one instance or Git style versioning, so promotion between stages follows the customer's own procedures, often a global variable that splits resources by environment.

Rocketbot's own guidance asks teams to keep a separate development environment and test robots with real data before production, and its terms say Ai Studio's accuracy in a flow must be validated before production use.

Sourcerocketbot.com/en/terms-and-conditions.htmlread 2026-10-13

C TWO measures operations as they run. Cross technology value reporting compares the cost and performance of RPA, APIs, AI agents and Power Automate, the Optimization Center points out inefficiencies with suggested improvements, and predictive intelligence flags SLA risks and likely failures before they hit. A team can see which kind of worker handles a process best, but a change to an SLA, routing rule or governance policy goes live without a test run first.

Sourcectwo.com/amp/real-time-intelligence and the C TWO new product features postread 2026-10-12

RPA Studio builds software robots that work any system the way a person does, clicking, typing, copying data, filling in forms and reading the screen, and they run on the customer's own Windows, macOS or Linux machines. The Orchestrator dispatches them, and a Saturn Studio flow can call a robot as one of its steps.

Sourcerocketbot.com/en/rpa-studio.htmlread 2026-10-13

The robots C TWO manages click and type through screens, and C TWO itself does not. It dispatches, watches and recovers those workers, and the Bot Agent on each machine reboots it and reports on virtual desktop performance and the processes and applications running, all through system controls. When a screen change breaks a robot, C TWO notices, reports and reroutes the work.

SourceC TWO Bot Agent post and ctwo.com/amp/autonomous-operations; ctwo.com/blog/c-two-bot-agent-secure-and-seamless-bot-managementread 2026-10-12