Back to profile

2025 — 2026

OverSSH — server orchestration

Hosts, scripts and flows grouped into projects. SSH orchestration, log monitoring, agent analysis of changes and proactive security.

Creator and developer

The challenge

Manual server procedures drifted, while health checks required inspecting each machine.

What I built

  • Designed hosts, scripts, flows and projects: flows combine scripts; projects group hosts, scripts and flows.
  • Automated installation, updates, deployment and checks over SSH.
  • Connected updates to GitHub/GitLab and added SSH collection of logs and system events.
  • Implemented agent analysis of logs and package changes, including repository checks and recommendations.
  • Implemented proactive security monitoring for suspicious changes.

Results

  • Deployment, updates and health checks follow repeatable workflows.
  • The tool is used in everyday server operations.
System architecture. Scripts and flows combine with hosts in projects and run over SSH. Logs, package changes and repository context feed the proactive agent security workflow.Open full-size diagram ↗
Components & connections

Overssh Workflow

  • Script catalogReusable scripts for installation, updates, deployment and diagnostics.
  • Flows · WorkflowsMulti-step sequences of scripts with conditions and checks.
  • Git delivery hooksGitHub/GitLab events initiate controlled project updates.

Projects and hosts

  • HostsManaged hosts included in projects.
  • ServicesApplication and infrastructure service types with their own operating rules.
  • ProjectsGroup hosts, individual scripts and flows with application services and execution rules.

Overssh Execution

  • SSH executorRuns project flows or individual scripts on selected hosts over SSH.
  • Service runtimeApplication processes and containers on managed hosts.

Overssh Verification

  • Health checksService availability and basic status.
  • Monitoring · Logs and eventsSSH collection of logs, package/container changes, sign-ins and system events.
  • AI analysis · SecurityAnalysis of logs and repository context for suspicious changes and potential injections.
  • Package · repositoriesPackage source context when updates or suspicious changes are detected.
  • Signals · RecommendationsAgent findings and recommendations for the operator.
  1. Script catalog→Flows · Workflowscomposes
  2. SSH executor→Service runtimeinstall / update / deploy
  3. Service runtime→Health checksquick status
  4. Service runtime→Monitoring · Logs and eventsevents and state
  5. Monitoring · Logs and events→AI analysis · Securityanalysis payload
  6. Hosts→Projectsproject hosts
  7. Services→Projectsproject services
  8. Flows · Workflows→Projectsproject flows
  9. Script catalog→Projectsindividual scripts
  10. Git delivery hooks→Projectsstart update
  11. Projects→SSH executorexecution plan
  12. Monitoring · Logs and events→Package · repositoriespackage changes
  13. Package · repositories→AI analysis · Securitycode context
  14. AI analysis · Security→Signals · Recommendationsfindings

Engineering takeaway

Context

An independent tool for maintaining servers and application services.

  • Different services require their own update and verification procedures.
  • Automation must preserve control over changes.

Approach

Turned recurring operations into explicit workflows that can be applied across different servers.

  • SSH as a common way to operate existing infrastructure.
  • Explicit composition of hosts, individual scripts and multi-step flows into projects.
  • Fast health checks separated from detailed log analysis.
  • Analyze package changes with repository context; keep recommendations separate from execution.

Lessons

  • Explicit operating procedures make automation understandable and maintainable.

Stack

  • Linux
  • SSH
  • Shell scripts
  • Docker
  • GitHub / GitLab hooks
  • CI/CD workflows
  • Health checks
  • Operational logs

Skills

Products, systems and ideas brought to life in working software.