· Gamertan Tend · operations
Tend makes small Go deployments boring.
A small Go service should not need a platform team. It should still get a reproducible artifact, a healthy candidate, a deliberate traffic switch, and a known way home. I built Tend because I was tired of carefully reconstructing that same path by hand.
The problem was not a missing shell command
I already knew how to build a binary, copy it to a server, restart a service, and edit Caddy. The risk lived between those commands: Was the commit clean and pushed? Did the second build produce the same bytes? Is this the digest I approved? Did the candidate start with production boundaries? What changed traffic? What happens if the smoke test fails after activation?
Tend turns those questions into one strict, versioned contract for small Go services on Linux, systemd, and Caddy. It packages a clean pushed commit twice, records checksums and Go provenance, writes an SPDX SBOM, requires explicit digest approval, tests an isolated candidate, validates the Caddy change, records rollback state, and restores the previous service when activation fails.
“She’s my antique.”
My wife has endured the 4 a.m. migrations, the Magento 1.9-to-2-and-beyond upheavals, emergency deployments, fixes, updates, and blue-green switches beside me. She has tenderly brushed the grey in my beard and rubbed the bald spot that years of server work helped earn. She has also been the person beside me when stress and fatigue from that work quite literally put me in hospital.
“She’s my antique” was in my vows—an inside joke we had already made part of our life together. It never meant obsolete. It meant valuable, storied, and irreplaceable. The image in my mind is a beautiful old Dutch wooden piece: preserve the finish, the history, the cracks, and the scratches. Do not sand away the story, and do not add dozens more through careless handling.
Tend is not simply an homage to my experience. It is a love letter to her. A calm deployment cannot return the nights already spent or erase the marks we have earned, but it can help me protect our next night, our health, and our time together. Reproducibility, health gates, and rollback are technical mechanisms; the actual thing they preserve is human.
Where it fits beside other tools
- CI proves the artifact. Tend carries that reviewed artifact through a constrained single-host release transition. It does not replace CI.
- Shell scripts remain more flexible. Tend deliberately trades that flexibility for validated paths, explicit state, no shell interpolation, and the same failure behavior on every run.
- Ansible and Terraform describe systems and infrastructure. They can prepare a Tend host or invoke Tend; Tend focuses on the application release boundary.
- Platforms and Kubernetes solve larger scheduling and orchestration problems. Tend is for the calm middle ground where one well-understood server is enough.
The preview intentionally does not manage databases, migrations, containers, Kubernetes, arbitrary hooks, artifact transport, or EQL Helper's application-specific catalog activation. Narrow scope is part of the safety model, not an unfinished platform pitch.
Why my opinions matter for shit in a cow pasture
They do not, by themselves. Experience suggests which questions are worth asking; evidence earns confidence in an answer.
I have spent years building and operating small services, recovering from my own mistakes, and learning which "simple" deployment steps become dangerous when they depend on memory or timing. That history informed Tend's opinions. Then I made the tool prove them: deterministic packaging, failure-injection tests, candidate checks, rollback and reactivation campaigns, and real maintenance releases across two differently shaped services.
The public dogfood record includes the exact source, artifacts, checks, boundaries, and failures observed. You can use Tend, borrow an idea, disagree with every opinion, or walk away. The evidence is there so none of those choices require faith in me.
This page took the same path
The Gamertan release containing this note was packaged, approved by exact SHA-256 digest, exercised as the inactive candidate, and activated with Tend Preview 2. The footer is not a decorative badge; it describes the release path that served the page.
Sandwich Hime uses Tend's singleton-candidate strategy. Gamertan uses its blue-green strategy. EQL Helper does not claim the Tend colophon because its database and catalog activation remain application-specific and outside the current contract.