H Company released Holo4 in 27B and 35B-A3B versions on 28 September. The vendor designs them for clicking through applications, executing code and calling tools through MCP or APIs. Downloadable weights and a hosted API are available; the model still needs an environment that executes its requested actions.

Licenses differ: the 27B weights use CC BY-NC 4.0 with a noncommercial restriction, while 35B-A3B uses Apache 2.0. Paid API terms are separate. Comparative scores come from the company, evaluation setups differ, and published task traces do not independently guarantee success.

The greatest value might be in workflows alternating between an older application without an interface and a newer service with an API. An agent could read documents, prepare an item list and transfer it into a system normally operated by hand. This would not magically eliminate integration; it offers another way to bridge a missing part of it.

Deployment requires checking the chosen variant's license, hardware needs and behavior when something fails or a screen changes. Whole-workflow testing is decisive: correctly completed tasks, human interventions, reversibility and total cost. For sensitive operations, the agent should initially prepare a proposal rather than automatically confirm an irreversible action.

With weights and API access already available, an optimistic pilot for one narrow workflow could yield results within one to three months. This is an editorial estimate allowing for integration and review, not a promise of a universal employee. The illustration shows generic interfaces, not the actual product.