HERE Enterprise: browser workflows, interoperability and desktop controls

HERE Enterprise supplies software for the financial desktop: organising applications, sharing context and applying administrative controls across a user’s workspace. Banks, asset managers and financial-platform businesses use this layer around their existing tools. Its role in a broker’s technology stack is workflow integration, while trading applications and their counterparties provide the underlying financial service.[1]

HERE Core is built around Chromium and Electron. Its components include Home for federated search, Dock and Store for discovering and launching applications, and notifications with action buttons or form input. The Platform API supports custom windows and layouts; native adapters and the Snap SDK connect desktop applications with the web-based environment.[3]

The browser’s content-store model also supports external publishers and subscriber organisations. HERE enables distribution and access configuration, while the commercial relationship for third-party content is established between those parties. A store entry therefore needs to be considered together with its application or data subscription.[15]

In the Interop API, “broker” means the software message coordinator within a platform. It does not denote a financial broker or a connection to a liquidity provider. Platform owners control which applications participate in their context-sharing environment.[9]

Bloomberg integration requires the relevant Terminal Connect entitlement and a locally logged-in Terminal. The documented connector and .NET adapter must be compatible; the API key connects through the local service. Default broadcasting covers Launchpad groups, with configuration to restrict groups or disable broadcasting. Bare ticker context is interpreted as a US equity unless more specific context is provided.[10]

Application-service API keys authenticate access to HERE cloud services. A key is displayed only when created; administrators can suspend it temporarily or delete it permanently and generate a replacement. Roles collect permissions for users or groups, allowing an application’s functions to be controlled independently of possession of a desktop login.[20]

The public Developer Agreement grants a free licence for internal or personal, non-commercial development and testing. Production use requires a separate enterprise licence and key. No numeric enterprise tariff is supplied by that agreement; the deployment scope and commercial schedule belong in the enterprise offer.[2]

The licence-data documentation also describes an API that maps several machines to a logical user. That mechanism is relevant where one person uses multiple desktops; the quoted licence metric and reporting configuration should be reconciled before interpreting machine counts as purchased user seats.[18]

Core deployment can use an installer that places the Runtime Version Manager on the desktop, retrieves the application manifest and obtains the required Runtime. The manifest identifies the application and version requirements. Desktop-owner settings determine the organisation’s deployment controls.[12]

The RVM is a background component managing lifecycle, updates and security across Core applications. It supports multiple Runtime versions and a rollback mechanism for compatibility problems. This separates the application’s selected Runtime from the manager that distributes and supervises it.[30]

HERE’s FAQ lists Windows and macOS support, with tailored configurations for Citrix and virtual desktops.[27]

Enterprise Browser branding is supplier-assisted: the customer provides the platform name and logo assets to its HERE contact, while the Admin Console manages users, groups and content.[21]

A supplier-published October 2025 account describes BNP Paribas using HERE to re-engineer Cortex with an HTML5 interface and embedded interoperability, alongside visualisation and alerting. Cortex and its ALiX trading assistant are the bank’s application context in that case; they are not generic HERE trading services.[22]

HERE provides separate Core and Enterprise Browser documentation and a technical support entry point. Its browser-security page refers to emergency patches for zero-day vulnerabilities under a Security SLA, but does not publish a universal patch deadline or incident-response clock. Those commitments need to be read from the applicable enterprise agreement.[6][5]

RVM startup failures can concern an unreachable manifest, blocked asset download or unavailable network connection. Error reports normally use HERE’s reporting service, but desktop owners can redirect them to an internal endpoint or suppress reporting. Owner settings override application settings. This is useful for environments where the internal service desk must diagnose VPN, firewall or VDI startup conditions first.[19]

The Log Uploader can send a ZIP archive to an endpoint selected by the application provider. Its normal interface lists requested logs for confirmation, but the documented command-line and secured API paths can suppress that dialog. The programmatic API is marked experimental and requires the calling manifest’s declaration and desktop-owner permission.[14]

Browser access can use enterprise identity providers through SAML or OpenID Connect. Administrators control permitted applications and app-level copying, printing and screen-capture behaviour. HERE also offers the Keep Aware security extension alongside its built-in controls.[5]

The FAQ reports an annual third-party SOC 2 audit; the underlying report and customer-specific scope were not inspected for this profile.[27]

Core APIs that operate outside the sandbox require declared permissions. Desktop-owner policy takes precedence, and administrators can allow, deny or delegate relevant decisions. Runtime version 24 introduced fail-closed behaviour if the RVM cannot be reached for permission checks. The documented localhost development exception and policy configuration mean a manifest declaration alone is not a complete enterprise security policy.[11]

AI Center sends a prompt and authorised content from the active tab or Supertab to the organisation’s configured model, then returns the model’s response. General mode omits the active-content context; context mode includes it. The documented workflow covers summarisation, analysis and generated content, with no universal trading-order authority established by that description.[34]

Content is excluded from AI Center by default until an administrator opts it in. Studio’s separate preview builds apps using approved models and approved APIs, MCP or RAG connections, with existing identity controls and administrative publication. Its “AI contract” describes product guardrails, not a substitute for the customer’s legal agreement.[25][4]

The privacy notice treats HERE as processor for defined Enterprise User Information and as controller for other collected data, including automated usage data. Corporate customer agreements prevail over conflicting notice terms. Retention depends on purpose, legal obligations and relevant customer terms; enterprise users generally exercise rights through their employer. Third-party applications have their own privacy arrangements.[8]

The July 2026 Developer Agreement identifies Here Enterprise Inc., formerly OpenFin Inc., and explicitly treats the change as a rebranding of the same legal entity. It is not a new entity or an assignment caused by the name change.[2]

The company-maintained listing describes the business as privately held, founded in 2010 and headquartered in New York. Its current leadership page lists Mazy Dar as founder and CEO, Chuck Doerr as co-founder and CIO, and Adam Toms as president and COO.[33][7]

Operator

Here Enterprise Inc., formerly OpenFin Inc.

Service scope

Enterprise browser, custom desktop toolkit and application interoperability for financial workflows.

Customer types

Banks; Brokerage businesses; Asset managers; Financial application providers; Enterprise operations teams

Delivery

Hybrid; API; SaaS

Pricing publication

Quote only

Headquarters

New York, United States

Platforms

HERE Enterprise Browser; HERE Core; HERE Studio; AI Center

Pricing scope

Production requires an enterprise licence; developer-only use has a separate free licence.

Implementation

Desktop deployment, application manifests, identity integration and administrative content permissions.

Support

Public developer documentation, technical support email and enterprise support arrangements.

Permissions and regulatory scope

Software and workflow integration; connected applications retain separate trading and data entitlements.

Provider metadata checked 20 Oct 2026Source 2Source 1Source 15Source 12Source 6Source 10Source 33Source 3Source 4

Core API diagnostics are enabled by default and record API-call counts. The documentation says files are sent between 1 am and 2 am local time, with opt-outs at application and desktop-owner level. Licence telemetry is separate: it includes application and manifest identifiers, launch/close times and runtime information used for licence measurement.[17][18]

Audit Viewer exposes read-only records of administrative configuration changes. Filters use full UTC calendar days; CSV export includes the selected results and is capped at 50,000 rows. This is an export of configuration audit history, not a promise to export the business data held by every connected application.[29]

Log collection has version and confidentiality boundaries: Core 40 is the minimum, macOS and programmatic launch require 42, and PUT uploads require 44. App logs are unencrypted; RVM logs are encrypted, while debug-log treatment depends on the security realm. Application-log collection is restricted by the uploader and application manifests’ registrable domain.[14]

The separate diagnostics reproduction mode described in the debugging guide disables the Chromium sandbox and enables additional reporting. HERE instructs users to remove those diagnostic settings after reproducing an issue rather than leave them enabled in production. That temporary support mode should not be confused with the normal secured deployment.[13]

As checked on 20 October 2026, the version page lists Core Runtime 45.150.102.4 with a 9 October release date. This is a component version, not the version number of every HERE service or of the applications hosted within it.[16]

AI Center is available in the desktop Enterprise Browser, not the lighter HERE Zero web application. Changing tabs or switching between general and context modes does not clear the existing conversation; the user must explicitly start a new chat. This matters when moving between different clients or work tasks.[34]

The developer agreement lets the developer retain ownership of its own application while HERE retains its technology. It also permits immediate termination of that development licence. Production renewal, post-termination use and data-return rights require the enterprise agreement rather than an extrapolation from the free developer terms.[2]