Tätä artikkelia ei ole vielä käännetty suomeksi.
To utilise the Nepton platform, customer networks must be able to connect to it via the public internet. Below is a collection of all network requirements, which can be used by a network specialist to ensure good connectivity.
IP addresses defined in this document are subject to change but will be communicated well in advance of any transition date.
Nepton services
Below are the connectivity details for the Nepton platform and all of its services.
To avoid any issues with future upgrades or changes in your subscription, it is recommended to permit access to all of the domains and ports mentioned for each environment you will use (production or testing).
Production use
The latest version of the Nepton platform and all of its features and services. Unless you have an instance of Nepton on your own private server, these are the connectivity details that are relevant to you.
Portal, Employees (HR), and management services
| Notes | Mandatory for browsers, mobiles, wall terminals, API and automated integrations |
| Domain | go.nepton.com |
| IP address | 83.150.75.175 |
| TCP Ports | 80 and 443 |
Wall terminals, Worktime and management services
| Notes | Mandatory for browsers, mobiles, wall terminals, API and automated integrations |
| Domain | time.nepton.com |
| IP address | 83.150.75.169 |
| TCP Ports | 80 and 443 |
Web analytics
| Notes |
Mandatory for browsers and mobiles |
| Domain | piwik.nepton.com |
| IP address | 83.150.75.169 |
| TCP ports | 80 and 443 |
Public testing
Available by special agreement, a testing environment can be used by customers via the public internet. This environment can be updated to any version of the platform, even including near-future changes.
Portal, Employees (HR), and management services
| Notes | Mandatory for browsers, mobiles, terminals, API and automated integrations |
| Domain | publictesting-go.nepton.com |
| IP address | 83.150.75.166 |
| TCP ports | 80 and 443 |
Wall terminals, Worktime and management services
| Notes | Mandatory for browsers, mobiles, wall terminals, API and automated integrations |
| Domain | publictesting-time.nepton.com |
| IP address | 83.150.75.165 |
| TCP ports | 80 and 443 |
SFTP data transfers
Nepton SFTP service
On request, Nepton can provide an SFTP service for integration purposes. Credentials are issued upon delivery of the account.
| Description | Customer opens outbound connection to Nepton SFTP service. This can be used to transfer data in/out from Nepton |
| Customer IP address |
Customer must inform Nepton about the static IP address they use to interact with the Nepton SFTP service.
Note that dynamic cloud IP addresses are not sufficient. Always use static cloud IP addresses instead |
| Nepton Domain | transfers.nepton.com |
| Nepton IP address | 83.150.75.188 |
| Nepton TCP port | 22 |
Customer SFTP server
If customers wish to use their own SFTP server for integrations, they should inform Nepton about their SFTP server Domain/IP, TCP port, and credentials.
Customers should open ALL of the following firewall rules on their network to permit Nepton access.
Required for HR and management service to use
| Description | Customer opens an inbound connection. This can be used to transfer data in/out from Nepton |
| Nepton domain | go.nepton.com |
| Nepton IP address | 83.150.75.175 |
| Nepton TCP port | 22 |
| Customer Domain/IP address | Customer specifies this |
Required for Worktime and management service to use
| Description | Customer opens an inbound connection. This can be used to transfer data in/out from Nepton |
| Nepton Domain | time.nepton.com |
| Nepton IP address | 83.150.75.169 |
| Nepton TCP port | 22 |
| Customer Domain/IP address | Customer specifies this |
Required for administrative access by Nepton specialists
| Description | Customer opens an inbound connection. Used to create, deploy and test integrations |
| Nepton IP address | 79.134.102.194 |
| Nepton TCP port | 22 |
| Customer Domain/IP address | Customer specifies this |
Wall terminals
Unless a bespoke configuration has been agreed, terminals fetch their IP addresses from the customer DHCP server. Terminals do not support AD or proxy technologies.
Wall terminals require access to the Production domains, IP addresses and TCP ports mentioned under the Nepton Services - Production use heading, above.