Security and deployment
The system is designed for local-network operation. For IT teams, the most important points are attack-surface minimisation, access control together with clear logs and readable history.
LAN-first
The system can run in a closed network without internet exposure.
Segmentation
Targeting groups and subnets reduces unnecessary noise and the risk of mistakes.
History / audit
You can quickly see what was sent, when, to whom and with what status or receipt.
Recommended deployment model
Most often: server + web panel in LAN (VM or physical), with clients on user workstations.
Starting checklist
• Gdzie stoi serwer (VM/fizycznie)?
• Should the web panel be accessible only from the admin network?
• How should recipients be segmented (subnets/groups)?
• Which notifications should require read receipts?
• How long should history be retained?
Most common IT questions
| Question | Answer (short) |
|---|---|
| Is internet access required? | No. The typical scenario is LAN-only operation. |
| Can the web panel be limited to the admin network? | Yes – recommended. |
| How are read receipts controlled? | Statuses and receipts are visible in the web panel. |
| How fast can it be deployed? | Most often: server setup + clients + notification delivery tests. |