DevOps case study · 01Linux / Identity / Automation

Secure Access
Orchestrator.

Access Panel / SSH & OpenVPN

From a control-panel action to real Linux access. One system for access rules, dynamic SSH keys, user accounts and VPN profiles, with tested failure behavior.

FastAPIReactPostgreSQLDockerOpenSSHOpenVPN
CONTROL PLANE / ACCESS MODEL

Gateway

Access Panel · API · PostgreSQL

Rules, keys, audit
HTTPS / SCOPED MACHINE TOKEN

Target agent

sshd · heartbeat
account provisioning

VPN CA

OpenVPN profiles
issue / revoke

The Gateway can also host a target agent. Independent emergency access is configured separately.

01

Access as a rule

A person, a key, a server and an expiry. Grant and revoke access from one control plane.

02

Gateway ≠ VM number

Deploy independently of a hypervisor. Running a target agent on the gateway is optional.

03

SSH + VPN

Dynamic SSH keys and a separate CA for issuing and revoking OpenVPN profiles.

Tested on a real VM

1 vCPU256 MB RAMDebian / KVM
  • Linux account provisioning from active access rules
  • SSH login without a local authorized_keys file
  • Access revocation after cache TTL expires
  • Dynamic login denied when authority and fresh cache are unavailable
  • Independent emergency login during an outage

Local verification, Oct 29, 2026: 486 backend tests and 33 frontend tests. Verification results, not an SLA.

One command for the Gateway

gateway / terminal
./sao up
./sao status
./sao down

Secrets, migrations, initial Gateway and HTTPS. Install the agent separately on the Linux host you choose. A real VPN endpoint requires additional network configuration.

© 2026 Vladislav Borodatyi. All rights reserved. Code use requires the author's written permission.