Administration, Security & Operations

SamvraCore ships as a single self-contained binary, and its release process reflects that. Distribution runs through a dedicated download server, samvracore-downloads at downloads.samvracore.tech. Releases follow a three-stage flow: deploy/upload-release.sh, then deploy/upload-pointer.sh, then deploy/promote-release.sh. A URL rewrite at ingest means the build pipeline does not need to know the canonical host, and rollback is simply re-promoting the previous version. The reference production host samvracore.tech runs on a Linux VPS under systemd with Restart=always, deployed by an SCP-plus-symlink-swap method. Local build archives are cleaned with a recoverability guard, and releases are published on GitHub.

Security posture

Security is layered throughout. Passwords are hashed with bcrypt at cost 10, and sensitive fields use AES-GCM encryption from pkg/encryption/; the portal-credential vault adds per-organisation key derivation. Authentication uses short-lived JWT access tokens with rotating refresh tokens, and RBAC middleware invalidates its cache when a role or permission changes. Audit logging covers every state-changing endpoint, and Row-Level Security acts as defence-in-depth alongside application-layer tenant filtering. The embedded HTTP server supports TLS, and pkg/middleware/ provides CSRF protection, rate limiting and IP-allowlist controls. The install wizard is hardened with an .installed marker and an atomic config write, closing the gap between installation and a secured running service.