Datavine On-Premise Agent Setup [Linux]
The On-Premise Agent allows the Datavine integration platform to access resources on your network that are not exposed to the internet. It runs as a system service, keeps a single outbound connection to Datavine, and needs no inbound firewall rules.
Before you start
- A Linux server running Debian, Ubuntu, RHEL, Rocky, Alma, Fedora or Alpine, with root
(
sudo) access. - Outbound HTTPS access to the Datavine cloud, plus network access to the internal systems you want to integrate.
- Your Datavine contact available to approve the registration code.
Install
Choose your distribution and architecture, then run the command on the server. It downloads the package, verifies its signature against the Datavine signing key, installs it, and starts registration.
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_amd64.deb \ && curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_amd64.deb.asc \ && curl -fsSL https://app.datavine.com/cloud-connector/signing-key.asc | gpg --import \ && gpg --verify datavine-cloud-connector_1.3.3_amd64.deb.asc datavine-cloud-connector_1.3.3_amd64.deb \ && sudo apt install -y ./datavine-cloud-connector_1.3.3_amd64.deb \ && sudo datavine-cloud-connector-register
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_arm64.deb \ && curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_arm64.deb.asc \ && curl -fsSL https://app.datavine.com/cloud-connector/signing-key.asc | gpg --import \ && gpg --verify datavine-cloud-connector_1.3.3_arm64.deb.asc datavine-cloud-connector_1.3.3_arm64.deb \ && sudo apt install -y ./datavine-cloud-connector_1.3.3_arm64.deb \ && sudo datavine-cloud-connector-register
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector-1.3.3-1.x86_64.rpm \ && sudo rpm --import https://app.datavine.com/cloud-connector/signing-key.asc \ && sudo dnf install -y --setopt=localpkg_gpgcheck=1 ./datavine-cloud-connector-1.3.3-1.x86_64.rpm \ && sudo datavine-cloud-connector-register
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector-1.3.3-1.aarch64.rpm \ && sudo rpm --import https://app.datavine.com/cloud-connector/signing-key.asc \ && sudo dnf install -y --setopt=localpkg_gpgcheck=1 ./datavine-cloud-connector-1.3.3-1.aarch64.rpm \ && sudo datavine-cloud-connector-register
Run as root (or prefix each command with doas or
sudo). apk verifies the package against the Datavine key installed in
/etc/apk/keys and refuses it otherwise.
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_x86_64.apk \ && curl -fsSL -o /etc/apk/keys/datavine.rsa.pub https://app.datavine.com/cloud-connector/datavine.rsa.pub \ && apk add ./datavine-cloud-connector_1.3.3_x86_64.apk \ && datavine-cloud-connector-register
curl -fLO https://gitlab.com/api/v4/projects/81725141/packages/generic/datavine_cloud_connector/1.3.3/datavine-cloud-connector_1.3.3_aarch64.apk \ && curl -fsSL -o /etc/apk/keys/datavine.rsa.pub https://app.datavine.com/cloud-connector/datavine.rsa.pub \ && apk add ./datavine-cloud-connector_1.3.3_aarch64.apk \ && datavine-cloud-connector-register
The last step prints a Registration Code. Give the code to your Datavine contact.
The command waits until the code is approved, then enables and starts the service. If it is
interrupted, run sudo datavine-cloud-connector-register again.
Check that it is running
systemctl status datavine-cloud-connector # live logs journalctl -u datavine-cloud-connector -f # Alpine rc-service datavine-cloud-connector status tail -f /var/log/datavine-cloud-connector.log
Upgrade and uninstall instructions are in the release notes. Windows setup is on the Windows page.
Security
The On-Premise Agent is a lightweight, self-updating process that provides secure, outbound-only connectivity for integration workflows that need access to internal resources. The sections below are the InfoSec fact sheet for the agent.
01Overview
The Datavine On-Premise Agent is a lightweight, self-updating process that enables secure connectivity from your internal network to the Datavine cloud platform for integration scenarios requiring access to internal resources.
- Supported platforms: Windows, Linux
- Distribution: Simple installer; no manual configuration required.
- Use case: Secure, outbound-only connectivity for on-premise integration workflows (no inbound ports needed).
02Deployment & operation
Installation
- The agent is a single binary with minimal dependencies.
- Windows installer and Linux packages (deb, rpm, apk) are available for streamlined setup.
- Runs as a service/daemon; requires only outbound internet access and network access to your requested integration systems.
Agent registration
- Upon installation, the agent generates a unique 8-character registration code.
- The user enters this code into the Datavine platform to link the agent to their account.
- After linking, the agent is issued a unique certificate and re-establishes a secure connection to the platform.
03Authentication & secure communication
mTLS connection
- All communications between the agent and the Datavine cloud use gRPC over mutual TLS (mTLS).
- Each agent is issued a unique certificate (containing a UUID) after registration, used to authenticate future connections.
- Decommissioning an agent revokes its certificate, blocking further access.
No inbound connectivity
- The agent establishes an outbound connection only; no inbound ports are required.
- The agent has no web interface or open API on the customer network.
04Tenant isolation
Per-tenant certificates
Every agent receives a unique certificate bound to a single Datavine tenant. An agent cannot authenticate as, or communicate on behalf of, any other tenant.
Limited communication channels
Each agent has a very strict limit on the actions it can communicate to the cloud platform. The only request an agent can submit is a registration request. After registering and connecting via mTLS, agents are only able to receive requests from the cloud platform.
This ensures that if an agent were compromised, it could not perform any actions in the Datavine cloud.
05Data handling & logging
No customer data or credentials persisted locally
The agent does not store customer data, credentials, or configuration files on disk. All operational data and any integration payloads are processed in memory only.
Certificate storage
The only persistent file written by the agent is the security certificate received at registration. This certificate is required to establish secure, mutually authenticated connections (gRPC over mTLS) with the Datavine platform.
Logging
- Operational logs (errors, connection events) are transmitted to Datavine over mTLS and retained for a limited period in accordance with our platform policy.
- Logs do not contain customer data payloads.
06Updates & maintenance
Self-updating
- The agent can receive updates directly from the Datavine cloud platform via the secure mTLS gRPC connection.
- Updates are performed in place and require no manual intervention.
Zero configuration
All agent behavior is controlled remotely; there are no local configuration files or user-accessible settings.
Decommissioning
Removal of the agent from the platform instantly revokes its certificate, immediately disabling connectivity.
07Security development practices
Vulnerability management
Security patches and updates are released as required and delivered automatically to all installed agents.
08Customer controls
Visibility
- Customers can view all registered agents and their current status. Datavine administrators can also provide historical connection audit logs on request.
- Agent connectivity can be revoked at any time.
Network controls
Customers retain full control over which internal resources the agent can reach via local network policies and firewall rules.
09Compliance alignment
SOC 2
Datavine has completed a SOC 2 audit. The report is available on request from security@datavine.com.
