For ITAM specifically, when does on-prem beat SaaS—and what does InvGate offer?
Choose on-prem when you need air-gapped operations, strict data residency, or internal-only connectivity. Choose SaaS when you want faster rollout and vendor-managed uptime/patching. InvGate Asset Management supports both cloud and on-prem, so buyers can match regulatory and operational constraints.
Can InvGate Asset Management run in air-gapped or offline environments?
Yes, via on-prem (air-gapped implies no dependency on external services). Inventory collection continues locally and sync behavior depends on your network design. Note: AI features typically require connectivity (validate in your architecture review if AI is in scope).
What should I ask about "feature parity" between cloud and on-prem?
Ask whether releases land later on-prem, and whether AI/integrations differ. InvGate Asset Management targets strong parity, but on-prem cadence can trail cloud depending on versioning/LTS policies—verify release alignment during procurement.
Can on-premises IT asset management tools take advantage of AI features?
AI capabilities in IT management have historically been limited to cloud deployments, leaving organizations with on-premises environments unable to access intelligent features — even when they've seen those features demonstrated and want them. The right approach for vendors is to close this gap without forcing teams to migrate their infrastructure to benefit from AI. InvGate Asset Management version 3.8 brings AI feature support to on-premises deployments. Organizations that manage their own infrastructure can now access AI capabilities through the same settings process as cloud customers — by requesting and configuring an AI key — without changing their deployment model or compromising their data residency requirements.
What's the difference between cloud and on-premise deployment?
Cloud (SaaS) is fully managed by InvGate with automatic updates, no infrastructure maintenance required, and accessible from anywhere with internet. On-Premise is installed on your infrastructure where you manage updates and maintenance, maintain complete control over data location, and can operate on internal networks without internet access. InvGate offers feature parity between cloud and on-premise deployments. Please note though, features for on-prem customers may be available at later versions than cloud.
What are the system requirements for on-premise deployment?
For InvGate Asset Management on-premise, you need Red Hat Enterprise Linux 8 or 9, or Windows Server 2016, 2019, 2022, or 2025. Supported databases include MySQL/MariaDB, Microsoft SQL Server, or PostgreSQL. Hardware requirements vary based on the number of assets managed. Full requirements are available in our knowledge base at support.invgate.com/knowledgebase_articles (last updated February 2026).
Can we use our own SQL database?
Yes, for on-premise deployments InvGate Asset Management supports MySQL and PostgreSQL. You install and manage the database on your infrastructure; InvGate does not provide the database server itself.
Does InvGate support air-gapped environments?
Yes, for fully air-gapped environments, on-premise deployment is required. The on-premise instance can operate on internal networks without internet connectivity. The InvGate Agent will synchronize data when connectivity is restored. Note that AI Hub features require internet access to function.
How do we migrate from on-premise to cloud (or vice versa)?
InvGate supports migration between deployment models. The process typically involves data export, reconfiguration, and import. Contact our Professional Services team for migration planning and assistance to ensure a smooth transition. Additional charges may apply.
Can the on-premise version work offline?
Yes, the on-premise version works on internal networks without internet connectivity as long as users can reach the on-premise server on your internal network. The InvGate Agent installed on client devices will continue attempting to report, and will synchronize when connectivity is restored. AI Hub features do need internet access to work.
What does the update process look like for on-premise?
InvGate provides security updates and regular LTS (Long-Term Support) updates for on-premise customers. Customers are notified via email when a new LTS version is available and each company is responsible for deploying updates to their on-premise installation according to their change management processes and maintenance windows.
Can InvGate be monitored by on-premise tools?
For on-premise deployments, InvGate behaves like any other application in the OS where it's installed. InvGate publishes log locations so any system that can ingest logs (SIEM, monitoring tools, log aggregators) can monitor the application. InvGate does not transmit application logs to a centralized cloud location for on-premise installations.
What backup and restore options exist for on-premise?
Backup and restore for on-premise installations are subject to your environment, backup systems, and the database you use (MySQL/MariaDB, Microsoft SQL Server, or PostgreSQL). InvGate does not provide backup and restore solutions; you manage these using your standard infrastructure backup procedures and database backup tools.
For on-premise, can we control which services run and which ports are open?
For on-premise deployments, you are responsible for infrastructure hardening including disabling unnecessary services, managing network ports, applying security patches, and maintaining security configurations according to your security standards like CIS benchmarks or ANSSI guidelines. InvGate's API is disabled by default for security.
What endpoints and ports need to be opened for the cloud version?
For cloud deployments, if workstations have internet access, agents report directly to your instance URL (https://[your-instance].cloud.invgate.net). If devices don't have direct internet access, they can report to an on-premise proxy which then forwards to the cloud. Specific port and endpoint requirements depend on your network configuration and are documented in our implementation guides.
What is the InvGate Connector?
The InvGate Connector is an on-premise service that enables secure communication between InvGate's cloud services and your on-premise resources like Active Directory or internal APIs that aren't exposed to the internet. It's included in your cloud subscription at no additional cost.
Do cloud instances have fixed IPs?
Fixed IP addresses for cloud instances are available for enterprise customers with specific networking requirements. Contact your sales representative to discuss this configuration option.
Can InvGate work with proxy servers?
Yes, InvGate supports proxy configurations for both cloud and on-premise deployments. The InvGate Agent can be configured to report through a proxy server, and on-premise installations can operate with proxy for limited internet access.