An on-premises data gateway alternative that also runs on Mac and Linux
On-premises data gateway alternatives come up for two reasons: there's no spare Windows machine next to the SQL Server, or you need apps, not reports. The AgentUI Connector installs on Windows, macOS or Linux, reads your database over one outbound HTTPS connection, and feeds the apps and AI you build in AgentUI.
It only reads, and you can revoke it in two clicks.
AgentUI Connector vs. Microsoft On-premises Data Gateway
| AgentUI Connector | Microsoft gateway | |
|---|---|---|
| Connection | Outbound only, HTTPS on port 443 | Outbound only, through Azure Relay |
| Runs on | Windows, macOS, Linux | Windows only |
| Data sources | Microsoft SQL Server only | Many sources, SQL Server included |
| Feeds | Apps and AI you build in AgentUI | Power BI, Power Apps, Power Automate, Logic Apps, Analysis Services |
| Writes | Never. It only reads. | Depends on the product using it (Power Apps can write) |
| Install | .exe, .pkg or .deb, or one command | Windows installer |
Neither needs an inbound firewall rule, since both connect out. What changes is which machine it can run on and what it can feed.
Why teams look beyond the Power BI gateway
There's no Windows machine to spare
The gateway needs a Windows machine. The connector also runs on the Linux or macOS machine already on that network.
You need an app, not another report
Build a stock screen, a customer lookup or an approvals list on top of SQL Server, and ask the AI questions about the same data.
IT wants one read-only path
The connector can only read, and the database password never leaves the server.
Nobody on the team wants to own it
One of us walks your IT through the install, so the setup doesn't live in one colleague's head.
Connect your SQL Server in three steps
Install it next to the database
Double-click the .exe, .pkg or .deb, or paste one command. No Node.js needed.
Create the connector in AgentUI
In AgentUI, open Connect Apps → SQL Database and click Create connector. It gives you one command to run on the server.
Check it's online
Your connection shows up as "<name> (on-prem)". If the server reboots or the service crashes, it restarts itself.
What IT will want to check
- The database password never leaves that server, and on Windows it's stored encrypted. AgentUI only holds a fingerprint of the connector key.
- It can run SELECT and WITH queries and nothing else, and it rolls each one back when it finishes.
- Two clicks revoke a connector, and its key stops working within 25 seconds.
- The Your connectors page shows which servers are online.
When to keep the on-premises data gateway
Keep it if your reports live in Power BI, if you pull from Oracle, files or other sources besides SQL Server, or if Power Apps needs to write back to the database. The connector does none of those.
The two are separate services, so you can keep the gateway for Power BI and add the connector for the apps you build in AgentUI.
What the connector won't do
- It reads Microsoft SQL Server only. MySQL, PostgreSQL or Oracle on your network won't work.
- Each query returns up to 1,000 rows and runs for up to 30 seconds. Nothing is copied or kept in sync.
- One workspace holds up to 20 connectors, so each server or site can have its own.
Related
Connect your SQL Server from the machine you already have
Your IT person gets a step-by-step Word guide with screenshots. If they'd like company for the install, we'll join the call.
It only reads, and you can revoke it in two clicks.