On-premise data integration In development

Your data can stay inside your network.

SteadyState Connector securely links internal databases, ERP systems, shared files, and legacy applications to managed data workflows — without exposing those systems directly to the internet.

Talk About Your Internal System See How It Works

Outbound connections. Controlled access. No public database exposure required.

SteadyState Connector is in active development. There is no download yet — we are scoping early integrations directly with customers. If your data is stuck on an internal system, that is a useful conversation to have now.

Still running important systems inside the building?

That's not unusual. Many businesses rely on systems that were never designed to connect securely to modern cloud services.

Internal SQL Server

Your ERP or reporting database only exists on the local network.

Legacy ERP

The system works, but nobody wants to expose it directly to the internet.

Shared network files

Critical CSV, Excel, or export files land on a local Windows share.

No integration team

Your internal IT team keeps the systems running, but does not build APIs or data pipelines.

Security concerns

Opening firewall ports or publishing a database publicly is not an acceptable solution.

Manual workarounds

Employees export files by hand because getting data out automatically seems too complicated.

SteadyState Connector gives those systems a controlled way to participate in automated workflows — without redesigning the environment, and without moving your on-premises systems to the cloud.

A secure connection from the inside out.

Inside your network, the ERP, SQL Server, or file share is read by the SteadyState Connector. The connector then opens an outbound HTTPS connection to SteadyState, where managed workflows process the data and deliver it to reporting, a database, or another destination. Nothing connects inward from SteadyState to your database.

01
Install
A small connector service is installed on a Windows or Linux machine that already has access to the internal data source.
02
Configure
The connector is given access only to the systems and data the integration requires.
03
Retrieve
When a managed workflow runs, the connector performs the approved extraction or process locally.
04
Transfer
The resulting data is sent outbound to SteadyState infrastructure, or directly to the approved destination.

Your internal database does not need to accept inbound internet traffic.

Built for the systems businesses actually have.

Imagine a manufacturing company whose ERP has been running reliably for fifteen years. The application stores its data in Microsoft SQL Server on the internal network. Finance exports reports by hand, because the company has no API, no data engineering team, and no desire to expose SQL Server publicly.

Before

Every morning:

1.An employee logs into the ERP
2.Several reports are exported
3.CSV files are copied into another system
4.Totals are checked by hand
5.Results are emailed to management

With SteadyState Connector

A managed process:

1.The connector queries approved SQL Server views locally
2.Data is validated before transfer
3.The extracted data is sent outbound over an encrypted connection
4.SteadyState workflows process and reconcile it
5.Reports and downstream systems are updated automatically
6.The team is alerted only when something goes wrong

The ERP can stay exactly where it is. The manual process does not have to.

Security

Designed to minimize exposure.

Outbound-only communication

The connector starts the conversation with SteadyState infrastructure. In a normal deployment you should not need to expose SQL Server, SMB shares, or internal applications to public internet traffic.

Encrypted transport

Connector communication uses HTTPS/TLS.

Dedicated connector identity

Each connector installation has its own identity and credentials, so access can be reviewed or revoked on its own.

Least-privilege data access

The database account the connector uses holds only the permissions the integration requires — read-only wherever that is possible.

Restricted jobs

A connector runs only the jobs it has been configured for. It is not open-ended remote access to your database.

Customer-specific isolation

Configuration and connector identities are kept isolated between customers.

The goal is not to give SteadyState broad access to your network. The goal is to give one integration exactly the access it requires.

Access only what the workflow needs.

When connecting to an internal database, we recommend creating a dedicated service account and restricting it to the tables or views the integration actually uses.

A dedicated account

steadystate_reader

Preferably

SELECT access only

And, where possible, integration views

integration.vw_daily_sales
integration.vw_inventory
integration.vw_customers

This lets the integration do its job without giving the connector broad access to the ERP database.

Common connector targets

More than SQL Server.

Databases

Microsoft SQL Server
PostgreSQL
MySQL
Oracle
ODBC-accessible databases

Files

CSV
Excel
JSON
XML
Local folders and network shares

Internal applications

Internal REST APIs
SOAP services
ERP systems
Accounting platforms
Custom business applications

Transfer systems

SFTP
Internal file servers
Scheduled exports

If the system can be reached from inside your network, there is a good chance we can integrate with it. Tell us what you're running and we'll tell you honestly whether it fits.

Move only what needs to move.

A connector does not require replicating your whole database. Which pattern fits depends on the integration — these are the ones we use most.

Query and transfer
Retrieve only the records the destination needs and send those.
Incremental extraction
Transfer only records that changed since the previous successful run.
File delivery
Generate a CSV, JSON, or Parquet file and transfer it securely.
Direct destination delivery
Where appropriate, send data straight to an approved destination rather than storing it in SteadyState systems.
Local processing
Some transformations can happen locally, before any data leaves your network.

Orchestrated without opening the database.

SteadyState's managed workflow platform schedules and monitors the jobs that use the connector — but the workflow platform never needs a direct network connection to your database.

A managed workflow requests an approved extraction
The connector, inside your network, receives the request
It connects locally to the internal SQL Server
Results are returned to the connector
The connector transfers them outbound over an encrypted connection
The managed workflow continues

Scheduling and monitoring happen centrally. Internal system access happens locally.

Often simpler than building a VPN.

Different environments call for different architectures. A VPN isn't wrong — it's just a heavier tool than many integrations need.

Approaches to connecting internal systems and where each fits best
Approach	Best fit
SteadyState Connector	Targeted access to specific internal systems and data
VPN / private network	Broader network-level integration requirements
Cloud private networking	Organizations already operating primarily in AWS, Azure, or Google Cloud

We choose the simplest architecture that meets the security and operational requirements. For many small and midsize businesses, an outbound connector is easier to deploy and safer to scope than broad network connectivity.

A connector isn't useful if nobody knows it stopped working.

What gets watched

Connector heartbeat and last successful connection
Last successful job, and how long it took
Row counts and transfer status
Authentication and database connection errors
Job failures — surfaced to us, not left for you to notice

Acme Manufacturing

ERP Connector

Online

Last heartbeat: 32 seconds ago
Last successful job: 5:04 AM
Database: Connected
Rows extracted: 28,491
Job duration: 38 sec
Status: Success

Illustration of the signals we monitor for a connector deployment.

We handle the integration work.

You should not need an internal data engineering team to deploy a connector. We walk through it with you:

Choose an appropriate machine or server
Install the connector
Establish a dedicated service account
Confirm local system access
Test outbound connectivity
Configure the approved jobs
Validate the results against what the business expects
Enable monitoring

Your internal IT will still be involved in a few places, and that's normal:

Installing software on a company machine
Granting database permissions
Approving outbound HTTPS from that machine
Creating the service account

Is this the right tool for your situation?

A good fit when…

Your ERP or accounting system is hosted on-premises
Your data lives in SQL Server or another local database
Employees export reports or files by hand
You don't want to expose databases publicly
You have no internal data engineering team
Data needs to move regularly into another application or reporting environment
Your existing integration is fragile or undocumented
An internal data process needs monitoring around it

Probably unnecessary when…

If the source system already has a secure public API or a native cloud integration, adding a connector may just add complexity.

You already have mature private-cloud networking
The source is already securely accessible
A native vendor integration solves the problem
The workflow doesn't involve internal systems at all

We recommend the simplest secure architecture, whether that uses SteadyState Connector or not.

Need only a simple recurring extraction?

SmallDataPipes, with the connector behind it.

SteadyState Connector can also power SmallDataPipes integrations when the source data lives inside your network — so a straightforward SQL, file, or ERP export can be automated without turning it into a larger consulting project.

Explore SmallDataPipes ↗