Corelation put the person back in the core

Imagine a credit union member with a savings account, a car loan and a joint account with her father. To her, these are parts of one financial life. To a computer, they can become separate little kingdoms. The teller’s task is to reconstruct the person from the paperwork. Corelation begins with a different proposition: perhaps the computer should do more of the remembering.

A person is a better starting point

Corelation sells software to credit unions, rather than accounts to consumers. Its main product, KeyStone, handles the operational machinery behind deposits, loans and member service. A member may never learn the company’s name. An employee using its browser-based interface may spend much of a working day inside it.

The distinction that makes the company interesting is its person-centric design. KeyStone presents member relationships and account access together, and tracks activity by person. In our hypothetical household, that means the joint account belongs in a larger picture, with ownership and permissions still defined. Knowing someone has a relationship with an account is different from giving them permission to use it.

That is a small-sounding design choice with practical consequences. Information organized around a person can help staff understand an interaction without treating every account as a fresh introduction. The point is continuity: the member should not need to explain the shape of her financial life every time she asks a question.

The retirement that did not take

John Landis was hardly an outsider arriving to rescue banking with a clever app. Corelation’s founder and chairman had already designed two major credit union processing platforms before KeyStone. His experience stretches back to systems introduced in the late 1970s and the mid-1980s. He knew the territory because he had helped draw the map.

A 2012 company newsletter describes his attempt to retire after 25 years in the industry. New technology tempted him back. The same account describes more than six years of research and development behind KeyStone. Corelation itself began in 2009. The company’s founding date, in other words, does not capture the whole gestation of the software.

“It was an irresistible challenge,” Landis says on the company’s leadership page. The attraction was the opportunity to build again with tools unavailable when he designed the earlier systems. There is something pleasingly inconvenient about this origin: retirement offered leisure; a new database offered unfinished business.

Experience also sits on the service side. Theresa Benavidez led the company before becoming CEO Emeritus in January 2025, when Rob Landis became CEO. His earlier work included training, business analysis, project management and support. These are useful apprenticeships for a business whose product arrives attached to a substantial change in somebody else’s working day.

More inside, more doors outside

Corelation calls its product philosophy “More in the Core.” KeyStone includes tools that extend beyond recording balances, including workflows, CRM and real-time operational dashboards. Staff can tailor dashboard views to their jobs and drill into current information. A core can therefore act as a working instrument, rather than merely a record that another application must explain.

At the same time, Corelation argues for an open ecosystem. KeyBridge is its integration API. The company says it exposes the full transaction set, allowing outside vendors to perform actions available within KeyStone. The commercial promise is choice: a credit union can select additional systems to suit its own members and operations.

The combination is worth noticing. Including functionality inside a product and welcoming functionality from outside it can coexist. A credit union may want fewer separate tools for routine work, while keeping an independent digital banking provider. Breadth inside the core does not remove the need for useful connections beyond it.

Corelation’s partner directory includes Access Softek, Alkami, Bankjoy and Narmi. Those relationships place it in a market where a core processor must cooperate with other suppliers as well as compete for the institution’s central contract. In April 2026, DaLand CUSO and Corelation also announced Coin2Core, a digital asset integration using KeyStone architecture and KeyBridge. The API gives the platform a way to accommodate services beyond its original scope.

The bill is also paid in attention

The revealing case is Mountain America. Its KeyStone conversion went live on June 1, 2026, after nearly three years of planning, coordination, testing and execution. The credit union had more than $22 billion in assets and 1.4 million members. In Corelation’s account, all 108 branches opened as scheduled, with digital banking operational and key payment processing functions completed successfully.

That does not mean the change felt invisible. Corelation’s conversion announcement acknowledged early member confusion and said those concerns had been resolved. The release also described extensive employee training, member education and continuing refinement. The useful detail is the adjustment work. A system can be operating while people are still learning what has changed.

For a buyer considering similar software, the cost question extends beyond the contract. Planning consumes staff attention; training takes time; changed routines need explanation. Mountain America’s preparation is evidence of that commitment, not a timetable every institution should copy. Its size and scope make it a particular case.

Corelation supports the move with project management and conversion services. Its training approach combines hands-on sessions, demonstrations, guides and job aids, including teaching internal trainers who can pass skills to colleagues. Those services address a fairly ordinary truth: installing software and making people comfortable with it are separate jobs.

“The system is never finished.”

John Landis · KeyNotes, 2012

A signature is not a migration

Corelation’s growth needs two columns. In 2025, 38 credit unions signed to adopt KeyStone; 28 completed conversions. These figures describe different stages of the business. The company passed 300 total clients in April 2026, but that total includes institutions awaiting deployment. The twelve first-quarter signings were scheduled to convert in 2027 and 2028.

The distinction becomes especially important with SECU. In May 2026, the North Carolina institution signed with Corelation as part of a multi-year transformation. At announcement, it had more than $59 billion in assets and 2.9 million members. Its stated priorities included faster improvements, automation and a fuller view of member relationships. It selected KeyStone; that announcement was not a completed migration.

SECU’s chief executive, Leigh Brady, described a thorough evaluation and cited Corelation’s credit union specialization, reputation and recommendations. That helps explain the decision without inventing a dramatic change of heart. Buyers are judging both software and the people who will help them operate it.

A renewal supplies another kind of evidence. Desert Financial extended its partnership for ten years in 2024, after nearly a decade on KeyStone. Its assets had grown from $3.1 billion when it signed in 2014 to roughly $8.9 billion at renewal. The credit union credited openness and integration with supporting its growth. That is customer testimony, rather than proof that software alone produced the result.

The useful thing to borrow

Corelation competes in the core processing market alongside established alternatives such as Jack Henry’s Symitar and Fiserv’s credit union platforms. Its proposition combines member-oriented records, built-in operational tools, external integrations and service. The business is an enterprise relationship: institutions contract for core software and the work surrounding its adoption and continued use.

One service detail deserves a close look. Corelation says its client relationship managers have no products to sell and no quotas. Their work includes advocacy and periodic site visits. Removing a sales target does not automatically create good service, but it gives the role a clear purpose: help an existing client use the system well.

The transferable lessons are practical. Decide what the information system needs to understand before redesigning its screen. Make the integration plan part of the purchasing decision. Teach people who can teach others. Give service staff incentives that fit the service promise. Each is applicable well beyond credit unions.

There are conditions attached. An open API still needs capable partners and implementation work. A richer member view needs sound records and careful permissions. An institution unable to commit people to training and conversion planning should treat a major migration as an organizational decision, with a budget for attention as well as technology.

Corelation’s interesting wager is that these unglamorous details deserve to sit together. The account, the relationship, the connection to another vendor, the person answering a support question: each affects what happens when a member needs help. A friendly screen has to begin somewhere. Here, it begins with what the system remembers.