Integrations

PHX Terminal connects to a firm’s existing software in two complementary ways: the canonical platform automates at the UI layer through the Hover Opaque Application, and the commercial delivery program layers named enterprise integrations on top of that foundation.

Integration Flow

flowchart LR
  ORA["Oracle AI / OCI<br/>LLM layer"] --> API["Integration APIs<br/>Go / Python microservices"]
  API --> M365["Microsoft 365<br/>Graph · Azure AD"]
  API --> SF["Salesforce<br/>Experience · Einstein"]
  API --> VEN["Vendor APIs<br/>20 legal providers"]
  API --> SBX["Developer Sandbox"]
  SBX --> MKT["Marketplace"]

UI-layer integration: the universal adapter

The platform’s core integration mechanism does not depend on a target application exposing an API. Using AI Computer Vision, the Hover Opaque Application interacts with any user interface — modern or legacy — acting as a universal adapter at the UI layer.

This is decisive for legacy systems, which are often built on outdated languages, expensive to maintain, and difficult to integrate. Two strategies apply:

• Encapsulation — wrapping existing legacy systems with APIs so they can exchange data with modern tools.
• UI-layer automation — when direct API integration is not feasible, too complex, or too costly, the platform interacts directly with the application’s interface.

This bridges the integration gap for applications that lack modern APIs, delivering value without a full, disruptive system overhaul and lowering adoption friction for firms of all sizes.

The delivery program integrations

The commercial delivery program (see Program & Delivery) layers a set of named enterprise integrations onto the canonical platform:

Layer	Function	Technologies
Oracle AI / OCI	Legal AI automation and knowledge modeling (LLM layer)	Oracle AI, OCI
Microsoft 365	Firm-wide daily workflow — Outlook, Teams, Word, SharePoint	Microsoft Graph, Azure AD
Salesforce	Client portal and CRM	Salesforce Experience, Einstein
Vendor integrations	Connectors to 20 major legal software providers	Modular connectors with version control

Note

These named integrations represent the commercial delivery roadmap layered on top of the canonical hover-app platform — not the entirety of the product. The platform stands on its UI-layer automation; the enterprise integrations accelerate adoption inside the tools firms already use.

Resilience of the connector model

Vendor integrations use modular connectors with version control so that a breaking change in one vendor’s API affects only that connector — not the whole platform. This isolation, combined with the UI-layer fallback, keeps the integration surface resilient as the surrounding ecosystem evolves. See Risk & Mitigation for how API changes are managed.