Enhans
Also known as: Enhans AI
An enterprise AI execution platform. An ontology layer gives agents business context, a customer built agent and workflow layer decides what happens, and ACT-2, the company's own computer use model, carries the work out by operating browsers and business systems directly where APIs fall short.
Enhans is an enterprise agentic AI company whose platform, AgentOS, is built to move companies from AI that analyzes to AI that carries out operational work inside the systems a business already runs.
AgentOS is organized as five layers. Pipeline Builder connects and prepares enterprise data, bringing databases, APIs and files into the platform. Ontology Manager turns that data into business meaning by defining entities, relationships, rules and terminology, and it does so in a separate ontology lake instead of modifying the customer's databases, so existing systems stay in place.
Agent Builder is where task specific agents are created and connected with tools, rules and conditions into execution flows, with the customer defining how agents operate, what information they may use, when actions fire and how exceptions are handled. App Builder turns results into dashboards, generated views and natural language interfaces. ACT-2 executes.
ACT-2 is the company's own computer use model and the distinctive part of the platform. Instead of depending on integrations, it operates browsers, SaaS platforms, admin panels, internal tools and operational portals directly, on the argument that many enterprise systems do not expose complete APIs. It maps a target system, performs the workflow in a controlled execution environment, saves successful action paths so repeated work does not have to be reasoned through again, and adapts when screens, fields or workflows change. It returns results, screenshots, change records and artifacts for each request, so a team can audit what happened and connect an action back to the decision behind it.
Alongside the build platform, the company sells CommerceOS, a set of specialized agents that can be taken individually. They are the Price, Promotion, SNS, QA, Brand Protection, Product Experience and AD agents, with published use cases pairing single agents to sectors such as ecommerce, fashion and food and beverage. The platform is also presented for defense, finance, heavy industries and manufacturing, with a published customer case in armed forces cost review.
Deployment is flexible. As well as cloud, AgentOS and ACT-2 can be deployed into infrastructure the customer manages, including on premises and private cloud, which the company positions as a differentiator against hosted computer use tools. The platform is listed on the Microsoft Azure Marketplace as a quotation based offering, and no price is published. The action model runs on the company's own stack, with no customer choice of underlying model, and there is no published security certification, access model, developer API or SDK.
Vendor details
Canonical URL
https://www.enhans.ai
Category
Enterprise operations agent
Subcategory
Enterprise AI execution operating system
Funding status
Independent, headquartered in Seoul with a San Francisco presence, led by chief executive Seung-hyun Lee, with an engineering team drawn from UC Berkeley, Tsinghua, Seoul National University, and Peking University. Founded in 2024, originally operating in commerce under the name ViralPick, and has raised roughly ten million dollars from about fifteen investors including Naver Ventures, the Industrial Bank of Korea, Infocomm Media Development Authority of Singapore, and Plug and Play, with a strategic Naver Ventures investment announced in April 2026. Reports adoption by more than thirty global enterprises including Samsung and Philips, operations in over fifty countries, membership in Microsoft's startup programs with an Azure Marketplace listing, and selection as the only Korean company in a Palantir startup fellowship.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
AgentOS turns fragmented tools and processes into one operating system for AI, using an ontology layer for business context and ACT-2, the company's own computer use model, to execute across an enterprise's systems, interfaces, and channels. It spans commerce marketplaces and operational systems across manufacturing, finance, healthcare, logistics, and more, is listed on the Azure Marketplace, and is delivered with a forward deployed engineering model.
In practice
Your AI can analyze the business but still hands every action back to a person to execute. Enhans's ACT-2 action model carries decisions through to completion by operating browsers and business tools across your systems, so agents act while people decide.
Raw material, currency, and logistics costs are quietly eroding margin before anyone reacts. Enhans tracks those shifts against product level margin and acts before they eat into profit.
Your commerce operation runs pricing, promotions, ads and brand protection by hand. Enhans offers prebuilt CommerceOS agents for those jobs, such as the Price, Promotion, AD and Brand Protection agents, and you can take them one at a time.
Sources & related URLs
Related / legacy domains
Agentic Index coverage score
8.0 / 14 capabilities · 57%
| Integrations & Tool Calling | Partial |
|---|---|
|
There is no named third party system, such as an ERP, CRM, marketplace, data warehouse or collaboration tool. Data comes in by category, from databases, APIs and files, and Enhans names industries instead of systems. Agents take authenticated action in outside systems through ACT-2, which operates browsers, SaaS platforms, admin panels and operational portals. Pipeline Builder connects and prepares enterprise data, bringing databases, APIs and files in so the data is ready for execution, and it reads from those sources. App Builder sends results to dashboards and views inside the platform, not to an outside system. There is no named integration catalog and no support for custom tools. Agent Builder connects agents with tools, rules and conditions but names no tool, says nothing about how one is added and has no tool interface. Enhans drives interfaces instead of publishing connectors, because many enterprise systems do not expose complete APIs. Sourceenhans.ai/agent-os Pipeline Builder and Agent Builder sections, enhans.ai/act-2 API-limited system coverageread 2026-09-14 |
|
| Workflow Orchestration | Full |
|
AgentOS runs work in several steps across several agents. Five modules sit in order on one execution path. Pipeline Builder prepares data, and Ontology Manager defines business meaning and relationships. Agent Builder designs agents and execution flows, and App Builder connects business meanings to operational interfaces. ACT-2 then carries out the business work. Enhans describes AgentOS as connecting "enterprise data, ontology, agents, workflows, views, and action in one execution architecture," with each layer made explicit. Enhans presents running several agents together as a differentiator. AgentOS lets multi agent systems operate according to enterprise logic, so enterprises can build and connect agents for specific business purposes that run within real workflows and operating logic. In the market monitoring use case, monitoring agents run over Pipeline Builder, ontology management and workflow logic, with Price Agent, Social Media Agent and Brand Protection Agent as the example agents on one flow. The customer composes the flows. In Agent Builder, a customer builds task specific agents on top of enterprise data and ontology, then connects them with tools, rules and conditions into workflows for real operations. The customer defines how agents operate, what information they can use, when actions fire and how exceptions are handled. Rules and conditions written for each flow give the customer control over branching. Enhans names no runtime, BPMN or graph notation, versioning, retry or concurrency behavior, and does not say what happens when a step fails in a flow with several agents. Sourceenhans.ai/agent-os architecture layers, differentiators and use cases, FAQ Q5read 2026-09-14 |
|
| Knowledge Grounding & RAG | Full |
|
Ontology Manager, a product module, turns data into business meaning as a graph. It defines entities, relationships, rules and terminology so AI can work with real enterprise context. Together these form a semantic layer that agents query, instead of context assembled for each run. The layer persists. AgentOS builds a separate ontology lake while keeping existing systems in place, using Pipeline Builder to store the required data separately and organize it for AI instead of modifying enterprise databases directly. Pipeline Builder fills it from databases, APIs and files, and agents query it at run time. Because it is a store and not a prompt, it scales past a context window. Enhans argues that ontology gives AI the structure it needs to work with enterprise context. Without it, AI may generate plausible responses, but it is far harder to make them consistent, explainable and operationally useful. The structure is maintained, not built once. Ontology Manager generates about ninety percent of the ontology automatically from source system data, and forward deployed engineers complete the rest on site. The ontology describes the customer's business, not state an agent keeps about its own work. Enhans does not say how agents query the ontology or what provenance an answer carries, and names no retrieval mechanism, query interface, embedding approach or citation surface. Sourceenhans.ai/agent-os Ontology Manager, ontology lake and FAQ Q3read 2026-09-14 |
|
| Human Oversight & Guardrails | Partial |
|
Decisions stay with the customer, and the tagline is "you decide and our agents act." In Agent Builder the customer sets limits on agent autonomy at build time, defining how agents should operate, what information they can use, when actions should be triggered and how exceptions should be handled. ACT-2 runs through a "governed execution layer," so AI agents can take action without the customer giving up control over the execution environment. There is no step where a person reviews and approves an action. There is no approval queue, pending state or accept and reject action. There is no reviewer, risk threshold per action or escalation path to a named person, and no record of who approved what. Enhans does not say whether a person handles exceptions, and ACT-2's Adapt step runs fallback execution with no human in it. The execution layer is built to reduce human involvement, cutting the need to reason through the same workflow on every run so that high volume automation becomes more economically viable. Sourceenhans.ai/agent-os Agent Builder FAQ, enhans.ai/act-2 governed execution and adapt stepread 2026-09-14 |
|
| Security, Identity & Governance | Not documented |
|
There is no security attestation or access model for the platform. AgentOS can be deployed to match customer infrastructure and security requirements, and Enhans says enterprise AI must account for existing systems, security and infrastructure requirements. Both are about fitting what the customer already has, and neither says what Enhans itself does. There is no SOC 2, ISO 27001, auditor, report, trust center or compliance page. Enhans names no SSO, SAML or SCIM, and no RBAC, roles or permissions model. The site has no security, trust or compliance section, and its only legal link is a privacy policy. Enhans sells to large enterprises and defense customers, including through the Azure Marketplace. Sourceenhans.ai/agent-os deployment section and full navigation, enhans.ai/act-2 navigation and footerread 2026-09-14 |
|
| Observability & Auditability | Full |
|
Each ACT-2 run returns execution evidence. It returns results, screenshots, change records and artifacts for each request, so teams can audit what happened and connect execution back to the original decision. These four kinds of artifact come back with every run. The record covers the agent's own execution, request by request, not the health of the customer's operations. Screenshots and change records show what the agent saw and what it changed. Because ACT-2 operates interfaces instead of APIs, there is no system log to inherit, so the artifacts come from Enhans's execution layer, not from the systems being operated. Enhans presents this as a differentiator, setting its evidence and execution records against the limited verification of other tools. It describes enterprise automation as entering the required system, following the right process, completing the action and proving the result. It also says generic computer use does not scale, partly because teams need traceable records of what was executed. Enhans gives no retention period or export path, no admin view across users or agents and no alerting, and does not say where these records are stored or for how long. Sourceenhans.ai/act-2 execution evidence, comparison table and enterprise-execution framingread 2026-09-14 |
|
| Memory & State Persistence | Not documented |
|
Agents have no memory store, and Enhans names no scope, lifetime, retention period or purge path. A customer cannot find where agent memory lives or delete it for one customer without touching the ontology lake, which is the application's data model. There is also no store of facts that users maintain for the agent to consult. The persistent ontology describes the customer's business, its entities, relationships, rules and terminology, held in a separate ontology lake. Agents do not write state about their own work into it and read it back. The platform learns continuously across cycles, and that learning is absorbed into the product. ACT-2's Reuse step saves successful action paths and applies them to similar future tasks. Its reusable workflow execution converts successful task paths into workflows that can be used again, reducing the need to reason through the same workflow on every run. The agent writes something lasting from its own experience, but it becomes a procedure the platform replays, not context the agent reads when it decides. Sourceenhans.ai/act-2 reuse step and reusable workflow execution, enhans.ai/agent-os ontology layerread 2026-09-14 |
|
| Deployment & Data Residency | Full |
|
AgentOS can be deployed on premises or in private cloud, matching customer infrastructure and security requirements. These are the customer's own environments, not regions Enhans runs, so the software runs where the customer is. ACT-2, the part that touches the customer's systems, can also be deployed in controlled environments, including on premises or infrastructure the customer manages, where execution control and system access matter. Enhans sets this flexible deployment against hosted tools that execute in the cloud by default. AgentOS builds a separate ontology lake while keeping existing systems in place. It stores the data it needs separately instead of changing enterprise databases, with no rip and replace. Because its data layer sits beside the customer's systems, it can sit inside the customer's estate. For the default cloud there is no region list, residency commitment or data location statement. There is no installation or architecture documentation for an on premises deployment. Delivery is quotation based, so the boundary is negotiated for each customer instead of being specified up front. Sourceenhans.ai/agent-os built for enterprise deployment section, enhans.ai/act-2 deployment comparisonread 2026-09-14 |
|
| Prebuilt Agents, Templates & Packs | Full |
|
A named set of prebuilt agents ships under CommerceOS. AgentOS itself is not a catalog of prebuilt agents. It is the platform where enterprises connect their data, define business meaning and build task specific agents. Enhans says prebuilt agents serve narrow predefined tasks while AgentOS gives enterprises the tools to build their own, and its four worked scenarios are representative scenarios, not fixed product packages. CommerceOS offers seven specialized AI agents with their own pages and durable URLs. They are Price Agent, Promotion Agent, SNS Agent, QA Agent, Brand Protection Agent, Product Experience Agent and AD Agent. Each is a whole product that works without the others, and pricing, advertising, brand protection, social posting, quality assurance and review analysis are separate commercial functions. Customers can take the agents one at a time. The market monitoring scenario uses Price Agent, Social Media Agent and Brand Protection Agent as its example agents, and industry pages pair single agents with single verticals, such as Ecommerce with QA Agent, Fashion with SNS Agent and F&B with Brand Protection Agent. AgentOS is sold as a build platform and CommerceOS as a packaged set. There is no entitlement, install or enable action, and no pricing for each agent. Sourceenhans.ai/agent-os not-a-catalog statement and use cases, enhans.ai/act-2 navigation CommerceOS specialized agent listread 2026-09-14 |
|
| Triggers & Channel Coverage | Partial |
|
In Agent Builder a customer defines when actions should be triggered, alongside how agents operate, what information they can use and how exceptions are handled. With trigger conditions written for each agent, the platform runs on events instead of by hand. In the market monitoring use case, monitoring agents watch market signals in real time and connect insights to an operational response. The use case is built with Pipeline Builder, ontology management, workflow logic and dashboard views. Enhans does not say what can fire a trigger. It names no event source, such as a webhook, schedule or inbound API call, a message queue or subscription to a system's change events, or a mailbox, chat channel or ticket queue. Outputs go to dashboards, generated views and natural language interfaces. Sourceenhans.ai/agent-os Agent Builder FAQ and market monitoring use caseread 2026-09-14 |
|
| Model Flexibility & Routing | Not documented |
|
ACT-2, Enhans's own computer use model, runs the actions, and the customer cannot choose or route models. There is no model selector, admin entitlement or model setting for an agent or workflow, no disclosed routing and no way to bring your own key or model. In Agent Builder a customer chooses agents, tools, rules and conditions, but not the model. ACT-2 is the platform's headline technical asset, with its own product page, subdomain and benchmark claim. Enhans trained the action model itself and keeps the stack fixed, so the customer gets no choice. Enhans names its own model but no provider, family or version for any other part of the platform. It does not say which models run the reasoning, planning and language layers across Agent Builder, App Builder and the ontology work, and it has no subprocessor list. A customer can learn what drives their screens but not what reads their ontology. Enhans says ACT-2 ranks in the global top five on Online-Mind2Web alongside Google, OpenAI and Anthropic. Those three labs are benchmark peers, not models a customer can use on the platform. Sourceenhans.ai/act-2 in-house model and benchmark claim, enhans.ai/agent-os Agent Builder configuration surfaceread 2026-09-14 |
|
| APIs, SDKs & MCP Extensibility | Partial |
|
AgentOS has no public API, SDK or developer surface. There is no developer section, API reference, documentation portal or docs subdomain, and no agent card, webhook or CLI. The builders are authoring surfaces inside the product. The interfaces point outward. Pipeline Builder brings databases, APIs and files into AgentOS, consuming other systems' APIs, and ACT-2 drives external systems the same way. Neither lets an outside caller drive AgentOS. Enhans mentions MCP based integration support alongside its deployment options but does not say which way it runs. An MCP server would expose AgentOS to a customer's assistants, while an MCP client would only consume tool servers. The offering is quotation based. Sourceenhans.ai/agent-os and /act-2 navigation and Pipeline Builder, Microsoft Marketplace listing unreadread 2026-09-14 |
|
| Testing, Debugging & Optimization | Not documented |
|
Customers have no way to test or evaluate the agents. There is no evaluation harness, scored test cases or golden set, no judge, regression suite or A/B comparison between agent configurations, and no release quality gate or loop that measures the deployed agent against outcomes. There is no debugging surface either. Agents built on the ontology automate decision domains including cost analysis, audit and simulation. That simulation models the customer's business, such as a pricing scenario or a cost structure, not whether the agent's work was correct. Enhans says ACT-2 ranks in the global top five on the Online-Mind2Web computer use benchmark, alongside Google, OpenAI and Anthropic. The benchmark measures the underlying action model, not agent behavior on a customer's work, and customers cannot run it against their own workflows. ACT-2's execution evidence and its checks and confirmations in processes with several steps show what happened on a given run. They do not show whether a change to an agent made it better. Sourceenhans.ai/act-2 execution evidence and comparison table, enhans.ai/agent-os use casesread 2026-09-14 |
|
| Browser & Computer Use | Full |
|
ACT-2 is the enterprise computer use layer for AgentOS, covering the browser and desktop applications. It is the AI execution layer that turns decisions into actions across browsers, business systems and operational tools, connecting to browsers, SaaS platforms, admin panels, internal tools and operational portals. It operates browsers and business tools through a governed execution layer. The agent navigates and performs the workflow in a controlled computer use environment that Enhans runs. ACT-2 is Enhans's own model, not another company's engine, and Enhans contrasts it with hosted CUAs built for help with individual tasks. Business tools change screens, fields and workflows over time. When a screen, field or workflow changes, ACT-2 can support fallback execution and workflow updates. Enhans built it for limited API coverage, working across tools and portals where APIs are incomplete, unavailable or impractical, since many enterprise systems do not expose complete APIs. The execution cycle has four steps. In Explore, ACT-2 maps the target system and identifies the actions needed. Execute then runs the workflow in the controlled environment, followed by Reuse and Adapt. Sourceenhans.ai/act-2 computer use layer, core capabilities and execution cycleread 2026-09-14 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Not public. Quoted through enterprise engagement, with an Azure Marketplace listing but no public rates.
Not published. AgentOS is sold as a customized, quotation based service, and no seat, agent or usage unit appears, so whether the enterprise subscription is scoped to agents, workflows or usage is not stated.
What is public
Only the sales motion is published, on the website and in the marketplace alike. The website's only call to action is a contact form routed through a short qualification sequence, and there is no pricing page anywhere in a large navigation. The Azure Marketplace listing is transactable in principle but publishes no rate, and describes itself as a base public offer for a quotation based service.
Billing mechanics
Not disclosed. Paid access is a quoted enterprise engagement delivered with forward deployed engineering, and whether the subscription is scoped to agents, workflows or execution volume is not published.
Cost watchouts
Broad rollouts across many agents, workflows, and marketplaces can raise cost, and forward deployed delivery may be a significant services component.
Variable cost rationale
No billing axis, overage rule, included quota or unit of sale is published on the website or in the marketplace listing. Nothing documented makes a bill grow within a term, and nothing documented caps it. Paid access is a quoted enterprise engagement. One signal points to metering underneath. ACT-2 is pitched on the economics of repetition, reducing the need to reason again through the same workflow on every run so that high volume automation becomes more economically viable. That is the argument a vendor makes when consumption is metered, but no per run rate is published.
Additional watchouts
Two cost drivers are visible in the delivery model, and neither is priced publicly. First, ontology construction includes on site forward deployed engineering, so the first year cost is a platform fee plus an implementation engagement whose size depends on how much of the ontology the automated generation covers in a given estate. Automated generation covers roughly ninety percent, and the residual is the negotiable part. Second, ACT-2 is a computer use execution layer, pitched on repetition becoming cheaper because successful action paths are reused rather than reasoned through again. That framing implies a per run or per reasoning cost underneath, which is never stated. The unit of consumption, what counts as a run, and whether reused paths are billed differently from first executions are not published. On premises and private cloud deployment is offered, with its own commercial terms, which are not published.
Sales call required
Yes, required for paid access
Free / trial
None published
Lowest paid plan
Not published
Key ambiguities
Enhans's Microsoft Azure Marketplace listing is the only transactable surface, and it publishes no rate. The listing describes AgentOS as a customized, quotation based service and itself as a base public offer with transaction scope agreed separately, so the marketplace is a procurement route rather than a price. No tier, unit of sale, seat rate, agent rate or usage meter appears on the website. Delivery is forward deployed. Ontology Manager automatically generates roughly ninety percent of the ontology, and Enhans Forward Deployed Engineers complete the remainder on site, so a services component is part of every deployment and is not separately priced either.
Related vendors
- 11th Estate — Agentic platform whose AI engine scans markets, matches an…
- Abacum — FP&A platform for growing companies whose AI Modeler builds, edits…
- Adopt AI — AI native accounting and bookkeeping firm whose agents run…
- Aera Technology — Decision intelligence platform where an always on agent executes…
- Akro AI — On premise operational intelligence that automates document heavy…
- alfred_ — AI executive assistant that triages the inbox overnight and scores…
Alternatives to Enhans
The closest documented capability profiles to Enhans among enterprise operations agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Kenmei7.0 / 14Adds documented Security, Identity & Governance
- RiskFront AI5.0 / 14A lighter documented profile than Enhans
- Variance10.0 / 14Adds documented Security, Identity & Governance and Memory & State Persistence
- Akro AI6.5 / 14Adds documented Security, Identity & Governance and Memory & State Persistence
- Board9.5 / 14Adds documented Security, Identity & Governance and Memory & State Persistence
- ComplianceQuest5.5 / 14Adds documented Security, Identity & Governance
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded