Express-O 17 in the cloud
Plan SaaS delivery for your Banking, Cooperative, Credit Union, or Lending edition, with mobile, payments, channels, and reporting scoped for your institution.
Explore Express-O 17 →Express-O & Express-O 17 · Delivery option
Your banking platform.
Delivered as cloud SaaS.
Cloud software as a service is a delivery option for both Express-O and Express-O 17. Choose the platform that fits your institution, then plan cloud hosting and service responsibilities with our team. Express-O 17 launch is scheduled for early 2027.
Discuss cloud requirementsChoose the product first
Two platforms.
One cloud service option.
Cloud SaaS changes how your platform is delivered. Product scope, edition, and implementation timing follow the platform you choose.
Express-O in the cloud
Explore SaaS delivery for institutions with 1–2 operating units and basic banking operations, with migration and service scope agreed before implementation.
Explore Express-O →Your platform, your service arrangement
Core operations.
Cloud delivery.
The cloud service builds on the Express-O or Express-O 17 platform you select. Hosting and operating responsibilities are defined around that platform and your institution’s requirements.
Banking operations
Customer and account records, deposits, lending, transactions, accounting, approvals, and reporting in one core.
Service model
Cloud hosting, application operations, access, monitoring, backups, support, and recovery responsibilities are documented in the service agreement.
Controlled transition
Migration, connected systems, security review, testing, training, and go live criteria are planned with your institution.
Deployment region, data handling, resilience targets, service levels, pricing, and regulatory obligations depend on the agreed scope and applicable requirements. Existing Express-O installations are assessed before any move.
Compare Express-O and Express-O 17 →Before procurement
What comes with the model?
What needs agreement?
Cloud SaaS is a delivery option for both Express-O and Express-O 17. Express-O 17 launch is scheduled for early 2027. The following operating and commercial terms need to be documented for your institution before commitment.
Which hosting options are available?
Cloud SaaS delivery is an option for either platform, subject to its product availability and agreed implementation scope. Confirm the proposed provider, region, data handling, access arrangements, and any institution-specific hosting constraints during assessment. No standard provider or region is published here.
Who is responsible for backups and recovery?
The service agreement defines application operations, monitoring, backup, and recovery responsibilities. Ask for backup frequency, retention, restore testing, recovery targets, and your institution’s responsibilities in writing; the website does not publish standard recovery commitments.
What support coverage is included?
Support is part of the service arrangement. Agree coverage hours, contact and escalation paths, maintenance arrangements, and service levels in the contract. No response-time guarantee is published here.
How are licensing and pricing determined?
The offering uses a software as a service model. Request a scoped proposal distinguishing recurring service and licensing charges from migration, integration, training, and other implementation work. Public prices and a standard per-user or per-branch charging basis are not specified.
Can an existing installation move to the cloud?
Existing Express-O installations are assessed first. Agree data migration and reconciliation, connected systems, testing, training, and go-live acceptance criteria. Regulatory and security review must reflect your operating market.