HERE Studio Preview: Governed AI App Builder for Enterprise Browser

HERE Enterprise has announced HERE Studio, a natural-language app builder designed for regulated organizations that want employees to create internal tools without sending data or workflows outside a governed enterprise environment.
The product, announced July 14, is available in preview for HERE Enterprise Browser customers. It targets banking, health care, government and other organizations where ordinary “vibe coding” tools can clash with data-handling, identity and audit requirements.

Secure enterprise sales dashboard integrates business data, approved AI, APIs, and governance controls.App building inside the enterprise browser​

HERE Studio lets non-developers describe a task-specific application in plain language, then publish it into the HERE Enterprise Browser workspace. The company’s example is a sales dashboard that combines client information from several systems, presents it in a role-specific layout and can be shared with a team.
The important distinction is that Studio is not presented as a standalone public-cloud coding service. According to HERE, generated applications are built around the organization’s approved AI models, data sources, APIs and security policies. The firm says customers can use sanctioned services such as Claude Enterprise, ChatGPT Enterprise, Microsoft Copilot or Google Gemini, as well as internal models.
That matters for Windows shops because browser-based workflow tools are increasingly replacing purpose-built desktop utilities. If a company already centralizes business apps and AI access through an enterprise browser, a low-code builder embedded in that environment could reduce requests for small internal dashboards, data views and task-specific utilities.

Governance is the product pitch​

HERE is making “compliant by construction” its central claim. Studio apps are generated against an AI contract that the company says can enforce data classification, design standards, API entitlements, interoperability rules and security policy before an app is published.
Access control is also intended to reuse existing identity systems rather than introduce a separate permissions layer. HERE specifically names Microsoft Entra and Okta as supported identity sources. Administrators can limit Studio access to selected builders, grant it more broadly, and control which users or groups receive a finished app.
The approach is aimed at a common enterprise problem: business teams need a narrow tool immediately, while IT must evaluate its AI provider, data connections, access model and compliance posture. HERE’s pitch is that those controls are already present in the workspace, so the app builder cannot bypass them.

What admins should verify​

The release is a preview, not a general availability rollout. HERE’s product page says access is limited to a select number of firms, and an administrator publishes the generated app into the team workspace.
Organizations evaluating it should focus less on the natural-language interface and more on the controls behind it:
  • Which models, APIs, MCP resources and RAG systems an app can reach.
  • Whether Entra group membership and conditional-access policies carry through to published apps.
  • How generated applications are reviewed, logged, versioned and retired.
  • Whether data-loss prevention, audit and retention controls cover the apps as they do the browser workspace.
HERE Studio remains a limited preview for existing HERE Enterprise Browser customers.

References​

  1. Primary source: NTB Kommunikasjon
    Published: 2026-07-14T13:50:09.558751
 

Back
Top