Skip to main content
kombify Guard is Techstack’s server-side reliability and security component. It connects an enrolled server to its owner, supervises authorized operations and reports what happened. Its value is the connection between configuration, execution and evidence: you can distinguish a reachable server from a protected application and a backup job from a demonstrated recovery.
These pages explain Guard’s architecture and the meaning of its evidence. Techstack is pre-1.0; connected and managed operation remain preview scope. Available operations depend on the installed release and server profile. See availability and the release-bound API and CLI reference.

What changes for the owner

For example, a photo service can have a healthy web container while its database is unavailable. Its host can also meet a security baseline while that service exposes an unintended endpoint. Guard’s protection model keeps these facts separate so an apparently healthy server does not hide an application problem.

One operating model across home and cloud

A homelab can span home hardware and rented servers. Techstack coordinates those servers; each Guard is bound to one server. The design keeps the same identity, authorization and evidence boundaries across placements. Self-managed Techstack can control its Guards without a hosted kombify account. Connecting an installation to hosted services does not implicitly transfer its local owner’s authority. Guard is part of Techstack, with no separate product or security tier. Standalone StackKits remains independent of Guard and Techstack. See operating modes.

The responsibilities fit together

An AI assistant can explain a finding or propose an operation. It uses the same authorization and execution boundaries; an explanation is not permission to change the server.

What the trust mark means

Guard is built around verifiable conditions, not the presence of a running agent. Enrollment, an authenticated command round trip, durable operations, secured configuration, update posture, tested recovery and governed reach each need their own evidence. Unknown or stale evidence cannot establish protection. An aggregate indicator alone is insufficient to qualify an entire deployment. Guard does not establish that a server is immune to compromise, that every application is managed, or that no data can be lost. Its useful promise is observable protection and controlled recovery within a declared scope.

Architecture and operation truth

How identity, durable results and execution boundaries handle failures.

Protection and recovery evidence

Understand host and application coverage, repairs and recovery claims.