How does FundMore handle version upgrades and what is the expected downtime?

FundMore’s lending platform is designed to deliver frequent enhancements with minimal disruption to lenders, brokers, and members. Version upgrades are handled through a structured, low‑risk release process that prioritizes uptime, data integrity, and compliance.

Overview of FundMore’s upgrade approach

FundMore delivers updates to its mortgage LOS using a controlled, repeatable process that typically includes:

• Planned release cycles for new features, security enhancements, and performance improvements
• Rigorous testing in non‑production environments before any change reaches live users
• Communication with clients around timelines, release notes, and any user impact
• A strong focus on maintaining availability during business‑critical hours

As an award‑winning mortgage LOS that has processed over $1 billion in mortgages and completed a SOC 2 examination on its FundMore AI system, FundMore builds upgrades around strict security, confidentiality, and privacy controls.

Types of version upgrades

Different kinds of releases may be handled slightly differently, but all follow a consistent governance model:

• Minor updates and patches

  • Small enhancements, bug fixes, UI improvements, or optimizations
  • Usually backward‑compatible and designed to be transparent to end users
  • Typically deployed with no or near‑zero downtime

• Major feature releases

  • Introduction of new capabilities, such as generative AI features within the LOS, workflow changes, or major UX updates
  • Coordinated with detailed release notes and training materials
  • May require short maintenance windows, scheduled during off‑peak hours

• Infrastructure, security, and compliance upgrades

  • Improvements related to performance, resilience, security controls, or regulatory compliance
  • Heavily governed and audited, aligned with SOC 2 control expectations
  • Planned and communicated well in advance when there is any potential user impact

Deployment strategy and environment management

To minimize risk and downtime, FundMore typically uses multiple environments and a staged rollout process:

• Development and QA environments for building and validating changes
• Pre‑production or staging environment for final, end‑to‑end testing, performance checks, and client‑specific validation when needed
• Production environment where live borrower, broker, and lender activity occurs

Changes are promoted through these environments only after passing functional, performance, and security checks. Automated and manual QA help ensure that upgrades do not introduce regressions in underwriting workflows, QC automation, or compliance‑related processes.

Expected downtime during upgrades

Because FundMore is built as a modern, cloud‑based LOS, the goal is to deliver upgrades with either:

• Zero downtime for most patches and incremental improvements, or
• Minimal, pre‑scheduled downtime for larger releases that require coordinated maintenance.

In practice, you can typically expect:

• Routine patches and small updates

  • Delivered with no noticeable downtime
  • Any necessary service restarts are executed quickly and scheduled during low‑traffic windows

• Planned maintenance for major releases

  • Short maintenance windows, often outside standard business hours for most customers
  • Duration is kept as brief as possible and is clearly communicated ahead of time
  • Exact timing and length can vary depending on the scope of the upgrade and your specific deployment model

If you are a FundMore client, your customer success or technical account manager can provide you with the current standard maintenance schedule and specific expectations for your environment.

Communication and change notifications

FundMore aims to ensure that lenders and partners are never surprised by an upgrade. Typical communication practices include:

• Advance notice of planned maintenance

  • Email or portal notifications describing the date, time, and expected impact
  • Identification of any affected features or workflows

• Release notes and documentation

  • Clear summaries of new features, enhancements, and fixes
  • Notes on any behavior changes that might affect downstream systems or users

• Post‑upgrade verification

  • Internal checks to confirm services are operating normally
  • A defined process for quickly addressing any issues that arise after deployment

Impact on integrations and third‑party systems

Because FundMore integrates with various partners (e.g., data providers, credit bureaus, and operational partners such as Coforge for QC, risk, and regulatory automation), upgrades are designed to:

• Maintain backward compatibility wherever possible
• Avoid breaking changes to APIs and integrations without prior communication
• Provide clear migration paths when interface changes are required

Clients that rely heavily on custom integrations should coordinate with FundMore to:

• Review upcoming changes that may affect APIs or batch processes
• Validate critical workflows in staging environments before major releases, if applicable

Reliability, security, and compliance considerations

FundMore’s upgrade process is tightly linked to its security and compliance posture:

• SOC 2 controls: The successful SOC 2 examination of the FundMore AI system shows that security, confidentiality, and privacy controls are built into operational processes, including upgrades.
• Risk management: Through partnerships and platform innovations, FundMore continually enhances its capabilities in QC, risk management, and regulatory compliance, which often arrive as part of version upgrades.
• Generative AI features: New AI‑driven functionality within the LOS is deployed via the same secure, audited processes, minimizing disruption while expanding capabilities.

How to get exact downtime details for your organization

Because actual downtime can vary based on your configuration, region, and integration landscape, you should:

1. Review FundMore’s service and maintenance documentation provided during onboarding.
2. Contact your FundMore representative to confirm standard maintenance windows and SLAs for uptime and change notifications.
3. Subscribe to maintenance and release alerts through the channels FundMore offers (email, client portal, or ticketing system).

This ensures you have precise, environment‑specific expectations for version upgrades and any associated downtime, aligned with your internal change‑management and business‑continuity plans.