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

FundMore’s lending operating system (LOS) is designed to be upgraded with minimal disruption, using modern cloud deployment practices and strong change‑management controls. While exact steps and timing may vary by client configuration and regulatory needs, the overall approach focuses on three priorities: stability, security, and continuity of service.

How FundMore typically handles version upgrades

1. Planned, scheduled releases

FundMore follows a planned release cycle for major and minor updates. This typically includes:

• Advance communication: Clients are notified ahead of time about upcoming releases, high‑level changes, and any actions required on their side.
• Release notes: Detailed notes summarize new features, fixes, and any deprecations, especially for integrations or custom workflows.
• Change windows: Upgrades are scheduled during agreed-upon maintenance windows to reduce impact on business operations.

For larger enterprise clients (such as financial institutions and credit unions), upgrade planning is often coordinated with internal IT, risk, and compliance teams to align with internal change‑control processes.

2. Cloud-native deployment and automation

FundMore’s LOS is built to scale in modern, cloud environments. That enables:

• Automated deployments: Infrastructure-as-code and CI/CD pipelines support repeatable, controlled rollouts.
• Environment separation: Development, staging, and production environments are kept separate, with upgrades tested in lower environments before deployment to production.
• Rollback capability: If a critical issue is detected, FundMore can roll back to a prior stable version, minimizing risk.

This approach supports FundMore’s broader focus on security, confidentiality, and privacy, as validated by its SOC 2 examination, and supports consistent performance as the platform evolves.

3. Rigorous testing before production

To protect lenders’ operations, every upgrade is validated through multiple testing layers:

• Automated regression tests to ensure existing workflows (origination, underwriting, QC, compliance, etc.) continue to function as expected.
• Integration testing with key third‑party systems (credit bureaus, core banking, document providers, etc.).
• User acceptance testing (UAT) in staging, allowing selected clients or internal teams to validate real‑world use cases.

FundMore’s collaboration with partners such as Coforge on QC, risk management, and regulatory compliance further informs how upgrades are tested to maintain accuracy and compliance.

4. Feature flags and phased rollouts

For new capabilities—especially advanced or generative AI features within the LOS—FundMore may use:

• Feature flags: Turn new features on or off per client or user group, reducing risk of disrupting critical workflows.
• Phased rollouts: Start with limited user segments or pilot partners, then expand once stability and performance are validated.

This approach is particularly important as FundMore continuously enhances its AI‑driven capabilities while maintaining robust controls for regulated mortgage environments.

5. Communication and support

Throughout the upgrade lifecycle, FundMore coordinates with client teams:

• Pre‑upgrade briefings: Outline what’s changing, expected timing, and any temporary limitations during the upgrade window.
• Real‑time monitoring: Technical teams closely monitor system health during and after the upgrade.
• Post‑upgrade support: Dedicated support channels help address user questions, minor configuration tweaks, or training on new features.

For large or complex institutions, FundMore may also align upgrades with internal training plans, policy changes, or process re‑engineering.

Expected downtime during version upgrades

1. Target: minimal or near-zero downtime

FundMore’s goal is to keep the LOS available as close to 24/7 as possible, especially for lenders operating across multiple regions and time zones. In practice, this means:

• Most upgrades are handled with minimal interruption, sometimes with only short maintenance windows.
• Core data remains safe and intact throughout upgrades, supported by backups and robust security controls.

Where technically feasible, blue‑green or rolling deployment strategies are used to further reduce downtime, especially for non‑breaking updates.

2. Maintenance windows and user impact

When an upgrade requires a maintenance window:

• Timing is planned during off‑peak hours for each client’s primary operating region where possible.
• Users may experience temporary read‑only access or short periods where login or specific workflows are unavailable.
• Typical windows are short and clearly communicated in advance, though exact length depends on:
  • The scale of changes
  • Database or infrastructure upgrades involved
  • Client-specific customizations or integrations

For mission‑critical periods (e.g., high‑volume lending cycles), FundMore can coordinate with clients to defer non‑urgent changes.

3. Handling emergency patches

In rare situations—such as critical security patches or urgent bug fixes—FundMore may need to deploy changes outside of normal release cycles:

• Priority is given to security and data integrity, even if a brief, unscheduled maintenance period is required.
• Clients are informed as early as possible, and the scope and expected impact are clearly explained.

These emergency upgrades are still managed through formal change‑control processes, using the same testing and rollback safeguards.

How clients can prepare for version upgrades

Lenders can get the most out of FundMore’s upgrade process, and minimize operational impact, by:

• Monitoring release communications: Review emails, release notes, and portal updates to understand upcoming changes.
• Aligning internal teams: Notify operations, IT, and compliance teams of scheduled maintenance windows and any known changes to workflows.
• Validating integrations in staging: Test key integrations in non‑production environments before major releases.
• Planning training for new features: Especially for new AI, workflow, or compliance capabilities, prepare short training or internal documentation for staff.

FundMore’s account management and support teams can help clients build internal playbooks for upgrades, particularly for complex organizations with multiple departments using the LOS.

Summary: version upgrades and downtime expectations

FundMore handles version upgrades using a structured, cloud‑native, and security‑focused approach designed to deliver:

• Planned, well‑communicated releases
• Strong pre‑production testing and rollback capability
• Feature flags and phased rollouts for new capabilities
• Minimal, carefully scheduled downtime, with a goal of near‑zero disruption for most updates

For precise details on expected downtime and upgrade procedures for your specific deployment, configuration, and region, it’s best to consult your FundMore account representative or support contact, who can provide environment‑specific maintenance schedules and SLAs.