- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- About licensing
- Community plan
- Flex: Licensing plan framework
- Activating your Enterprise license
- Upgrading and downgrading licenses
- License migration
- Requesting a service trial
- Assigning licenses to tenants
- Assigning user licenses
- Deallocating user licenses
- Monitoring license allocation
- License overallocation
- Licensing notifications
- User license management
- Tenants and services
- Accounts and roles
- AI Trust Layer
- External applications
- Notifications
- Logging
- Data Export
- Testing in your organization
- Troubleshooting
- Migrating to Automation Cloud
Community plan
A free licensing plan for individuals and small organizations, giving direct sign-up access to the UiPath agentic platform with a fixed set of licenses.
Feature availability depends on the cloud platform that you use. For details, refer to the Feature availability page.
The Community plan is a free licensing plan that gives you access to the UiPath® agentic platform. It belongs to the Unified Pricing licensing model, and it is designed for individual developers, builders, and automation enthusiasts.
Two characteristics distinguish it from the other free plan. The Free plan reaches an organization only when a trial or paid plan expires, whereas the Community plan is available through direct sign-up at cloud.uipath.com. The Community plan also carries a fixed set of licenses that cannot be increased, alongside a monthly pool of Credits shared across the capabilities in use.
For a comparison with the paid plans, see Unified Pricing: Licensing plan framework.
Eligibility and commercial terms
The Community plan is available at no cost to individuals and organizations that meet the eligibility criteria set out in the Community Agreement.
The Community Agreement sets out the full terms of use.
The plan has no time limit. Its underlying license runs for 12 months and renews automatically, so the expiry date on the Licenses page moves forward each term.
Existing Community organizations on Flex licensing are a separate case. They keep their current user and robot licenses, and they already have access to the agentic capabilities through the monthly Credits pool. Automatic migration of those licenses to the Community plan is planned in the near future. The entitlements of the Flex Community Plan are described in Flex: Licensing plan framework.
Included licenses
A Community organization has one tenant, one Pro user, one Plus user, and one Unattended Robot. The two user licenses differ only in their access to Studio.
| License | Access |
|---|---|
| Pro | Studio, StudioX, Attended Robot, Apps, Action Center, Task Capture, Agent Builder, Document Understanding |
| Plus | StudioX, Attended Robot, Apps, Action Center, Task Capture, Agent Builder, Document Understanding |
Development capability is otherwise unreduced. Studio Web is available to both licenses, and the Pro license adds Studio on the desktop with its full feature set:
- Object Repository
- Remote debugging and conditional breakpoints
- Workflow Analyzer
- Coded workflows
- Source control through Git, Subversion, and Team Foundation Server (TFS)
Orchestration is similarly unrestricted in scope. Maestro supports Flow, Business Process Model and Notation (BPMN), and Case Management, with a monthly execution limit.
Individual services carry reduced throughput or volume rather than being withheld, and identity resources are capped at the organization level. Both sets of figures are listed in Community plan breakdown.
Services enabled per tenant
Maestro, Document Understanding, and IXP are licensed at organization level, yet each becomes usable only on the tenants where it is enabled. A service that is licensed but absent from a tenant therefore indicates an enablement gap rather than a licensing one. Tenant service enablement is covered in Managing tenants.
How Community Credits work
Consumption on the Community plan is not metered service by service. Instead, the organization receives a monthly Credits allowance, resetting at the start of each month and divided into two independent pools.
| Pool | Covers |
|---|---|
| Monthly Pool | Agent Development, Coding Agent, Conversational Agents, Context Grounding, ScreenPlay Development, Healing Agent, UI Automation, Serverless Execution, and Integration Service |
| Delegate and Autopilot | Delegate and Autopilot only |
Because the pools are independent, consumption against one never draws down the other. Delegate and Autopilot therefore keep working when the Monthly Pool is empty, and the reverse also holds.
Consumption appears on the Licenses page, under Consumables, as the percentage of each allowance that remains. The figure is organization-wide rather than per tenant.
An exhausted pool recovers at the next monthly reset. Two other routes exist: a model of your own, which moves AI and agentic workloads off the pool entirely, or an upgrade to a paid plan.
A model of your own is the most effective way to reduce consumption, because agent runs against UiPath-hosted models are the largest single draw on the pool. Setup is described in Configuring LLMs.
The AI and Agentic usage pool that paid Unified Pricing and Flex plans provide is a separate entitlement, and it is not part of the Community plan. It is described in AI and Agentic usage pool.
Capabilities not included
The following capabilities are unavailable or reduced on the Community plan.
| Capability | Availability |
|---|---|
| AI Center | Not available |
| Automation Cloud Robots (VM-based) | Not available. Unattended executions run through Serverless Execution or the included Unattended Robot on a machine of your own. |
| Automation Hub | Not available |
| Insights | Not available |
| Process Mining | Not available |
| IXP | Partially available. Generative Extraction for unstructured and complex documents and Document Understanding are included. Communications Mining is not. |
| UiPath Support | Not available. Community organizations are supported through the UiPath Community Forum. |
Platform behavior specific to Community
Five platform characteristics differ from the paid plans and shape how a Community organization can be operated.
- Release timing: Community organizations receive platform changes first. A change reaches Community when its release notes are published, and Enterprise organizations typically follow between one hour and 14 days later. See Feature rollout.
- Data residency: The organization is provisioned in the European Union. It stays there after a self-serve purchase; when you upgrade to an Enterprise license, you can choose the region. See Data residency.
- Audit log retention: Entries are kept approximately 30 days, against two years on Enterprise.
- Consumables Center: Not available. Credits consumption appears on the Licenses page instead.
- Dormant organizations: An organization that stays inactive is deleted automatically, after notification. See Dormant data deletion.
Upgrading from Community
An upgrade replaces the fixed license counts and the Credits allowance with the entitlements of the plan you upgrade to, and it is the only route to additional users or robots. After a self-serve purchase, the organization stays in the European Union; with an Enterprise license, you can choose the region.
Two paths lead off the Community plan from the Licenses page: a self-serve purchase, or activation of an existing Enterprise license code. Both are covered in Purchasing a plan and Upgrading and downgrading licenses.