Platform
On-Premise Systems
How to Connect to a Local On-Premise System
Keep your ERP or database on your own servers and still connect it to Salesforce, HubSpot or Dynamics 365. Rapidi reaches it from inside your network, so the server never has to face the internet.
Rapidi connects to a local on-premise system through RapidiConnector, a small Windows service you install on a server inside your own network. It opens an encrypted outbound connection to the Rapidi cloud service and keeps it open, so you do not open inbound firewall ports or need a fixed IP address.
- What you install
- RapidiConnector, a small Windows service, on a machine that can see your local system.
- What you open in the firewall
- Nothing inbound. Outbound traffic only, on port 80 and the service port shown in MyRapidi.
- How the data travels
- Compressed and encrypted with TLS 1.2 or TLS 1.3.
How does RapidiConnector connect an on-premise system to the cloud?
Your local system stays where it is. RapidiConnector sits next to it, calls out to the Rapidi cloud service and carries the data both ways over that one connection.
When RapidiConnector starts, it looks up the address of your Rapidi service, connects to it and keeps that connection open. The Rapidi cloud service runs your transfers on the schedule you set and sends each request down that open line. RapidiConnector reads or writes your local system and sends the result back.
That is why the setup works behind a normal company firewall. There is no inbound firewall rule to approve and no fixed IP address to arrange.
Is connecting an on-premise system to the cloud secure?
The security questions an IT team asks first, answered from the Rapidi documentation.
| Connection direction | Outbound only, from RapidiConnector to the Rapidi service. No inbound ports are opened. |
|---|---|
| Firewall rules | Allow outbound traffic on port 80 and on the service port shown in MyRapidi. |
| Fixed IP address | Not needed. |
| Encryption in transit | TLS 1.2 or TLS 1.3, normally AES-128 or stronger depending on the Windows version. Your own SSL certificate can be used on request. |
| Sign-in to your system | Windows authentication, using the account RapidiConnector runs under, or a user for that system. Stored credentials are encrypted with a key kept separate per customer. |
| Data kept in the cloud | No customer data is stored on Rapidi servers, unless you choose a centrally hosted mirror. |
| Where Rapidi is hosted | AWS, in the EU Frankfurt region or the US West Oregon region. |
| Monitoring | The MyRapidi dashboard shows every connected RapidiConnector, the IP address it connects from and its version. Errors are written to the Windows Event Viewer. |
Source: the Rapidi documentation for Security in Rapidi, Installing the RapidiConnector, Where Rapidi is hosted and the Dashboard, read 16 September 2026.
How do you install RapidiConnector?
Five steps, done once on the server that sits next to your system.
Download RapidiConnector
In MyRapidi, open the connection to your local system, expand RapidiConnector and download the installer. There is a 32-bit and a 64-bit version. NAV through C/Front needs the 32-bit one.
Install it on a machine that can see your system
Run the installer as administrator on an application server or in the DMZ, next to the system you want to connect. Add the client or driver that system needs, for example the SQL Server client.
Link it to your Rapidi service
Open the RapidiConnector Service Controller, enter the Rapidi Service ID, user ID and password shown in MyRapidi, press Verify, then Install.
Start the service and check the dashboard
Start the Windows service. The MyRapidi dashboard shows the connector as connected, with the IP address it connects from and its version.
Test the connection and read the design
Press Test on the connection, then Read Design to load the tables and fields. From here the transfers are set up on screen, not written as code.
Source: the Rapidi documentation for Installing the RapidiConnector, read 16 September 2026.
Which on-premise systems can Rapidi connect to?
RapidiConnector reaches the systems below. Each one needs its own client or driver on the same machine, and nothing is installed inside the system itself.
| Dynamics NAV and Navision | Through C/Front, SQL Server, Web Services or OData, including Navision 3.56. See the Dynamics NAV connector. |
|---|---|
| Dynamics AX | Through the SQL Server database, Web Services or OData. |
| Dynamics GP | Through SQL Server, including stored procedures. See the Dynamics GP connector. |
| Dynamics C5 and XAL | Supported as local systems. See the Dynamics C5 connector. |
| Dynamics CRM on-premise | Supported as a local system. |
| Databases | Microsoft SQL Server, Oracle, MySQL, IBM DB2, SQLite and any database with an ODBC driver. See the SQL Server connector. |
| Other local services | Lotus Notes, and REST or OData services that are only reachable inside your network. |
Source: the connection pages in the Rapidi documentation that include an Installing the RapidiConnector section, read 16 September 2026.
On-premise, cloud or hybrid: which setup fits?
The same Rapidi service handles all three. What changes is where the transfers run and whether RapidiConnector is needed.
| What you are comparing | Cloud system | On-premise system | Hybrid engine |
|---|---|---|---|
| Example | Salesforce, HubSpot, Business Central online | Dynamics NAV or SQL Server on your own server | Two local systems that must keep syncing even when the internet is down |
| RapidiConnector needed | No, Rapidi connects directly | Yes | A local Rapidi Hybrid service runs the transfers next to your systems |
| Where transfers run | Rapidi cloud service | Rapidi cloud service | On your own server |
| Internet needed to run | Yes | Yes | No, only to download changes you make in MyRapidi |
| Data leaves your network | Yes, between the cloud systems | Yes, encrypted, to reach the other system | No, when source and target are both in your network |
| Plans | All four plans | All four plans | Enterprise and Unlimited |
Source: the Rapidi product update on Hybrid service installation, the OData connection documentation and the Rapidi plan comparison, read 16 September 2026.
In their own words
Who already connects an on-premise system this way?
Held: this block needs a named Rapidi customer who runs an on-premise system through RapidiConnector, with an attributed quote they have approved. The Sea Breeze case story describes an on-premise Dynamics NAV connected to Salesforce, but it carries no approved quote about the connector, so none is shown.
Where do you go next?
Platform
Rapidi technology
The platform, the Replicator and the connection technology behind every Rapidi integration.
Technology
Connectors
Every system Rapidi connects to
Cloud and on-premise, from Dynamics and Salesforce to SQL Server, Oracle and REST.
All connectors
Integration
Salesforce and Dynamics NAV
The most common on-premise case: a local NAV connected to Salesforce in the cloud.
See the integration
Your setup
Ask about your own servers
Tell us what runs on your network and what it has to talk to, and we will say plainly how Rapidi covers it.
Talk to a consultant
Last reviewed: 16 September 2026
Frequently asked questions
Can a cloud integration platform reach a system behind our firewall?
Yes, when something inside the firewall starts the conversation. With Rapidi that is RapidiConnector, a small Windows service in your network. It connects out to the Rapidi cloud service and keeps the connection open, so the cloud never has to reach in.
Do we have to open inbound ports in our firewall?
No. The connection from RapidiConnector is outbound only. You allow outbound traffic on port 80, which it uses to look up the Rapidi service, and on the service port shown in MyRapidi. No inbound ports and no fixed IP address are needed.
Is the data encrypted between our network and Rapidi?
Yes. Every connection between the Rapidi servers and a locally installed RapidiConnector uses TLS 1.2 or TLS 1.3, normally with AES-128 or stronger depending on the Windows version. The data is also compressed on the way.
Is our data stored in the Rapidi cloud?
No. According to the Rapidi security documentation, no customer data is stored on Rapidi servers. The one exception is the Rapidi Mirror Technology, if you choose a centrally hosted mirror.
Where can RapidiConnector be installed?
On a Windows machine that can reach the system you connect: an application server, a server in the DMZ, or a virtual machine in Azure. It does not install anything inside the ERP or the database itself.
Can we run more than one RapidiConnector?
Yes. You add one for each extra NAV, AX or SQL Server instance or company, and 32-bit and 64-bit connectors can run side by side on the same computer.
How is RapidiConnector kept up to date?
Upgrade it when Rapidi support advises. Support can normally upgrade it remotely, and the protocol is backward compatible, so an older connector keeps working with a newer central service.
Do cloud systems need RapidiConnector too?
No. Systems that are reachable from the internet, such as Salesforce, HubSpot or Business Central online, connect directly. RapidiConnector is only for systems inside your own network.
What does connecting an on-premise system cost?
Connecting to on-premise systems is included in all four Rapidi plans. The Hybrid engine, which runs transfers on your own server, is part of the Enterprise and Unlimited plans.
Is your on-premise system ready to connect?
Tell us what runs on your servers and what it has to talk to, and we will tell you plainly what the setup involves.