Skip to content

Portfolio

Prior technical project experience

Three technical environments built and managed before IronRelay Systems. Each entry describes the environment, what was built and why, what actually runs there, and the stack it runs on — the same kind of detail an audit of your own setup would produce.

Prior technical project experience · 2026

The projects

Three environments, described the way we would describe yours.

  1. 01Prior technical project experience · 2026

    Production Automation Server with Off-Site Backups

    • Ubuntu
    • Docker
    • n8n
    • Caddy
    • Tailscale

    Environment

    A single Linux host carrying automation work that had to keep running unattended, where the data on that host had to survive losing the host itself, and where the automation interface should not be reachable from the public internet.

    What was built, and why

    An Ubuntu server with Docker as the runtime boundary. n8n runs in a container and holds the scheduled workflows; Caddy runs in front of it as the reverse proxy, handling TLS and certificate renewal so the service is not published directly from the container. Backup jobs run on a schedule and write off-site rather than to the same disk. Administrative access goes over a Tailscale network, so the automation interface is reached inside a private network instead of through an exposed port.

    What runs there

    • Ubuntu host with Docker and Compose managing the container lifecycle
    • n8n container running the scheduled automation workflows
    • Caddy reverse proxy providing TLS termination for the service
    • Scheduled backup jobs writing to off-site storage
    • Tailscale private network used for administrative access
  2. 02Prior technical project experience · 2026

    Secure Production API Deployment

    • Ubuntu
    • Go
    • systemd
    • Caddy
    • SSH tunneling
    • MySQL

    Environment

    A Go API that needed to run as a real production service — started on boot, restarted when it fails, reachable over HTTPS — with its MySQL database kept off the public internet entirely.

    What was built, and why

    The API is built from Go source and deployed to an Ubuntu host, where systemd runs it as a managed service: start on boot, restart on failure, logs into the system journal. Caddy sits in front as the reverse proxy and handles TLS termination and certificate renewal, so the API process itself never deals with certificates. MySQL is reached over an SSH tunnel, which keeps database access and administration off the public network.

    What runs there

    • Go API service under systemd with managed lifecycle and journald logging
    • Caddy reverse proxy terminating TLS for the public API endpoint
    • MySQL instance not exposed to the public internet
    • SSH tunnel used for database access and administration
  3. 03Prior technical project experience · 2026

    Multi-Service Server Management Environment

    • Windows Server
    • Docker
    • PostgreSQL
    • ClickHouse
    • Valkey
    • networking

    Environment

    One managed host carrying several different data services side by side — relational storage, an analytics database, and a cache layer — where those services should not be able to reach each other or the host by accident.

    What was built, and why

    Docker runs each data service in its own container with its own storage and its own published ports, so the services do not share an installation or a process. Networking is configured deliberately rather than left flat: services are placed on defined networks and only the ports that need to be reachable are published, keeping the data services separated from one another and from the host. The host itself — Windows Server — is managed as a system, with the container runtime, storage and network configuration maintained alongside the services it carries.

    What runs there

    • Windows Server host running Docker as the container runtime
    • PostgreSQL container for relational data
    • ClickHouse container for analytical queries
    • Valkey container for caching
    • Defined container networks and published ports separating the services

Prior technical project experience · 2026

These are prior technical projects, not paid IronRelay Systems client engagements. No client, industry, duration, metric or business outcome is claimed or implied.