/ SONDA · ENTERPRISE

One program on a server of yours. Nothing of ours anywhere.

For the organizations whose data must stay on their own servers: Sonda Server keeps the team store on its own disk, or stands in front of the bucket or the MongoDB database you already have and holds its credentials — so no member's computer ever receives them. A static binary, no runtime, TLS 1.3 only, and a port that answers nothing at all to anyone without the token.

LINUX AMD64 · ARM64 · WINDOWS AMD64 TLS 1.3 ONLY PORT 50704 SERVICE INSTALL

Setup, question by question

1The store: a folder on this disk, or S3, Azure, Google Cloud, SSH, WebDAV, Git or MongoDB in front of which the server stands. Opened right away.
2The organization: its name, the first division, the administrator's username, name, email and password — secrets typed unseen.
3The port, the listen address, the allowed networks.
4The certificate: its own, self-signed for ten years, or the team's, or a proxy in front.
=One line: address, token and fingerprint. Pasted into Sonda, it fills all three.
/ THE WHOLE SURFACE

Anyone can reach a port. What matters is what it says back.

Every Sonda of the team talks to one port on a server of yours, with TLS 1.3 on both ends. Behind it is the store: a folder on the server's own disk, or the bucket or the MongoDB database you already have, with the server holding its credentials so no member's computer ever receives them.

In front of it are the checks a call meets: the allowed networks, the one certificate, the token, a sign-in the server checks itself, and the account read again while it works. A call that fails one of them gets nothing of the team's, and nothing of LockFlare's is anywhere in the path.

/ WHO IT ANSWERS

The port is the whole surface, so the port is strict.

Six rules, in the order a call meets them.

Outside the allowed networks, closed on arrival.

Connections from outside the allowed CIDRs are closed on arrival, before the handshake. Addresses inside them are never dropped.

One certificate, pinned.

TLS 1.3 on both ends. The fingerprint is pinned on the repository and travels in tickets; a pin is the one certificate taken, and a CA-vouched certificate is refused in its place unless the pin is taken off on purpose.

Nothing without the token.

A call without the token gets an empty 404 and nothing is read; a wrong token and a wrong address look the same from outside. The token is 32 random bytes, kept only as its SHA-256, said once, replaced in one command. An address that keeps calling without it is dropped for a minute, then longer, up to fifteen.

The token alone opens no file.

It reaches only what a sign-in needs: the organization document, the indexes, the SSO settings, invitations and join requests. No file of the team's.

Sign-in, checked by the server.

Each person signs in with a username and a password the server checks itself, with the same code a Sonda uses, and keeps nowhere. A pass is issued and stored only as its hash. Ten failures in ten minutes block that username for five; an unknown username costs the same work and gets the same sentence.

Cut off at the next call.

The users index is re-read every ten seconds. A paused or revoked account, or a password set again by an administrator, is refused at its next call. A session idle for fifteen minutes is closed.

/ ON THE BOX

Installed like a service. Kept like a secret.

Linux amd64 and arm64 as one static binary for any distribution; Windows amd64. Logs to journalctl or to a file.

On LinuxA systemd unit with NoNewPrivileges, restarting on failure, running as the configuration's owner, never as root. Files 0600 and folders 0700; a configuration, recovery file or key that other accounts can read is refused.
On WindowsA service that installs only where administrators alone can change the program, its folder and its configuration — and prints the line to fix it if not. Every file carries its own ACL — SYSTEM, Administrators and the run account — and a file anyone else can reach is refused.
Folder storeThe server is its only writer, held by the operating system's lock. A write is whole or not there: temp file, fsync, rename. Two publishes in the same instant never both land.
The only copyThe folder is the only copy of the team's store. Back it up with the store tools.
/ THE SETUP

Five minutes, one terminal.
Nothing to configure afterwards.

This is the whole installation, as the server prints it: download, one question per line, and at the end the one line a Sonda is given. The addresses, the token and the fingerprint below are placeholders — the real ones are said once, on your server, and nowhere else.

ops@store-1 — sonda-server -setup
LINUX · AMD64
ops@store-1:~$ curl -L -o sonda-server-linux-amd64.tar.gz "https://cdn.lockflare.com/sonda/server/sonda-server-linux-amd64.tar.gz?v=1.0.1"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
100 11.8M  100 11.8M    0     0  1712k      0  0:00:07  0:00:07 --:--:-- 1714k
ops@store-1:~$ sha256sum sonda-server-linux-amd64.tar.gz
3f1b…c9e0  sonda-server-linux-amd64.tar.gz
ops@store-1:~$ tar -xzf sonda-server-linux-amd64.tar.gz
ops@store-1:~$ ./sonda-server -version
sonda-server 1.0.1
ops@store-1:~$ ./sonda-server -setup
Sonda Server 1.0.1 — setup
/home/ops/sonda-server.json is written at the end, and not before. Enter keeps what is in [brackets]; a single - empties it.

1  Where the team store is kept
  1  A folder on this server
  2  S3-compatible storage
  3  Azure Blob Storage
  4  Google Cloud Storage
  5  SSH
  6  WebDAV
  7  Git repository
  8  MongoDB
  [1]: 1
Folder — the folder on THIS server that holds the store: absolute; made when it is not there
  [/home/ops/store]: /home/ops/newstore
  This folder is the only copy of the team's store: it is the one to back up. One Sonda Server writes it.

Opening the store…
  the folder store answers — 0 at its root; it refuses a write based on a version it no longer holds

2  The organization
The setup makes it, and its administrator's account: in Sonda, that person signs in with the username and
the password given here.
Organization — the company's name, or the team's — empty leaves it to be made from Sonda's first start
  : Example Corp
First division — an organization is divisions, each with its own people; the others are made in Sonda
  [General]: Development
Administrator's username — lowercase letters, digits, dots, dashes — 3 to 32; it is never changed
  : admin
Administrator's name — as the team reads it
  [admin]: Alex Rivera
Administrator's email — where Sonda reaches the administrator
  : ops@example.com
Administrator's password — at least 12 characters, taken as typed — the one typed in Sonda to sign in
  :
The password again
  :

3  Where the server is reached
Port — the port the server listens on
  [50704]:
Address — the address of this server to listen on — empty is every one it has
  :
Networks — the networks that may reach the server, as 10.0.0.0/8 or one address, a space between — empty is any
  :

4  The certificate a Sonda is shown — a Sonda reaches the server over https, always
  1  One the server makes: its fingerprint is compared once, in Sonda, and pinned there
  2  A certificate of the team's own, one the computers accept already (PEM files on this server)
  3  None here: a proxy of the team's speaks https in front of the server
  [1]:

Written: /home/ops/sonda-server.json
Made: the organization "Example Corp", with admin as its administrator.
      /home/ops/sonda-server.recovery keeps the administrator's recovery key: sonda-server -reset-admin sets the password again.

5  Start the server
  As a service, which takes root: sudo asks for this account's password.
Start Sonda Server now, and each time this server starts? [y]:
Installed: Sonda Server starts with this server, and is running now as ops.
  Its log        journalctl -u sonda-server
  Stop it        systemctl stop sonda-server
  Take it out    /home/ops/sonda-server -service remove

────────────────────────────────────────────────────────────────────────
What is left to do
────────────────────────────────────────────────────────────────────────
  Running: Sonda Server is started, and starts with this server each time it does.

  1  Open the port. A Sonda reaches this server on TCP port 50704: it is to be open in this server's firewall,
     and in the hosting provider's where there is one.

       ufw          sudo ufw allow 50704/tcp
       firewalld    sudo firewall-cmd --permanent --add-port=50704/tcp && sudo firewall-cmd --reload

  2  In Sonda: New account, then Enterprises and regulated organizations.
  3  Paste this one line into the Address field or the Token field — either takes it — and press Test the store.
     It fills the address, the token and the fingerprint by itself: it is the one thing copied from here.

       SNS1.eyJh••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••IifQ

  4  Sign in as admin, with the password typed in this setup.

What each one is, and where it goes
    One line     The three below as one, for the Address field or the Token field: with it, none of the three
                 is typed. It carries the token: it is kept as the token is.
    Address      https://203.0.113.10:50704
                 or https://[2001:db8::7c8]:50704
                 Where a Sonda reaches this server: the Address field. A name the team's DNS has for this server works as well.
    Token        Kx3m•••••••••••••••••••••••••••••••••••Vq2P
                 What lets a Sonda speak to this server at all: the Token field, where the line is not used.
                 It is no password and signs nobody in: a person signs in after it, with a username and a
                 password this server checks.
                 Said now and not again: the server keeps its hash alone. Keep it where the company's secrets
                 are kept; sonda-server -token makes a new one.
    Fingerprint  SHA256:7c1e4a••••••••••••••••••••••••••••••••••••••••••••••••••••••d09b2a
                 What tells this server from another at its address. Typed nowhere: the line carries it, and
                 without the line Sonda shows it at the first Test: the same one, and it is trusted once.
    Sign in      admin, with the password given here: the username and the password of the page after the test.
ops@store-1:~$ 
/ WHILE EVERY COMPUTER IS CLOSED

It runs the team's schedules, too.

A desktop that is closed watches nothing. The server is on, inside your network, and already holds the store, so the schedules run there.

A key of its own

A key pair made at setup, its fingerprint printed at every start. The owner compares it and pairs the server; from then on every Sonda seals the projects it runs for that key alone, and believes the runs it signs.

On a cadence

A request, a folder or a whole project, every minute to weekly, each request with its scripts and its checks. Every run is signed by the server's key and sealed under the project's.

Alerts and the summary

Mail through the organization's own mail server, handed to the server sealed for its key. A webhook, set by administrators. A daily or weekly digest for each workspace.

/ LOCKFLARE SONDA

Sonda Server, in the free edition, up to 10 seats.

Sonda Server, listed →