Valon vs Sagent

Two cloud rebuilds approaching from opposite directions

Valon and Sagent now compete for the same purchase. Both sell a cloud built core servicing system of record. Both ask servicers to leave an older core behind.

They arrived differently. Sagent came out of Fiserv Lending Solutions, bought by Warburg Pincus in 2018. Valon started in 2019 as a servicer writing its own software. Neither is the quiet incumbent here, which changes how reference calls should go.

Valon’s pivot from subservicer to software vendor

Valon ran loans itself until August 2026. Carrington Mortgage Services then bought Valon Mortgage and its subservicing book. That moved roughly 810,000 loans and about $197 billion in unpaid principal balance.

Valon Technologies kept the platform and now licenses ValonOS. Carrington adopted ValonOS as its core after closing. Rithm Capital plans to run Newrez on ValonOS from 2027, covering more than four million homeowners. Rithm also invested in Valon, so that reference is not arm’s length.

Sagent’s installed base and its two platform question

Sagent reports more than 40 clients and 16 million active loans across its systems. Those figures are vendor stated. Most of that volume sits on LoanServ, the older real time core.

Dara is the newer platform, split into Core, Consumer, Default and Analytics. Dara Core finished a version 1.0 build in 2025 with Mr. Cooper testing it. Click n’ Close and Evergreen Home Loans committed to Dara deployments in 2026. A buyer should ask which system will run its loans in 2030.

Ledger design, escrow and tax mechanics

Valon describes ValonOS as one ledger with sub second data freshness. LoanServ posts payments and cash positions in real time as well. Both claims are vendor stated and neither carries a published method.

LoanServ escrow administration handles hazard insurance, PMI and MIP, property tax and HOA dues. Valon publishes less escrow detail publicly, so ask for a written breakdown. Escrow analysis errors drive complaints and refunds, so test a full analysis cycle.

Agency reporting and government loan handling

Valon lists prebuilt integrations with Fannie Mae, Freddie Mac and Ginnie Mae. Its servicing arm held Ginnie Mae issuer approval and licenses in all fifty states. That operating record now sits with Carrington, while the software stayed with Valon.

The Sagent LoanServ investor module covers agency, private and portfolio investors. It reports cash at investor, pool and loan level and handles FHA, VA and USDA detail. Government loans carry the tightest reporting deadlines, so demo a Ginnie Mae cycle on both.

Default workflow and who answers the examiner

Dara Default handles loss mitigation, bankruptcy, foreclosure, claims and invoices. Sagent shipped Default before Dara Core, so it has run longer in production. Valon built default handling for its own book, including government loss mitigation.

Valon publishes SOC 2 Type 1 and Type 2 coverage for the platform. Under either license the servicer answers the CFPB and state examiners. Ask each vendor which default letters and timelines arrive without custom work.

Conversion risk, reference calls and unpublished pricing

Neither company posts a public price. Ask both for a five year cost per loan at your volume and delinquency rate. Ask which items bill separately, including conversion, interfaces, custom reports and support.

Reference calls matter more here than in most software purchases. Sagent can point to LoanServ clients, but LoanServ is not Dara. Valon can point to Carrington and Newrez, and it has ties to both. Insist on a reference with no ownership or investment link to the vendor.

Which one to pick

A servicer with a large government book and thin technology staff should lean toward Sagent. LoanServ gives a working fallback while Dara modules come online. Ask Sagent to put the LoanServ support end date into the contract.

A servicer rebuilding its operating model around automation should look closely at Valon. ValonOS was written for one ledger and machine handled exceptions. Ask Valon to show a conversion from a core that Valon did not build.