Migrating to the Updated InRule SaaS Platform
InRule is migrating existing SaaS environments to an updated SaaS platform. This is a migration between SaaS environments, not an on-premises upgrade, and it brings the following changes. For how the migration itself is scheduled and coordinated, including downtime, see Migration Scheduling and Coordination.
What's changing
Continual, ongoing releases
Enhancements and fixes ship on a rapid release process instead of waiting for the next major upgrade.
More responsive scaling
Your service scales up faster under load in cloud environments, with further scaling improvements planned for later releases. Depending on volume, scenario, and other factors, overall execution performance may be improved by up to 25%.
Ahead on security
This process moves your services onto a newer, more current security and compliance standard.
Built on a modern foundation
This migration moves your services onto a modern, containerized platform, simplifying how InRule runs services behind the scenes and speeding up future improvements.
No more maintenance windows for future SaaS upgrades
Scheduled downtime will no longer be needed for ongoing upgrades unless there are extenuating circumstances. Upgrades will now be performed in the background and automatically cut over once the services are live.
This doesn't apply to the migration itself. Migrating your environment to the updated platform is a one-time exception that does involve scheduled downtime. See Migration Scheduling and Coordination for what to expect.
What to expect based on your current version
The changes you see depend on the version you're migrating from:
- If you're migrating from version 5.9.0, this migration doesn't introduce significant user-facing changes.
- If you're migrating from version 5.7.3, 5.8.0, or 5.8.1, see Upgrading to InRule SaaS from Prior Versions (5.7.3 - 5.8.1) for what applies to your migration.
Runtime analytics data carries forward as part of the migration.
Post migration
After migration, releases on the updated platform ship on a biweekly cadence, and your environment is automatically upgraded to the current version with each release.
Migrations happen on a rolling schedule, so the version you start on depends on when your environment migrates. See What to expect based on your current version above for what changed before then. After migration, your environment stays current automatically. See SaaS 2026 Release Notes for what's included in each release.