🔐 AMXELA Security Overview

AMXELA is designed with a security-first mindset, ensuring your data, credentials, and infrastructure remain under your full control.

🛡️ Security Principles

Local-Only SSH Connections
All remote commands run directly on your device — no external servers or middlemen are involved.
Keychain Credential Storage
SSH passwords and private keys are securely stored using Apple’s Keychain. They are never saved in plaintext or uploaded to the cloud.
iCloud Sync (Optional)
Server configurations (not credentials) are synced privately through your Apple ID using Apple’s CloudKit.
No Telemetry or Tracking
AMXELA does not include any analytics, crash reporters, or tracking libraries.
No Root Required
All monitoring features work with standard or restricted SSH users — no elevated access is necessary.

To ensure secure usage of AMXELA, we recommend:

✅ Creating a dedicated SSH user for monitoring
✅ Optionally disabling shell access for restricted users
✅ Granting access only to /proc and limited system commands (uptime, df, cat, etc.)
❌ Avoid using root or sudo-enabled users unless absolutely required

To monitor Docker containers without using sudo, your SSH user must be part of the docker group on the remote server.

Use the following command:

sudo usermod -aG docker your-user

After running this command, log out and log back in (or restart your SSH session) to apply the group change.

AMXELA uses the following open-source libraries:

See the Licenses page for full license text and attribution.

AMXELA runs 100% locally. We do not operate any proxy, backend, cloud service, or telemetry engine.

All connections occur between your device and your own servers — directly.

Have security concerns or wish to report a vulnerability?

Reach us at:
📧 suport@amxela.com