An open-source RPA studio — free, without a subscription
A .NET workflow designer, an AI agent that builds robots from a spec, headless runs. Apache-2.0 and sources on GitHub: the studio, the runner and the orchestrator are free forever.
Open source Free forever Apache-2.0
A workflow designer on .NET and Workflow Foundation. An AI agent reads the spec and assembles the robot, the runner executes it without a GUI. Studio, runner and orchestrator are free; licence and sources are open. There is no vendor cloud: everything runs on your machines.
Apache-2.0 · no sign-up, no keys · no lock-in to our infrastructure · Windows 10/11 · .NET Framework 4.7.2
Start with three commands
git clone https://github.com/FreeAiSoft/AiRpa.git
cd AiRpa
dotnet buildIf it does not build, that is our defect — not an installation quirk.
Project goals
Four goals that drive our decisions — and that you can hold us to.
Goal 1
An open-source RPA studio
The designer, the runner and the orchestrator live in a public repository under Apache-2.0: you can read the engine, build it, change it and fix it yourself — no vendor permission needed.
Goal 2
The robot is not tied to the project's infrastructure
The output is plain dll and exe files: you can invoke them from any orchestrator, scheduler or CI, not only from ours. Switching orchestrators means changing the call, not rewriting the robot.
Goal 3
A studio with no dependency on external infrastructure
No vendor cloud, no licence server, no mandatory connection: the studio runs on your machines and inside your own environment.
Goal 4
End-to-end automation of robot development
Anything the agent can do, the agent should do: from spec to a finished robot — requirement parsing, the model, the package, the run, the report and the fixes that follow.
Open source, not “source available”
Openness here is not a word on a banner: it is four verifiable facts.
Apache-2.0
The licence text sits in the repository as LICENSE: commercial use, modifications and forks are allowed, with an explicit patent grant.
Public repository
Code, history, sample projects and documentation in one place. You do not have to ask a sales manager for a link.
Price 0
No fee for the licence, for a run or for the number of machines — neither today nor in a year. The page markup carries the same zero price.
Immutable package
A robot package is checked by SHA-256: the same version with different content is never overwritten.
Free is not a trial
No “30 days”, no “up to three robots”, no “free for personal use only”. The boundaries are stated upfront so that they do not change later.
| Item | How it works |
|---|---|
| Studio, runner, orchestrator | free forever: no limit on robots, machines or runs |
| Sign-up, keys, internet | not needed: clone, build, run; execution works offline |
| Implementation, training, support | a separate service — write to us if you need someone to do the work |
| Our infrastructure | not needed: the studio, runner and orchestrator run on your machines; there is no vendor cloud and no licence server |
| What you will never get | a licence server, telemetry with robot data, forced “subscription” updates |
No lock-in to our infrastructure
The studio does not need our cloud and does not ask permission to run: no vendor server, no mandatory connection, no “licence renewal” that may fail.
Works offline
The studio and the runner live on your machine, an execution needs no network, and there is no licence check that calls home — because there is no licence check at all.
Runs anywhere
Windows 10/11, your own server or your own cloud: the only requirement is .NET Framework 4.7.2, which the system already has.
Leaving costs nothing
The runner is all a machine needs; the project and the robot packages are your files, not records in our service. You never have to ask us for them.
Three differences from vendor platforms
The code is open and free
No licence fee, no subscription, no per-run charge. You can read how the engine works and fix it yourself.
What exactly is openThe AI agent builds from a spec
The agent parses requirements, asks about ambiguities and edits the workflow model — with an edit log.
How the agent edits a workflowSources and runs stay with you
The robot project, its sources and the headless run live on your machine: nothing is taken away, nothing blocks an offline run, and nothing ties you to our infrastructure.
Orchestration without a GUIFrom spec to report
Step 1
Spec
docx, pdf or xlsx: the agent splits it into items and collects ambiguities as questions.
Step 2
Workflow model
An activity tree in C# and Workflow Foundation: edited by hand or by the agent, every change is visible.
Step 3
Robot package
Version, content and SHA-256: the package is immutable and cannot be swapped unnoticed.
Step 4
RpaRunner.exe
A run without a GUI: an exit code and a step report instead of “take a look yourself”.
The “spec item ↔ workflow element” trace shows what is actually implemented and what is still a question — the same trace becomes the acceptance baseline.
What the studio does
AI agent from a spec
Reads the requirements, asks questions and assembles the robot by editing the model.
Read moreOrchestrator without a GUI
Schedules, queues and statuses on a server, without a desktop shell.
Read moreRunner and robot package
Headless runs with exit codes and a report; the package is verified by SHA-256.
Read moreMCP for external agents
Studio tools are available to an external agent over an open protocol.
Read moreAll eight capabilities — including C# activities and NuGet libraries.
How we differ from UiPath, Power Automate and OpenRPA
| AiRpaStudio | UiPath | Power Automate | OpenRPA | |
|---|---|---|---|---|
| Licence price | 0 | per price list | per price list | 0 |
| Mandatory subscription | no | yes | yes | no |
| Sources with the customer | yes, Apache-2.0 | no | no | yes |
| Run without a GUI | yes, RpaRunner.exe | yes | yes | limited |
Data about other platforms comes from public vendor pages as of this page's update date. Figures, links and dates are on the Comparison page.
First robot in 30 minutes
- Clone the repository and build the solution:
dotnet build. Windows 10/11 and .NET Framework 4.7.2 are required. - Open the sample project in the studio or in Visual Studio 2022/2026 — it builds with no manual edits.
- Run the scenario through
RpaRunner.exeand take the exit code with the step report.
If something does not build
That is our defect, not an installation quirk. Open an issue in the repository or write to us — we fix it and mention it in the release notes.
Who it fits and who it does not
It fits
- an RPA engineer who wants a C#/.NET designer of their own;
- an IT department that needs sources and runs to stay in-house;
- an integrator building robots for clients without licence fees;
- a team where specs are written by non-developers: the agent asks about ambiguities.
It does not fit
- when you need a vendor SLA and a one-click boxed installer;
- when you need a cloud platform with ready-made connectors to everything;
- when nobody on the team can build a .NET project.
What is already verified
The sample builds with no edits
The project from the repository builds and runs in both the studio and the runner — no “fix the path in the config” step.
Docs from the same repository
Product pages and code live side by side: the description does not lag behind behaviour at release time.
The package is immutable
The same package version with different content is never overwritten: verified by SHA-256.
Questions people ask first
LICENSE file and on the Licence page; there is no warranty, it is provided “as is”.dotnet build; Windows 10/11 and .NET Framework 4.7.2 are required.RpaRunner.exe; there is no licence server and no mandatory outbound calls.Take the sources, not a subscription
The repository is open: code, licence, samples and documentation in one place. Public builds arrive with the first release — for now the studio is built from source.
Apache-2.0 · 0 · no sign-up