Community
For personal setups, homelabs and early automation.
$0
Core automation
- Open source under the MIT license
- Run automation from the UI and API
- Execution history and logs
- Project-level access control
- Documentation and community support
Run Semaphore UI in your own environment. Start free, choose Pro for team automation and support, or Enterprise for business-critical operations.
All plans are self-hosted
For personal setups, homelabs and early automation.
$0
For teams running and scaling infrastructure automation in production.
From $20/ month
Prefer to pay by bank transfer?Continue in Customer Portal →
For governed, highly available or business-critical infrastructure.
Custom
Trusted by thousands of teams
#1
Ansible UI for Windows & Linux
14K+
Stars on GitHub
6M+
Pulls on Docker Hub
100K+
Installations
Taxes calculated at checkout.
Buy nowFlexible terms for larger scale, complex deployments, and specific licensing needs.
Use this quick guide before going into the full comparison.
Choose the right Semaphore UI plan based on automation, security, integrations, and production needs.
Swipe to compare all three plans →
| Feature |
CommunityStart for free
|
Enterprise
|
|
|---|---|---|---|
| Automation & execution | |||
| Running Ansible, Terraform, OpenTofu, Shell, Python and PowerShell from one platform | |||
| Inventory management (Static, File-based, Dynamic) | |||
| Reusable Task Templates | |||
| Scheduled Tasks (Cron) | |||
| Reusable automation configuration (Variable Groups) Reusable sets of environment variables and secrets that can be shared across task templates. | |||
| Distributed execution (Global Runners) | |||
| Isolated execution (Project Runners) Execution agents that run tasks close to private networks, remote sites or restricted infrastructure. | |||
| Terraform/OpenTofu HTTP backend Stores Terraform or OpenTofu state in Semaphore UI through the standard HTTP backend. | |||
| Tag-based runners routing | |||
| Docker execution Runs each task in an isolated Docker container instead of directly on the runner host. | |||
| Kubernetes execution Runs each task in an isolated pod in your Kubernetes cluster. | |||
| Workflows Connects task templates into a visual sequence with conditions between steps. | |||
| Access control | |||
| Project-level access control | |||
| Role-based access control (RBAC) | |||
| Two-factor authentication (TOTP) | |||
| LDAP / Active Directory login | |||
| SSO via OIDC (Okta, Entra ID, Keycloak, Google etc.) | |||
| Role mapping from IdP groups | |||
| Custom Roles | |||
| Granular task-level permissions | |||
| Secrets & credentials | |||
| Centralized credential store (Key Store) | |||
| Encrypted credentials with runtime injection | |||
| HashiCorp Vault secrets storage | |||
| OpenBao secrets storage | |||
| AWS Secrets Manager secrets storage | |||
| Azure Key Vault secrets storage | |||
| Devolutions Server secrets storage | |||
| Audit | |||
| Task History | |||
| Activity History | |||
| Server Log | |||
| Task Execution Summary | |||
| File-based Log Export | |||
| API & integrations | |||
| REST API | |||
| Webhook Automation Triggers | |||
| Git repositories (GitHub, GitLab, Bitbucket) | |||
| Notifications (Email, Slack and Microsoft Teams, etc.) | |||
| MCP server for AI-based automation workflows | |||
| Support | |||
| Support SLA | 48h business days | Custom SLA options based on your needs | |
| Feature request review | Community-driven | Standard review | Prioritized review |
| Onboarding help | |||
| Upgrade help | |||
| Configuration help | |||
| Custom development | |||
| Migration assistance | |||
| Licensing | |||
| High Availability | |||
| Multi-instance license | Up to 3 instances | ||
| Air-gapped (offline) license | |||
Use the full Pro experience with your own infrastructure and data.
Choose a tier based on the infrastructure you manage. For Ansible, use the managed-node count. For Terraform and OpenTofu, use the managed-resource count. If you use both, choose a tier that covers both counts. Every tier includes both allowances, the same Pro features and business-time support, plus one Pro user, one Project Runner and one instance. You can add more users, runners and instances as needed.
Each distinct node managed with Ansible and each distinct Terraform or OpenTofu resource managed through Semaphore UI counts once per monthly usage period. Repeat runs do not increase the count. Objects present only in an inventory or state file do not count. Usage periods start on your license start date and reset monthly, including on annual plans.
We count the underlying nodes Semaphore UI actually manages. Inventory entries and refreshes alone do not increase usage. A temporary VM counts if it is managed during the usage period, even if it is later removed. For example, managing 50 VMs and then 50 different replacements in the same period counts as 100 distinct nodes. If your fleet changes rapidly, Sales can help you choose a tier based on a representative usage pattern.
A Pro user is someone who creates, edits or administers Pro automation. People limited to running or viewing existing automation may not need a Pro seat. For mixed or custom roles, ask Sales to confirm the required seat count.
Count the execution agents your setup needs to run tasks near private or isolated infrastructure. Each runner can execute multiple tasks, with parallel execution controlled by its concurrency setting. Global Runners remain available in Community and do not count as paid Pro runner add-ons.
Every Pro license includes one instance, typically production. You can purchase up to two additional staging, test or development instances for the same team and environment, using the same license key. Size capacity using the highest monthly managed-node count and the highest monthly managed-resource count among those instances. Independent production environments require separate licenses.
Purchased Pro user and Project Runner quantities are enforced in Semaphore UI. The instance quantity limits how many installations can use the license key. Infrastructure usage is currently reviewed manually, and exceeding a managed-node or resource allowance does not automatically stop automation. Contact Sales if you are approaching a limit or need help assessing usage.
You can increase capacity or add Pro users, Project Runners and instances during your paid term. Make available changes in the Customer Portal, or contact Support if the change you need is not shown there. Purchased capacity and add-ons cannot be reduced during the current term. You can choose a smaller configuration for your next term.
Monthly billing charges your configuration each month and is paid by card only. Annual billing charges once for the year at a lower price, with payment by card or invoice. For the starting configuration, that is $20 per month or $199 for one year, before applicable tax.
Prices exclude applicable tax. Enter your billing details and a valid Tax ID or VAT ID during checkout. Our billing partner Paddle calculates the tax and displays the final amount before you confirm the order. Reverse charge may apply to an eligible cross-border business purchase with a valid VAT ID.
For an annual Pro license, choose invoice at checkout in the Customer Portal. Our billing partner Paddle issues the invoice automatically. You can pay it by bank transfer within 30 days of the invoice date. Annual purchases can also be paid by card. Monthly purchases are paid by card.
Choose your configuration and billing period, then select Buy now to continue in the Customer Portal. Review your order and billing details before confirming. After payment is completed, your key is available under License Keys in the Customer Portal. Copy it into your self-hosted Semaphore UI installation to activate Pro.
Yes. Start a 30-day Pro trial in the Customer Portal and evaluate it in your own self-hosted environment. No credit card is required. To continue with a paid license, choose your configuration and complete checkout.
Your current terms remain in place through the end of your paid period. You can move to configurable Pro then or earlier if you choose. Some configurations may cost more than your previous plan, depending on the infrastructure capacity and team setup you need. Eligible existing customers may receive a transition offer. Check your options in the Customer Portal or contact Support.
One Pro license supports up to 500 managed nodes, 5,000 managed resources, 25 Pro users, 25 Project Runners and 3 instances. Contact Sales about Enterprise if you need higher limits, high availability, offline licensing, advanced access controls or a complex multi-team deployment. Pro uses published terms, and standard company, billing and tax documents may be supplied when available. Negotiated contracts or extensive vendor onboarding should be discussed with Sales as part of an Enterprise offer.
Choose Pro for everyday team automation, or talk to us about Enterprise requirements.