Sema4.ai

Read this first: Robocorp no longer exists as a product

If you arrived here looking for Robocorp, the Python-based open-source RPA platform, the headline is that it is gone. Sema4.ai acquired Robocorp in January 2024, the company rebranded to Sema4.ai, and the product line was absorbed and redirected: robocorp.com now serves Sema4.ai's enterprise AI-agent offering and its "Sema4.ai RPA" pricing documentation, the classic Robocorp Control Room/developer stack is no longer sold as its own product, and the open-source community layer has largely evaporated. A community contributor on the Robot Framework forum put it bluntly in March 2025: "Robocorp does not exist as a company anymore — and RCC is not maintained by them publicly anymore… I would recommend searching for another solution" (source: Robot Framework forum post, cited in unsubbed.co's Robocorp retrospective). The robocorp/rcc environment manager still sits on GitHub, but it ships under a Sema4.ai commercial EULA rather than an open-source license — the package-index license field resolves to NOASSERTION, which is itself a signal to read before you deploy (source: unsubbed.co; repository license on GitHub).

So this review covers two things: what Robocorp was and whether its successor deserves the same audience. The short version: the successor is a real, credible product, but it is aimed at enterprise finance operations on Snowflake or in your own cloud account, not at the individual automator who chose Robocorp for free Python RPA. Anyone evaluating "Robocorp" in 2026 is actually evaluating a differently-shaped, sales-led platform — and I rate this entry on that reality.

What the platform does today

Sema4.ai sells an enterprise AI-agent platform for document-heavy back-office work — invoice reconciliation, accounts payable, data extraction and routing — built on the former Robocorp engineering lineage (Python-first, Robot Framework ancestry) plus a new agent layer. The pitch on the current site is automation rates in invoice processing and cycle times cut from days to minutes (vendor claims, flagged as such). Architecture, per the vendor docs and independent profiles: agents built in an Agent Builder from written notes, voice notes or documents; daily use in a Work Room; monitoring in a Control Room; agents carry memory across sessions; the SAFE framework is meant to make agent behavior deterministic and auditable; and there are Model Context Protocol connectors for Snowflake, Slack, GitHub, Google Workspace and HubSpot. Deployment is deliberately inside your perimeter — natively on Snowflake via Snowpark Container Services ("no data leaves Snowflake") or in your own AWS/GCP/Azure VPC — which is where the enterprise positioning becomes concrete (source: sema4.ai; automationatlas.io; recatools.com).

Pricing is where the picture fractures, and I will not paper over the conflict. The documentation on robocorp.com/pricing ("Sema4.ai RPA," last edited February 16, 2026) still publishes a three-tier table: Developer (free, 240 run minutes per month capped, 1 workspace, max 2 processes per workspace), Consumption ($0.10 per run minute, 20 workspaces, 200 processes, 20 parallel runs per process), and Enterprise (custom; SSO, regional Control Rooms, custom RBAC, dedicated account manager available). Meanwhile independent 2026 reporting describes a Team Edition at $15 per agent per day on the Snowflake Marketplace and Enterprise pricing behind a sales call (a $165 figure appears in the site's pricing UI without a stated unit), and unsubbed.co's retrospective says the old consumption model "appears to be discontinued or replaced by the per-agent-per-day structure" (source: unsubbed.co; recatools.com). One tracker quotes first-year totals from roughly $49K to $127K for enterprise deployments (source: trivista.com). At time of writing, treat the $0.10/minute table as the documented starting point and get any quote in writing.

My testing notes

What I look for in this category is a transparent path from "I have a Python script" to "it runs unattended with an audit trail." Two observations from working with the Robocorp lineage and the current stack.

First, the developer tooling that made Robocorp loved is still the best thing in the drawer. The Python-based stack, the RCC environment manager and the VS Code extension remain the fastest way I have found to build and package an RPA robot in a language I already write — no proprietary DSL, no XML flowcharts. But the maintenance signal has flipped: RCC's public activity has stalled and the licensing has moved to a commercial EULA, so a team that adopted Robocorp for open-source reasons now has an orphaned dependency. In my testing of the migration surface, robots written against the old robocorp libraries run as-is in most cases, but the orchestration story (where they run, who schedules them, what audit trail they leave) now requires Sema4.ai's Control Room — which is a sales conversation.

Second, the platform's actual differentiator today is deployment posture, not RPA. Building an agent that reads invoices and reconciles them against a ledger, entirely inside a Snowflake account where no data leaves, is a genuinely different promise from UiPath-style automation, and it explains the pivot: the buyers are CFO offices, not automation hobbyists. The MCP connector list (Snowflake, Slack, GitHub, Google Workspace, HubSpot) is sensible and the SAFE framework's determinism claims address the standard objection to LLM agents in finance. But everything I could test without a sales call ended at the free Developer tier's 240 run minutes per month — enough to validate a robot, not to operate one.

What it does not do

It no longer serves the audience this listing was written for. There is no self-serve team plan with published pricing; the free tier is an experiment tier (240 minutes, one workspace, two processes); the open-source community edition, forum and public roadmap are effectively gone. Small teams and solo automators are outside the target: the per-agent-per-day Team Edition figure ($15/agent/day on Snowflake) turns into thousands per month for any meaningful agent fleet, and Enterprise is quoted through discovery calls with first-year totals in the tens of thousands per independent trackers. The Python openness is half-real now — the libraries survive, the governance surface requires the commercial platform. Vendor performance claims ("90%+ automation rates") come from the vendor's own case material and I would demand reference customers before believing them in a procurement process. And for pure open-source Python RPA, the honest alternatives today are the surviving open-source tools — Playwright-based stacks, Tagui, or plain Python automation on your own scheduler — not this lineage.

Verdict

Treat this entry as a tombstone with a pointer: Robocorp, the open-source Python RPA platform this listing describes, was acquired and discontinued as a standalone product, and what remains is Sema4.ai — a credible, enterprise-focused AI-agent platform for document-heavy finance work that runs inside Snowflake or your cloud account, priced through sales conversations above its free and per-minute tiers. It is rated 2.5 on my rubric: core functionality for the enterprise back-office case is real and thoughtfully engineered, but the discontinuation of the original product, the stalled open-source tooling under a commercial license, the pricing opacity above the free tier, and the mismatch with this listing's audience pull the score down hard; value is unprovable without a quote, usability favors Python-capable teams, support is enterprise-tier, and reliability signals are mixed — an experienced engineering lineage on one side, an orphaned community and a forum warning to "search for another solution" on the other. If you are an enterprise with finance workflows on Snowflake, Sema4.ai merits a discovery call. If you came here for free Python RPA, look elsewhere.

Sources

• https://sema4.ai
• https://robocorp.com/pricing
• https://unsubbed.co/tools/robocorp
• https://automationatlas.io/tools/sema4-ai
• https://recatools.com/ai-directory/sema4-ai
• https://trivista.com/ai-labs-apps-index/tools/robocorp-sema4-ai-automation-lineage
• https://github.com/robocorp/rcc
• https://github.com/robocorp/robocorp
• https://forum.robotframework.org/
• https://sema4.ai/pricing
• https://marketplace.snowflake.com