IZI Release Policy
IZI Release Policy for Gaming Club Software and Platform Update Schedule
Section titled “IZI Release Policy for Gaming Club Software and Platform Update Schedule”IZI ships updates continuously — no fixed weekly slot, no version lockstep. Updates go live when they are fully tested. Major releases arrive every 4–8 weeks and come with a CRM announcement 3–7 days in advance so you can prepare your staff. Patches and hotfixes follow their own cadence depending on urgency. Your existing tariff settings, loyalty rules, and staff accounts survive every update automatically — no manual migration needed unless the changelog says otherwise.
Types of Updates
Section titled “Types of Updates”Major releases introduce new modules or significant changes to existing ones. They ship every 4–8 weeks. Each major release includes a changelog entry, a CRM notification, and occasionally an email to the venue owner.
Patches cover bug fixes and small improvements. They ship as needed — anywhere from several times a week to several times a month — and are recorded briefly in the changelog.
Hotfixes address critical production bugs and go out immediately on discovery. They are not announced in advance, but do appear in the changelog after the fact.
Release Schedule
Section titled “Release Schedule”IZI does not follow a fixed calendar like “every Tuesday.” Updates ship when they are ready and tested.
For major releases, expect a CRM announcement 3–7 days before the rollout describing what will change and what (if anything) requires action on your end.
Backward Compatibility
Section titled “Backward Compatibility”IZI actively avoids breaking your existing configuration during updates:
- Tariff settings, loyalty programs, and staff roles are preserved across all updates.
- API — breaking changes are announced at least 30 days in advance; the previous API version remains supported for 90 days after the new one ships.
- POS and third-party integrations — you receive at least 14 days’ notice before any change that affects a connected service.
If an update requires a manual action from your team, the changelog entry will say so explicitly and include step-by-step instructions.
Rollbacks
Section titled “Rollbacks”IZI does not offer per-venue rollbacks to a previous version. If an update causes unexpected behavior in your club, contact support immediately — regressions are treated as priority bugs and addressed in the next hotfix window.
Beta Testing
Section titled “Beta Testing”Clubs that want to test changes before they reach production can opt into beta access. Reach out to your IZI account manager to discuss participation. Beta builds receive the same changelog documentation as production releases.
Update Notifications
Section titled “Update Notifications”You can track major releases through two channels:
- CRM notifications — enabled by default for the venue owner account; no setup required.
- IZI Telegram channel — ask your account manager for the current link.
Maintenance Windows
Section titled “Maintenance Windows”Planned maintenance typically runs during low-traffic hours: 00:00–06:00 UTC+4. Clubs receive at least 24 hours’ notice before scheduled downtime.
Unplanned maintenance during a critical incident may start without prior notice, but a notification is sent at the moment work begins.
See Also
Section titled “See Also”Frequently asked questions
How often does IZI release platform updates?
IZI ships patches and hotfixes on a rolling basis — whenever they are ready and tested. Major releases arrive every 4–8 weeks and are announced in the CRM 3–7 days in advance.
Will an IZI platform update break my existing tariff settings or loyalty rules?
No. Tariff settings, loyalty programs, and staff roles are preserved across all updates. If a manual action is required, the changelog entry says so explicitly and includes step-by-step instructions.
How do I find out about upcoming releases in advance?
CRM notifications are enabled by default for the venue owner account. Major releases also appear in the IZI Telegram channel — ask your account manager for the current link.