Model-agnostic agent platform
OpenHands is presented as an open-source, model-agnostic platform, so teams can choose how agents run and which model providers they use.
OpenHands
RevendiquerOpenHands is an open-source, model-agnostic platform for cloud coding agents that automates engineering workflows with web, CLI, terminal UI, and SDK access.
OpenHands at a glance
OpenHands is an open-source platform for cloud coding agents that helps teams automate engineering work in a controlled, model-agnostic environment. The product is positioned as a way to run agents securely and transparently while keeping control over deployment, access, and data.
Across the public site, OpenHands is described as usable locally, in hosted cloud form, or in self-hosted enterprise deployments. It supports individual developers, teams, and organizations that want agents to fix bugs, review pull requests, migrate code, triage incidents, and run scheduled or event-driven automations.
Core capabilities
Flexible deployment options
The product can run locally, in a hosted cloud environment, or in self-hosted and private VPC deployments, giving teams several operating modes.
Multiple interfaces and SDK access
OpenHands supports a web GUI, terminal UI, CLI, and SDK, which lets users interact with agents in different ways and embed them into other products or internal tools.
Automated engineering workflows
The enterprise pages describe isolated sandboxes, repository access, PR creation, and triggered runs from GitHub, Slack, Jira, or cron workflows.
Integrations and governance tools
The pricing and enterprise pages list GitHub, GitLab, Bitbucket, Slack, Jira, Linear, CI/CD, SSO, RBAC, and audit-related controls as part of the platform.
Practical use cases
Security issue remediation
Run agents that scan repositories, fix vulnerabilities, and open reviewable pull requests for engineering teams that want automated remediation with human review.
Pull request review
Use OpenHands to examine pull requests for quality, security, and best practices before changes are merged.
Code migration and modernization
Apply the platform to legacy modernization projects, including the COBOL-to-Java migration workflow described on the homepage.
Incident triage and follow-up
Trigger agents from GitHub, Slack, Jira, or scheduled jobs so they can investigate errors, summarize root causes, and post debugging output without requiring a laptop to stay online.
Team automation rollout
Give individual developers and teams a shared way to run automations locally or in the cloud, with organization controls when they need RBAC, audit logs, and budget guardrails.
Pros and Cons
Pros
- Open-source and model-agnostic, so teams can keep more control over where agents run and which providers they use.
- Multiple deployment choices, including local, hosted cloud, self-hosted, and private VPC options.
- Supports several interfaces, including web, CLI, terminal UI, and SDK access.
- Documented workflows cover bug fixing, PR review, code migration, and incident triage.
- Enterprise controls include RBAC, SSO, audit logs, and budget controls.
Cons
- Some feature details are only summarized at a high level on the public pages, especially around integrations and setup.
- The pricing page shows multiple deployment and plan options, but not all limits and operational details are spelled out publicly.
FAQ
How can OpenHands be deployed?
OpenHands offers a local open-source setup, a hosted cloud option, and an enterprise deployment path. The pricing page describes an open-source local version, a SaaS Individual plan, and an Enterprise plan with self-hosted or VPC deployment options.
Can I bring my own model provider or key?
The source describes OpenHands as model-agnostic and says teams can use their own LLM keys or choose provider access through OpenHands plans. The enterprise page also says it works with providers such as Anthropic, OpenAI, Bedrock, and others.
What kind of workflows does OpenHands support?
OpenHands can run agents in isolated sandboxes on a VM or in the cloud, and the enterprise page says automations can be triggered from GitHub issues, Slack messages, Jira tickets, or a schedule.
Which integrations and controls are documented publicly?
The public pages show web-based GUI, terminal UI, CLI, an SDK, Git integrations, Slack, Jira, GitLab, GitHub, Bitbucket, and some enterprise controls such as RBAC, SSO, audit logs, and budget controls. The source does not provide a complete integrations catalog.
Quick Facts
- Category
- Developer Tool
- Primary use
- Cloud coding agents for engineering automation
- Deployment
- Local, hosted cloud, self-hosted, and private VPC
- Interfaces
- Web GUI, terminal UI, CLI, SDK
- Notable workflows
- Fix vulnerabilities, review PRs, migrate code, triage incidents
- Domain
- openhands.dev