Reference
When Soviez Connects Online
Explicit online lifecycle operations
When Soviez connects online
Rule
Each connection to Soviez services is started by an operation you run (or approve). Before sensitive steps, the product discloses what is about to happen.
Operations that may need connectivity
| Operation | Why connectivity is needed |
|---|---|
| Device authorization | Link this server to your Soviez account |
New Production (--new) | Verify license, select approved release, authorize download |
| Product update | Verify update entitlement and download the approved release |
| New Stage operations | Verify Stage entitlement |
Operations that do not depend on continuous connectivity
| Operation | Notes |
|---|---|
| Running ERP | Continues if Soviez is unreachable |
| Local backup / restore | Available on the host |
| Status / diagnostics | Local inspection |
Authorizing a server
When you authorize a device:
- Your account is linked to that server for future authenticated requests
- No business data is sent
- Authorization alone does not consume a Production license slot
- Authorization alone does not activate ERP
- You can revoke the device later; revocation blocks future connected operations, not a running ERP
Image download (install / update)
| What happens | Detail |
|---|---|
| You start it | Not a silent background sync |
| Exact release | Approved digest — not a mutable latest tag |
| Temporary access | Short-lived pull-only credentials |
| No permanent Hub login | Not stored as a day-to-day host credential |
| If Soviez is down | Running ERP is unaffected; a new pull you requested may wait until service returns |
New Production (--new)
Typical connected steps include device authorization (if needed), license verification, approved release selection, image download, environment creation, domain/HTTPS setup, and activation.
Activation secrets are stored with restricted permissions and are not written to logs or command arguments.
If the network drops mid-install, resume with the documented reattach flow for that operation when service returns.
Never sent
Accounting data, customer lists, attachments, database dumps, filestore files, passwords, activation secrets in logs, device private keys, or permanent organization registry tokens.
Source: canonical operator documentation · Permalink