What you will achieve
By the end of this guide, the BrynQ Agent runs as a Windows service on a server in your own network. BrynQ can then reach the systems you choose (a SQL database, files, an internal REST or SOAP API, or Active Directory) without opening inbound firewall ports, registering DNS records or installing SSL certificates yourself.
ℹ Installing for Sage 100 France? This guide covers the installer from start to finish. The Sage pages of the installer are only listed briefly here (Step 4). For the Sage steps, follow
Sage 100 France module.
Before you start
Tick off this checklist first. Each item prevents a common reason for getting stuck.
- ☐ A Windows server running Windows Server 2016 or newer (64-bit), that can reach the systems BrynQ needs to connect to.
The installer refuses older Windows versions. - ☐ Local administrator rights on that server.
Why: the installer creates Windows services and writes to Program Files and ProgramData. Without these rights, parts of the installation can fail. - ☐ Edge, Chrome or Firefox on the server, to open the local admin page later. Internet Explorer can't show it.
- ☐ Outbound connections from the server (no inbound ports are needed):
https://app.brynq.com, TCP port 443 (the BrynQ API and updates);region1.v2.argotunnel.com and region2.v2.argotunnel.com, port 7844 (UDP, with TCP as fallback). This is the secure connection to BrynQ. It cannot go through a proxy, so port 7844 must be open directly.
Behind a proxy that asks for a sign-in (NTLM or Kerberos)? Allow the server's computer account (DOMAIN\SERVER$) on the proxy. See Network settings of the BrynQ Agent. - ☐ A customer-scoped BrynQ API token. It must be linked to exactly one customer: the customer this Agent belongs to. Ask BrynQ for it. See The API token for the BrynQ Agent.
Why: BrynQ uses this token to set up the secure connection and to deliver updates. A token for several customers is rejected. If you limit the token to certain IP addresses, add the public IP address of this server. - ☐ Know which modules you need (see Step 3). Ask BrynQ support if you are not sure.
- ☐ For the SQL Server module only: the SQL Server name, and an account (Windows or SQL Server login) with access to the databases BrynQ needs.
Step 1: Download the installer
📍 Where: BrynQ, in a browser on the Windows server.
- Sign in to BrynQ and go to Organization > Agent. The page is called BrynQ Agent.
Don't see it? Ask an administrator to add the permission Access to download the BrynQ Agent to your role. - Check the latest Version card. Select Click here to read the full release notes if you want to review the changes first.
- Click Download and save the installer (
brynq-agent-installer-<version>.exe) on the server.
Need an older version? Use Older versions on the same page. Each version shows its release date, release notes and a Checksum (SHA-256) for your IT integrity checks. Use the latest version unless BrynQ support tells you otherwise.
ℹ Security warning? The installer is signed by
Salure ICT BV (BrynQ's legal entity). Windows or your browser may still warn about a new file. See
Security for how to verify the signature.
Step 2: Run the installer
📍 Where: the Windows server.
- Right-click the installer and choose Run as administrator.
- Select Setup Language: choose English, French, German or Dutch. The Windows display language is preselected. All BrynQ pages follow this language. The license agreement is always in English, and Sage screen names stay in French.

- License Agreement: read it carefully. Section 7 (Support and Diagnostics) describes what BrynQ support can read on the server. If you agree to it and want to use the BrynQ Agent, accept it to continue.
- On a first installation: keep the default installation folder (
C:\Program Files\BrynQ\Agent) unless your organization requires another location. - Cloud connection: paste the BrynQ API token. BrynQ checks the token while you type. Next only works once you see BrynQ accepts this token.

Other messages you may see:- BrynQ does not accept this token (for example TOKEN_NOT_FOUND or TOKEN_EXPIRED): check that you copied the whole token, or ask BrynQ for a new one.
- BrynQ only accepts this token from other IP addresses. Add the public IP address of this server to the token in BrynQ.
- The token is not an agent token: an agent token is linked to exactly one customer. Use the agent token of this customer.
- BrynQ could not be reached or did not answer: check the outbound connection to
app.brynq.com, then click Check again.
Running the installer again on a server that is already connected? Choose Keep the existing API token (recommended) or Replace it with a new API token.
Step 3: Choose the modules
Key idea: a module is one type of connection the Agent offers to BrynQ. Only the modules you select are available; all others stay closed. On a new installation, nothing is selected.
The Modules page groups the modules under Data sources, API proxies and Payroll integrations. Select a module to read its description on the right.
| Module | Select it when BrynQ needs to... |
| SQL Server | run queries on a SQL Server database in your network. |
| File Management | upload, list or download files and folders on the server or network. |
| Active Directory | read or update Active Directory (LDAP). |
| REST Proxy | call an internal REST API. |
| SOAP Proxy | call an internal SOAP web service. |
| Sage 100 France | import data into Sage 100 Paie & RH. This also turns on SQL Server and File Management (shown greyed out). See Sage 100 France module. |

Select only what you need. To change the modules later, run the installer again. On a re-installation, the modules that are already on show an Enabled tag.
Step 4: Sage pages (only for Sage 100 France)
When you tick Sage 100 France, the installer first scans the server and then shows these pages. The Sage screen names stay in French in every language.
- Sage — Select Companies: tick the companies BrynQ imports into.
- SQL Server connection and Databases (Step 5). The SQL Server comes from the Sage files. The connection page is skipped when that connection already works.
- Sage service account: paste the Code and Token of the service account you create in Sage.
- Sage installation: only shown when there is more than one Sage installation to choose from.
- Sage import models: create BrynQ's three import models in Sage. Next works once all three are found and Sage is closed.
- ConnectImport scenario: keep Let BrynQ create the scenario (recommended).
Follow Sage 100 France module for each of these pages step by step.
Step 5: Set up the SQL connection (only for SQL Server)
🔍 The installer detects most values for you. It finds the local SQL Server instances and the installed SQL Server ODBC drivers, and offers them in the dropdowns. Usually you can pick the suggested value. Only look things up yourself if something is missing or you don't recognise it.
On the SQL Server connection page:
- Server: pick the suggested SQL Server, or type its name (for example SERVERNAME or SERVERNAME\INSTANCE). With Sage 100 France, the server is taken from the Sage files.
- Login method: choose Windows authentication or SQL Server authentication. Only SQL Server authentication asks for a Username and Password. The account needs access to the databases BrynQ uses.
- Leave Advanced... as it is unless your database administrator says otherwise. It holds the ODBC Driver and the Extra connection options (default
Encrypt=no;TrustServerCertificate=yes). - Click Test connection. You see Connection successful, or the reason why the connection failed.

Running the installer again? Choose Keep the current settings (recommended) or Change the settings.
On the Databases page, choose which databases the BrynQ interfaces use:
- Only the databases I select (recommended): tick them in the list. Missing one? Click Database not in the list? to add its name.
- All databases on this server: includes databases that are added later.

⚠ This choice does not limit access. It only records which databases the interfaces use. To limit access, give the SQL login rights on those databases only.
The SQL settings are stored only on your server. You can change them later in the local admin dashboard.
Step 6: Finish and check
- Additional options:
- Shortcuts: Create a desktop shortcut (recommended) and Create a Start Menu shortcut open the admin dashboard later.
- BrynQ support: keep Share advanced diagnostics (recommended) ticked so BrynQ support can solve problems faster. What does BrynQ support see? explains what is shared. You can change this later on the admin dashboard under Troubleshooting.
- Network: tick Use custom local network settings only when another program on the server already uses port 7070 or 7071.
Defaults: listen IP 127.0.0.1, Agent port 7070, local admin port 7071.

- Check the summary on Ready to Install and click Install. The installer shows its progress per step. If the last step fails, a Retry dialog lets you try again with every choice kept.
- When the installation is done, keep Open the BrynQ Agent dashboard ticked and click Finish.

✅ Checkpoint:- Open Task Manager > Services. BrynQAgent and BrynQCloudflared have the status Running. (With Sage 100 France there is a third service: BrynQSageImport.)
- Open
http://127.0.0.1:7071/admin in a browser on the server. The Home page shows your Agent address and BrynQ connection: Connected. - Open
C:\ProgramData\BrynQ\Agent\config\public_url.txt. It contains your Agent address: https://<your-customer>.brynq-agent.com.
✖ Something not right? See
Troubleshooting the BrynQ Agent. The installer keeps a copy of its log in
C:\ProgramData\BrynQ\Agent\logs\installer\setup-<date>-<time>.log. Did the installation stop because a BrynQ folder was created by another user? The message names the
takeown command that fixes it.
Step 7: Use the Agent in BrynQ
When you set up an interface that uses the Agent, enter the Agent address from public_url.txt (https://<your-customer>.brynq-agent.com) in the authorization of that app in BrynQ. The template guide of your interface tells you exactly where.
What gets installed
| What | Where |
| Program files | C:\Program Files\BrynQ\Agent (or the folder you chose) |
| Settings | C:\ProgramData\BrynQ\Agent\config (only administrators and Windows itself can read it) |
| Log files | C:\ProgramData\BrynQ\Agent\logs (installer logs in the installer subfolder) |
| Windows services | BrynQAgent (the Agent), BrynQCloudflared (the secure connection to BrynQ), BrynQSageImport (only with Sage 100 France). All start automatically (delayed) when Windows starts. |
Next steps