1
dedicated tenancy per client
PORFIN Cloud offering
Move PORFIN to the cloud without changing systems or loading IT with the infrastructure.
PORFIN Cloud lets you run the application on a dedicated instance per client, managed by Alfa GL. The client reduces operational load, gains agility to execute projects and opens a gradual path from the legacy version to the modernized version.
VPN
secure access to production and testing
2
planned patches per year
Legacy + Web
gradual coexistence once transition is enabled
Why this offering exists
The problem is not PORFIN. The problem is sustaining it on-premise when the technical operation gets in the way.
Operational load that adds no value to the business
Infrastructure, backups, environments and base administration of the platform keep consuming time from IT teams that are already stretched thin.
Projects stalled by internal provisioning
Support, testing and new initiatives are delayed when every environment depends on internal requests, approval windows and the client's infrastructure timelines.
Perceived risk of touching an operation that already works
Many clients want to move forward, but not at the cost of an abrupt change to an application that is still critical to their daily operation today.
What's included
A dedicated operation, managed by Alfa GL, without turning PORFIN into a shared instance.
Production and testing managed by Alfa GL
Alfa GL provisions and operates the environments needed to run the solution and support, testing and projects with greater agility.
Dedicated instance and isolated data per client
Each client operates in its own tenancy, with complete separation of application, data and access from any other client.
Secure access via VPN
The client keeps accessing the application through controlled channels, without exposure to an open model or a shared instance.
Controlled update policy
The offering keeps a predictable operation, with a stable policy of two patches per year, without forcing short change cycles that affect the operation.
Expected outcome
What changes when PORFIN no longer depends on the client's data center.
Less load for IT
The client stops carrying a large part of infrastructure administration and the daily pressure of sustaining operational and project environments.
More speed to execute support and evolution
Alfa GL can enable environments and execute work with far less friction, which cuts dead time between decision and execution.
A change path with less risk
First the current operation is moved as-is. Then, when the client decides, a controlled coexistence between legacy and modernized is enabled.
Deployment models
Two ways to operate PORFIN depending on the level of change the client wants to take on.
PORFIN On-Premise
The client retains full control of infrastructure and technical operation, but also the full load of environments, administration and provisioning timelines.
PORFIN Cloud Transition
Once on managed cloud, the client can run the legacy and modernized versions side by side and gradually retire the legacy with lower risk.
Cloud Transition
First the current operation is moved. Then the transition to modernized opens with less risk.
The offering does not force an abrupt change. First it moves the current PORFIN to managed cloud. Then it enables a controlled coexistence between the legacy and the modernized version to retire the legacy little by little.
01
Move the current PORFIN to managed cloud
The initial priority is not to change the product, but to move the current operation to an infrastructure managed by Alfa GL.
02
Deliver production and testing with secure access
The client starts operating and testing on dedicated environments, with less dependence on internal provisioning.
03
Open controlled coexistence with the modernized version
When the client is ready, Alfa GL can enable access to both the legacy and the modernized version to reduce change anxiety.
04
Gradually retire the legacy
The transition happens in phases, not as an abrupt jump, until the legacy version is retired when the operation confirms it.
Frequently asked questions
Normal objections when the conversation moves from on-premise to managed cloud.
Is this a traditional SaaS?
Not in the classic sense of a single multi-company instance for all clients. Commercially it is best presented as PORFIN Cloud: software operated by Alfa GL in a dedicated instance per client.
Do we share the application or data with other clients?
No. Each client has its own tenancy, with its application, its data and its access kept separate. The proposal does not depend on a shared base across clients.
Do we have to migrate to the modernized version right away?
No. The offering starts by moving the current PORFIN to managed cloud. Coexistence between legacy and modernized is enabled later, when the client wants to reduce risk and move forward in phases.
What changes for the technology area?
The load of operating infrastructure decreases and, above all, the dead time to enable support, testing and project environments is reduced. IT keeps governance, but stops carrying the most cumbersome part of base operation.
How are updates handled?
The offering keeps a controlled and predictable policy of two patches per year. The idea is not to impose short change cycles, but to provide operational stability while gaining agility to execute projects.
Next step
Let's assess whether PORFIN Cloud reduces operational friction in your current context.
We review current infrastructure, load for IT, provisioning timelines, testing needs and whether it makes sense to open a later path of coexistence between legacy and modernized.