Sync the self-hosting stack (215bfeb)

This commit is contained in:
2026-08-19 08:58:25 +02:00
parent 7eee594c40
commit 38ec167acd
+12 -5
View File
@@ -145,8 +145,9 @@ administrator account and then needs a key.
**An unlicensed instance contacts nobody.** No check-in, no telemetry, nothing leaves your network at
all. The reporting below starts only once a key is in place.
A licensed instance then reports to the address written into that key, by default once a day. This is
everything it sends, in full:
A licensed instance then reports to the address written into that key, at an interval your provider
sets — every ten minutes on the current arrangement, so that a renewal or a revocation reaches you
promptly rather than tomorrow. This is everything it sends, in full:
| Field | What it is |
| ----------------------- | ------------------------------------------------- |
@@ -156,12 +157,18 @@ everything it sends, in full:
| Version | Which Jarvis build you are running |
| Contract version | Which set of limits this build understands — a checksum, not a document |
| Counts | How many organizations, users, agents and assets |
| Public URL | Your instance's address — **optional, see below** |
| Public URL | Your instance's address — always sent, see below |
| Timestamps | When the process started, and when it reported |
**Counts, not contents.** No names, no email addresses, no conversation text, no asset inventory, no
credentials, nothing about what you administer. The only field that identifies your network rather
than measuring something is the public URL, and it can be switched off.
credentials, nothing about what you administer.
**The public URL is the one field that names your network rather than measuring something, and on a
licensed instance it is sent.** It used to be a switch on the licence screen; it is not any more,
because an installation the publisher can identify only by a fingerprint is one where "which of these
is the customer calling about" has no answer. The screen now shows you the exact address that leaves,
under Settings → Licence. If that is not acceptable for your deployment, the answer is to run
unlicensed — which contacts nobody at all — or to take it up with your provider before installing.
The reply can carry a renewed key, which your instance adopts on its own — so a renewal reaches you
without anybody re-pasting anything.