Security by Design

Zero-Trust Infrastructure
Security & Compliance

Security is not an add-on feature at OpsVera — it is the bedrock of our entire telemetry, agent, and database architecture.

Outbound-Only mTLS Architecture

The ops-agent creates an encrypted connection strictly outward to agent.opsvera.dev:443. It does not open listening network ports, preventing port scanner discovery, remote code execution bugs, or unsolicited inbound connections.

PostgreSQL Row-Level Security (RLS)

Multi-tenant boundaries are strictly enforced inside the database engine using FORCE ROW LEVEL SECURITY on all tenant tables. Cross-tenant access is structurally impossible even in the event of an application logic anomaly.

Cryptographic Agent Signing & Auto-Updates

Every Go binary build is cryptographically signed using Cosign and verified via public root keys before automatic in-place updates. Checksums are validated to prevent tampering and supply chain poisoning.

CrowdSec Collaborative Defense

Integrates with local CrowdSec security bouncers on edge servers. Aggregates brute force attacks and malicious IP lists across the entire cluster to proactively harden your perimeter.

Compliance & Data Protection Standards

GDPR & CCPA
Zero personal identifiable information (PII) collected in server telemetry. Full data subject rights supported.
SOC 2 Alignment
Continuous audit logging, role-based access control (RBAC), and automated vulnerability testing.
TLS 1.3 / AES-256
All data in transit is encrypted via TLS 1.3 with Perfect Forward Secrecy. Data at rest is encrypted via AES-256.
Audit Trail
Immutable audit logs record all user logins, settings modifications, and runbook triggers.
Technical Documentation

OpsVera Agent Installation & Quickstart Guide

Deploy the ultra-lightweight ops-agent binary to any Linux server in under 60 seconds.

1

One-Liner Automated Installation

Run the following command on your target Linux machine as root or with sudo. The installer will automatically detect your OS distribution, architecture (x86_64 / aarch64), download the signed binary, configure systemd, and establish an outbound mTLS handshake.

curl -fsSL https://agent.opsvera.dev/install.sh | sudo bash -s -- --token=YOUR_WORKSPACE_TOKEN
2

Verify Agent Health & mTLS Handshake

Once installed, verify the service status with systemctl and run the diagnostic check:

// Check systemd daemon status
systemctl status opsvera-agent
// Run self-test and mTLS diagnostics
opsvera-agent --test-connection
3

System Requirements & Firewall Policy

Supported OS
  • Ubuntu 20.04, 22.04, 24.04 LTS
  • Debian 11 (Bullseye), 12 (Bookworm)
  • RHEL / AlmaLinux / Rocky Linux 8 & 9
  • Alpine Linux 3.16+
Minimal Footprint
  • RAM: < 15 MB resident memory
  • CPU: < 0.1% baseline overhead
  • Binary size: ~8.5 MB static Go ELF
  • Zero external shared libraries
Firewall & Ports
  • Inbound: 0 ports needed (None)
  • Outbound: TCP Port 443 (HTTPS)
  • Encrypted with TLS 1.3 + Client Cert
  • Safe through restrictive NAT/VPC
4

Backup Watchdog & Custom Health Hooks

OpsVera automatically detects active Borg and Restic repositories. To integrate custom cron backup scripts or trigger instant health pulses:

# Example: Sending a backup completion heartbeat from your cron script
/usr/local/bin/opsvera-agent backup-notify \
  --repo="borg://backup.corp.internal/var/backups" \
  --status=success \
  --bytes=42949672960 \
  --duration=312s
                    
Ready for Modern Operations?

Supercharge Your Infrastructure Operations Today

Join forward-thinking MSPs, cloud agencies, and DevOps teams who manage thousands of mission-critical Linux nodes effortlessly with OpsVera.