Aura Autopilot vs UiPath

Aura Autopilot 43

The launch post is dated 31 October 2026 and Aura 1.2.3 and 1.2.4 of 30 October 2026 ship Autopilot, so the last change is within 30 days (30). GitHub releases couldn't be read, and the two Aura release-note entries aren't three (0). Issue and pull-request replies couldn't be read; the project is days old, with Discord and support email as other channels (5 of 25). Not in the official MCP registry under any namespace (searched for autopilot and ramenvr) (0). Pinned dependencies, per-platform locks in packaging/, CI on three operating systems, conventional-commit checks and code-owner review (8 of 10). 43 in all.

UiPath 80

Orchestrator release notes dated 12 October 2026 (30). Entries on 5, 7 and 12 October and nine dates in September (20). Public dated release notes, a forum and a support portal. Support was not tested (12 of 15). The Python SDK uipath 2.14.37 was published on 12 October 2026. UiPath's MCP servers are not in the official MCP registry, where a search returned only a third-party server (12 of 15). The SDK's CI was not checked (6 of 10).

Aura Autopilot 53

Local-software reading, as tokeneconomizer was read: 30 for what leaves the machine and credentials, 20 approvals and sandboxing, 15 injection, 15 audit, 20 programme. Run sharing is on by default and sends recordings, screenshots, agent traces with the code the agent read and, for MCP runs, the user's own Claude Code or Codex conversation to app.tryaura.dev, after redacting secrets, paths, user and host names and email addresses. Keys sit in plain text in autopilot.env, the file tools never read *.env, and the localhost control endpoint carries a random secret (12). File tools write only the run's folder, notes.md and lib.py, and the user can stop or steer a run from the tab. autopilot connect codex sets default_tools_approval_mode to approve, and on Windows and macOS the sandbox is a plain child process without keys but with network and disk (10). sandbox.py names prompt injection from a game's code as the reason for the sandbox, and the frame describer is given only open questions (11). Each run keeps its agent log, harness versions, traces, decisions, report and recording, and the Feed tab shows activity (13). SECURITY.md asks for GitHub private vulnerability reporting; no security.txt on www.tryaura.dev (404), no bounty or certification found, advisories couldn't be read. Releases are signed and immutable, and pull requests need a code owner's approval (7). 53 in all.

UiPath 82

MCP OAuth with resource indicators binding a token to one server, external apps with OAuth scopes such as OR.Jobs, and PATs with chosen scopes and an expiry of up to one year (30). Folder roles limit what a token can do, and automatic client registration is off until an administrator enables it in the AI Trust Layer. No approval step before destructive API calls was found (14 of 20). Tools return job outputs from robots that read third-party applications, and no prompt-injection guidance was found in the MCP pages (5 of 15). Orchestrator audit logs and a preview API audit view (13 of 15). security.txt valid until 2028 with a HackerOne programme, and SOC 2 Type 2, ISO/IEC 27001 and FedRAMP Moderate claimed on the Automation Cloud page (20).

Aura Autopilot 50

Open-source software with paid parts around it, so the pricing lines are read for what a run needs. No payment protocol (0). TypeSafe publishes Jev's price per million input tokens and Aura's plans are public, Indie from $10 a month billed annually (20). Autopilot is free under Apache-2.0, and Aura's two-week trial needs no card (20). No Ramen account is needed with one's own keys, but a person installs the editor plugin and gets a TypeSafe key or signs in to Aura in a browser, so 10 rather than the self-hosted rule's 20 (10). 50 in all.

UiPath 25

No x402, MPP or L402 (0). Basic is published at $25 a month and the Community plan is free, while Standard, Enterprise and extra robots are priced by sales (10). The Community plan is free with no time limit by direct sign-up. No page we read says whether a card is needed (15 of 20). A person signs up in a browser and creates the PAT or external application (0).

Aura Autopilot 41

Local-software reading, as a stdio MCP server with engine plugins. Official downloads per engine and OS from GitHub Releases, signed and listed in SHA256SUMS.txt, with Unreal 5.4 to 5.8, Unity 6000.0 or later, Godot 4.7 or later, Windows and macOS and Python 3.12 or later stated. The agent service isn't on a package registry; the plugin installs it, with uv and Bun, on first run (17 of 20). .github/workflows/ci.yml runs ruff and pytest on Linux, Windows and macOS with Python 3.12 and 3.13 plus a Codex end-to-end job, and CONTRIBUTING.md names download and uninstall end-to-end workflows. Whether runs pass wasn't checked, as github.com couldn't be read (15 of 25). Open issues couldn't be read, and the repository is days old (5 of 25). No changelog; releases are tagged v<version>-<commit>, the plugin protocol is versioned and the contributing rules say to add optional fields rather than change existing ones (4 of 15). Python package 0.1.0 and the Unreal plugin marked IsBetaVersion (0). 41 in all.

UiPath 62

Graded on the hosted Orchestrator API and MCP servers. Public Atlassian Statuspage at status.uipath.com with component and incident history (20). The 90-day feed has several major incidents, including robot job failures in Europe from 10:00 to 17:23 UTC on 10 September 2026, solution deployments failing from 15:18 to 20:45 UTC on 11 September, Cloud Robot jobs stuck pending in the US for 94 minutes on 2 October and an expired certificate taking down several ML services across regions on 13 October (0). Per-endpoint rate limits with numbers (15). 429 responses carry Retry-After and X-RateLimit-Remaining, with retry guidance. No idempotency key for StartJobs was found (12 of 15). The Automation Cloud page states a 99.9 per cent uptime SLA, but the SLA document with credits was not found publicly (5 of 10). The Orchestrator API and the UiPath MCP server type are generally available, with Platform and Swagger servers in preview (10).

Aura Autopilot 55

Apache-2.0 for the repository, with bundled fonts under the SIL OFL (30). The repository's code docstrings and the Unreal README say what is shared and how it is redacted, but docs/run-data.md, which they cite, isn't published. Aura's terms (TribeVR Inc., 25 June 2026) and privacy policy (27 August 2026) don't mention Autopilot, opt Aura customers into training by default with a perpetual licence to that data, and state no retention period. Runs with one's own keys go to Aura's endpoint under an install token with no account and no terms named. Sent data is never deleted (10 of 30). No deprecation policy; the protocol rule to add optional fields is a contributor guideline (6 of 20). Sharing is disclosed in the setup screen, the README and the plugin docs with three ways to turn it off, but it is on by default, the documentation page doesn't say so, and it includes the user's own agent conversation (12 of 20). 58 in all.

UiPath 76

Closed service with published terms pages, though the MSSA that governs paid use is signed per customer and not public (15). The privacy policy covers cloud product data, says it may be used for product improvement and machine learning under the customer contract and warns against personal data on Community. The legal page dates it 30 November 2018, and the DPA download was not read (15 of 30). A product lifecycle policy and a dated deprecation timeline for the Swagger 2.0 specification (17 of 20). Hosting regions are named, such as Europe for Basic. No subprocessor list was read (10 of 20).

Aura Autopilot 74

MCP reading. All 14 tools (start_run, wait, probe, run_harness, snapshot, describe_frames, restart_level, report, frames and five file tools) have JSON Schema inputs, read in autopilot/mcp.py, session.py, external.py and files.py (25). No llms.txt on www.tryaura.dev (404). The agent skill, INSTRUCTIONS.md and KIT.md are Markdown written for the agent, and the README and CONTRIBUTING.md are in the repository (7 of 10). Descriptions say what each tool does and when not to use it (frames is for a describer subagent only, describe_frames is a fallback), with server instructions (17 of 20). Required fields and an enum on kind, but report.outcome is a free string with its values only in the description, numeric ranges sit in descriptions rather than the schema, and probe takes free-form Python (9 of 15). Prompt examples in the README and skill, plain-language errors in the MCP server and documented exit codes for headless runs (11 of 15). Version numbers and a protocol version, but no public changelog, and GitHub release notes couldn't be read (5 of 15). 74 in all.

UiPath 79

The Orchestrator API is described in OpenAPI 3.0, served per tenant at the Orchestrator URL plus /swagger/index.html rather than as a public file (20 of 25). llms.txt at docs.uipath.com and a Markdown copy of every page by adding .md (10). API pages state scope and limits clearly, such as which fields GET /odata/Jobs omits. MCP tool descriptions come from the description of each published artifact, so quality depends on the owner (12 of 20). OData types and an enumerated types reference. MCP tool inputs follow each process's arguments (11 of 15). Request examples on each API page and a table of custom error codes (14 of 15). Monthly dated release notes. UiPath says the Swagger version number should not be relied on (12 of 15).