Net-Base Install, sign in and update netERP – netERP Manual

Install, sign in and update netERP – netERP Manual

Install the netERP-Client from Windows, Linux and macOS, connect it to the server, log in, and keep it up to date.

Overview

Install, sign in and update netERP – netERP Manual im überblick

Passende Leistungs- und Technikpfade

Wichtige Vertiefungen zu diesem Thema

ServicesThe overall picture of architecture, modernization, services, portals and support.TechnologiesDelphi, C#, data access, REST and platform strategy as the technical foundation at a glance.ProjectsProject types, target architectures and typical evolution paths for enterprise software and portal logic.FAQ CenterConsolidate and categorize typical project questions on modernization, Delphi, portals, interfaces and operations.
netERP LogonetERPManualDownload netERP

Installing, signing in and updating netERP

Within minutes the client is installed and connected to your netERP server.

Install on Windows

  1. Open the download page and choose Windows 64 Bit. Only older 32-bit systems require Windows 32 Bit.
  2. Run the setup. It is signed with the signature of Net-Base Software GmbH and is available in German, English, French and Spanish.
  3. Choose for all users or only for me. When installing for all users, the setup also adds the netERP server’s certificate as trusted.
  4. If needed, create a desktop shortcut and start netERP at the end of the setup.

Install on Linux

For Ubuntu, Debian and related systems there is a DEB package, for Fedora, CentOS and RHEL an RPM package. After downloading, open a terminal in the download folder:

sudo apt install ./neterp_*_amd64.deb      # Ubuntu, Debian
sudo dnf install ./neterp-*-1.x86_64.rpm   # Fedora, CentOS, RHEL

netERP is installed to /opt/neterp, appears in the application menu and starts with neterp. Without a package manager, extract the TAR.GZ archive and run ./neterp/install.sh – without sudo for a single user, with sudo for all users; uninstall.sh removes it again.

Installing on macOS

  1. On the download page select macOS Apple Silicon and open the DMG.
  2. Drag netERP to the Applications folder and start it from there.

The DMG is signed with a Developer ID and notarized by Apple; macOS launches netERP without additional approval. The Mac client has been tested on macOS 26 with Apple silicon.

Connecting to the server

On first start – or if you hold Ctrl while starting – the Server Connection dialog appears. Enter the address of your netERP server and verify it with Test Connection; Default sets the predefined address. For the Public Beta you will receive the address and credentials on request.

The client connects over an encrypted channel and accepts only the netERP server’s certificate.

Signing in

  • Windows sign-in (Single Sign-on): If the server is configured for it, netERP signs you in via Windows with your Windows account, without any dialog.
  • Username and password: Otherwise the sign-in dialog appears. Accounts are created locally by the administrator or imported from Active Directory.
  • After five failed attempts the account is locked for 15 minutes.

Updates

Shortly after signing in, netERP checks whether a new version is available. To check manually go to File → Account → Check for updates.

  • Windows: After your consent netERP downloads the installer in the background, verifies the signature and the SHA-256 checksum, installs it after quitting and restarts. If any verification fails, nothing is installed.
  • Linux and macOS: The notice offers to open the download page. Install the new version as you did the first time; settings are preserved.

The installed version is shown under File → About.

netERP-Dashboard nach der Anmeldung
Screenshot from netERP using fictitious sample data.
netERP Manual
As of: October 2026 · Public Beta

All images were generated automatically by netERP using fictitious sample data.

Next step

If you have a concrete modernization, API or platform question, we should establish the technical scope clearly and early.

Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.

  • Current state, target state and technical risks are assessed jointly.
  • REST, data access, portals and rollout are not deferred to a later stage as secondary consequences.
  • You can see early on which path is economically and operationally viable.
Request project consultationView referencesTypical project questions in the FAQ center