One small service, on one server, next to your data.
The gateway is the only part of Sonela that runs inside your network. It dials out
to us over port 443 and asks whether there is work — so you open no inbound ports,
and nothing of yours is exposed to the internet. It is a single file: download it,
apply the settings your dashboard shows you, run it as a service.
1
Outbound only
It calls us; we never call it
The gateway opens the connection, over the same port 443 your browser uses, and
asks whether there is a question waiting. There is no inbound port to open, no
VPN to stand up and no tunnel to maintain. If the machine can browse the web, it
can run the gateway.
2
Stays on your machine
What it needs to reach your database stays there
Everything the gateway needs in order to sign in to your database is configured
on that one machine and stays on it — never sent to Sonela, never written to a
log, never echoed back. We hold only a hash of the gateway's own key, so even
that cannot be read back out of us.
3
Runs on your side
The same read-only checks, on your server
Every statement is validated as a single read-only SELECT over the schema you
approved, and rewritten with your tenant filter — inside your network, before it
reaches your database. Then it runs in a READ ONLY transaction with a
three-second statement timeout and a 500-row cap. Same code as a direct
connection, different address.
Download
Get the gateway.
One file per platform, self-contained — no runtime to install first. Each build
publishes its SHA-256 alongside it, so you can check what you downloaded before you
run it.
The gateway's key comes from your dashboard: sign in, add a gateway data source,
and the key appears once — with the settings to paste, ready to apply on the
machine that runs it.
Installing it
An afternoon's work, and most of that is deciding where it runs.
Pick one server that can already reach your database and browse the web. Download
the file for its platform and check the SHA-256. Apply the three settings your
dashboard shows you — it prints them ready to paste — and start it as a service so
it comes back after a reboot. The dashboard turns green when it connects.
Covers Windows and Linux, running it as a service that survives a reboot, checking
that it connected, rotating the key, uninstalling, and the first few things that
actually go wrong.
Your data never leaves the building. The answers do.
Open a workspace, add a gateway data source, and the key and the settings are on
screen in under a minute, ready to paste.