Skip to main content
Your database sits in a closed network. Nothing can reach it from the internet, and that is how it should stay. Concatflow connects to it anyway. You run a small agent on a machine that can see the database. The agent opens one outbound connection to Concatflow on port 443. Queries travel down that connection, and results travel back. You open no inbound port. You add no IP allowlist. You set up no VPN.
The agent runs in your network next to the database and opens outbound connections to Concatflow on port 443. Nothing connects inbound.The agent runs in your network next to the database and opens outbound connections to Concatflow on port 443. Nothing connects inbound.

​
What stays with you

  • The database password. It lives in the agent’s environment on your machine. Concatflow never sees it, stores it or carries it.
  • Write access. The agent checks the account before it serves anything. If the account can write, it refuses to start.
  • The off switch. Stop the container and nothing reaches the database. Revoke the agent in the dashboard and Concatflow disconnects it at once.

​
When to use it

Use an agent when the database is not reachable from the internet. That covers a private VPC, an on-premises server, or a database behind a firewall that only lets traffic out. If the database already accepts connections from the internet, a direct connection is simpler. You pick one or the other when you create the dataset, and you cannot switch later.

​
Supported databases

Quickstart

Connect a database through an agent in about ten minutes.

Security model

What the agent can do, and what it cannot.