Support
Release process
How the Gfacility SaaS release process works — three phases of planning, development, and UAT/production deployment, plus how bugs and customer wishes are handled.
Updated Jan 14, 2026
Gfacility operates a true Software as a Service (SaaS) model, which means there is only one unified version of our software for all our users. Unlike individual customer releases, every new version takes effect directly for all customers. This guarantees stable software, keeps all customers up to date, and requires no extra effort from customers for the release/update. To manage this efficiently, Gfacility follows a release process consisting of 3 phases.
Release process
The process illustration below shows what process every feature goes through.
Phase I - Planning and design
Our backlog is continuously filled with internal improvement suggestions, the roadmap, and customer wishes. Every two weeks features are selected and planned, after which a technical analysis (TA) and possibly a design proposal follow.
Phase II - Development & Quality Assurance
After planning and design, every feature is developed, with a lead time of at least 4 weeks (2 sprints) up to 12 weeks or longer depending on the complexity of the functionality to be developed. Developed features are deployed to the Development environment, where our quality team runs tests and logs defects.
Phase III - User Acceptance Test and Production Release
Features on the Development environment are released as a package to the UAT environment on a standard 4-week cycle. Customers have 4 weeks to test the new release before it is rolled out to the Production environment. Feedback must be submitted at the latest 1 week before the release; after that we cannot guarantee that it will still make the next release. Feedback on the UAT environment can be submitted by customers in the Gfacility Support environment.
As a result of severe defects in the UAT environment, a release may be delayed or cancelled. Customers receive a notice at the latest on the last Wednesday before the release if it does not go ahead. If the release proceeds as planned, no notice will be sent.
The release planning can be found here. Release notes for both the UAT and Production environments will be shared every Friday prior to the release.
Incidents / BUGS
Incidents and bugs are typically detected and resolved in the UAT environment, but it is possible for a bug to still appear in the production environment. To safeguard software stability, bugs are first resolved in the UAT environment and then rolled out to production with the next release. Only bugs with critical impact, which make work impossible without an available workaround, are resolved directly in the production environment. This process aims to minimise incidents and maintain a stable and reliable software environment for our users.
Customer wishes
Customer wishes are important for the continued development of our software and can be submitted via the Support environment. Every two weeks all wishes are reviewed and next steps will be communicated. When a wish is accepted, it will be added to the release process as described above.