01 / What it solves

Back to top

Most internal control does not need a standing remote-admin surface.

A temporary SSH allowance, a maintenance switch, or a one-shot daemon instruction is a small operation. Delivering every one through an always-open gateway, web control panel, or general shell can create more surface than the action needs.

Siglatch's answer

A very small encrypted UDP daemon for narrow internal control.

It listens for a bounded signal, checks the configured policy, and hands the request to the selected handler. It is not a VPN or a general remote shell.

02 / Use cases

Back to top

Use a small signal for a small operational job.

Siglatch fits work that can be named, bounded, and dispatched without opening a general-purpose administration channel.

01 Access

Dynamic IP or short maintenance window

Open SSH only when an operator needs it.

Accept a protected signal, allow the current source, then revoke or expire the path when the work is done.

Product fit
Temporary reachability without a permanently broad ingress rule.
Required boundary
Firewall behavior, key custody, expiry, and host policy remain operator-owned.
Read the access example
02 Maintenance

Admin panel or internal UI

Expose an internal control surface for a bounded window.

Toggle reachability around a named maintenance task instead of leaving the interface continuously reachable.

Product fit
Short-lived access to a known internal surface.
Required boundary
The surrounding application still owns authentication, authorization, and safe session behavior.
Read the maintenance example
03 Automation

One remote daemon action

Send reload, rotate, notify, or reboot as a named signal.

Route an accepted action identifier to a reviewed handler without introducing a web stack or interactive shell.

Product fit
Small operational actions with an explicit handler and failure boundary.
Required boundary
Handler parsing, privileges, idempotence, logging, and recovery remain local responsibilities.
Read the daemon examples
04 Signaling

Small job, log, or inter-server signal

Move a narrow operational signal between machines.

Trigger a job, forward a small telemetry or log signal, or call a custom static or dynamic handler through the UDP path.

Product fit
Bounded machine-to-machine control that does not need a general message platform.
Required boundary
Packet limits, delivery semantics, handler policy, and surrounding observability must match the use case.
Read the signaling examples