Hyland for Guidewire went live on Guidewire Marketplace on October 19 with integrations for the three applications in Guidewire's InsuranceSuite: ClaimCenter, PolicyCenter and BillingCenter. Guidewire validated them through its Ready for Guidewire program. The integrations use Content Federation Service to reach existing OnBase repositories, on premises or hosted, so an adjuster in ClaimCenter can open documents stored in OnBase without anyone first migrating them into Hyland's cloud.

Hyland, founded in 1991 in Westlake, Ohio, built OnBase into the document system behind claim files and patient records at thousands of organizations. This is my first piece on the company. The Guidewire release is a useful place to start because it shows how Hyland plans to modernize customers who, as Reworked reported in 2025, are in no hurry to move to the cloud.

Federation Lets an Insurer Move Its Core System Before Its Archive

Take a carrier that has run ClaimCenter alongside OnBase for a decade. Its claim files and damage photos sit in OnBase, indexed and held under retention rules the records team set years ago. When that carrier moves its core system to Guidewire Cloud, it has to decide what happens to those documents. Moving them means re-indexing years of files and confirming every retention rule survived the transfer, while leaving them in place requires a way for the cloud application to reach back into the archive.

Hyland for Guidewire provides that connection. Content Federation Service links the OnBase repository to Hyland's Content Innovation Cloud, and the integration displays the documents inside the Guidewire screen. The insurer can make the archive decision on its own timeline after the core system move, or put it off for as long as the federated setup meets its needs.

Hyland and Guidewire have worked together for more than a decade, and Guidewire cited 16 mutual customers when it added Hyland to its SolutionConnect partner program in June 2014.

Hyland Is Applying the Same Design to Its Own Four Platforms

Alongside OnBase, acquisitions brought Hyland Perceptive Content in 2017, Alfresco in 2020 and Nuxeo in 2021. Four months after Jitesh Ghai, former chief product officer at Informatica, became CEO in May 2024, Hyland announced the Content Innovation Cloud at its CommunityLIVE conference. The plan keeps all four platforms, cloud-enables them and applies AI to content wherever it resides, including repositories from other vendors.

Ghai's background helps explain that choice. Informatica's core business is connecting data across systems that companies keep running, and Hyland's ClaimCenter solution overview describes Content Federation Service as based on data federation principles, giving a unified view of distributed content while the files stay in place. Hyland used the same design for hospitals on October 27, adding pathology images to the Acuo archive and NilRead viewer it already sells for radiology and cardiology.

"[Insurers are] often doing it on fragmented content foundations that ultimately slow their business down."

Kathy Hrach, Vice President of Insurance Product Management, Hyland

Federation Leaves Governance With Each Source System

Federation leaves permissions, retention schedules and legal holds with each source system, so any cloud service reading across those systems has to check each one's rules at the moment of the request. That requirement grows as insurers turn on the optional AI document processing and AI agents Hyland offers through the Content Innovation Cloud, since an agent building a claim summary could pull from an on-premises OnBase server and a cloud repository in the same task.

For a carrier with years of OnBase content, federation is the lower-risk way to start. Some carriers will treat it as a bridge until they move content into Hyland's cloud repository, and others will keep it as the long-term design. Your choice between those paths decides how much governance work stays with your team, so make it before the integration goes live. Questions to bring to a Hyland briefing or proof of concept:

• Which OnBase versions and deployment models does Content Federation Service support today, and which other repositories are on the roadmap?
• How does the system check access rights when one request spans on-premises and cloud content?
• Do retention schedules and legal holds set in OnBase carry through to Content Innovation Cloud services and agents?
• Does Hyland's Cloud Update Service, which automates monthly OnBase updates, cover your deployment?