Corporate networkCustomer network, proxy, DNS and policies
ELIMFLOW ON-PREMISE
Your infrastructure. Your control.
Deploy ElimFlow inside your environment when data, network, identity or internal policies make it necessary to keep the platform under corporate control.
Your own infrastructure Corporate integration Controlled licensing
Private deploymentCustomer environment
PRIVATE
Identity layerSSO and access according to the agreed architecture
ElimFlow applicationWorkspace and enabled modules
Data & servicesDatabases, storage and integrations
OperationsBackup, updates and monitoring
01 Data under your architecture02 Internal network integration03 Controlled change windows04 Hybrid model available
ANNUAL LICENSE
ElimFlow Private from €4,900/year
Starting reference for up to 50 users. Scope, infrastructure, support and integrations are validated before contracting.
€4,900/ year · up to 50 users
Implementation from €950Assessment, deployment and initial configuration according to scope
WHY ON-PREMISE
When “in the cloud” is not the whole answer.
For some organizations, data location, access to internal systems and operational policies matter as much as functionality.
Data control
The platform can run on infrastructure managed by your organization and align with your internal policies.
- Your own storage
- Corporate network
- Internal policies
Access to internal systems
Work alongside resources not exposed to the Internet and services available only inside your network.
- Internal services
- Connectors
- Private integrations
Corporate identity
Integrate the workspace with the authentication and permission model defined for your environment.
- SSO
- Roles
- Tenant and organization
Planned operations
Define when to update, how to back up and who operates each layer of the platform.
- Change windows
- Backup
- Operating procedures
Licensing
The installation can be tied to a license and module scope agreed for the organization.
- License identifier
- Validity
- Activation control
Hybrid model
Not everything has to live in the same place. Components and integrations can be separated when the scenario requires it.
- Combined services
- Connectors
- Case-by-case architecture
PRIVATE ARCHITECTURE01 02 03
ElimFlow inside your ecosystem.
On-Premise does not mean copying a ZIP and walking away. Before deployment we review dependencies, identity, storage, network, backups, integrations and operations.
Network and accessDNS, proxy, firewall, TLS and required connectivity.
Data and storageDatabases, files, retention and backup strategy.
OperationsOwners, updates, support and recovery.
Corporate SSOIdentity
Internal ServicesAPIs · DB
StorageFiles · Backups
OperationsMonitoring · Updates
Reverse ProxyTLS · DNS
IMPLEMENTATION PROCESS
An installation that starts before the server.
The goal is to reach production with clear responsibilities, not discover them afterwards.
Assessment
We review infrastructure, users, identity, network and integrations.
Preparation
The environment is validated and prerequisites are documented before deployment.
Installation
We deploy the platform and configure modules, access and integrations.
Acceptance
We test real use cases, backup, access and operations before go-live.
CHOOSE THE MODEL
Not every organization needs the same thing.
The deployment model is chosen based on requirements, not trends.
ElimFlow Cloud
The most direct option for teams that want to reduce their own operational burden.
- Faster go-live
- Managed operations
- Simple scaling
ElimFlow Private
For organizations that need the platform to run inside their infrastructure.
- Infrastructure control
- Access to internal services
- Your own corporate policies
ElimFlow Hybrid
Combine components and services when the architecture requires responsibilities to be separated.
- Integration flexibility
- Selective connectivity
- Case-by-case design
ON-PREMISE FAQ
Before deployment.
Private deployment is technically defined with each organization.
Can ElimFlow On-Premise work without public Internet access?+
It can be designed for private networks, but specific requirements depend on the modules, updates and integrations selected. This is validated before deployment.
Who manages the database and backups?+
This is agreed during implementation. In an On-Premise model, the organization may take on a greater part of operations, with jointly defined procedures.
Can we use our own domains and certificates?+
Yes. The deployment can integrate with DNS, reverse proxy and certificates managed within the corporate infrastructure.
Are updates automatic?+
They do not have to be. In private environments, update windows can be planned to fit the organization’s change procedures.
How much does ElimFlow On-Premise cost?+
The starting reference is €4,900/year for up to 50 users, with implementation from €950. Final pricing depends on scope, infrastructure, integrations and the agreed support level.
Do you want ElimFlow inside your infrastructure?
Tell us about your environment and we will prepare a deployment proposal covering scope, responsibilities and integrations.