Tailscale-Native GitHub Actions Runner Fleets
Short answer: Strict is built for Tailscale from the ground up: Standalone mode authenticates Tailscale-User-Login headers via tailscale serve with zero accounts, shares NVMe build caches across peers, and monitors Tailscale node key expiry in strict doctor.
Run Strict's control plane behind tailscale serve with identity headers, peer build caching, and node key expiry alerts.
Drop-in workflow YAML & zero-sudo enrollment
Enroll your host with strict add-runner and route jobs directly via GitHub's native runs-on labels:
jobs:
deploy-staging:
runs-on: [self-hosted, Linux, X64]
steps:
- uses: actions/checkout@v4
- run: curl -fsS https://staging.tailnet.ts.net/health
curl -fsSL https://strict.ai/install.sh | sh
curl -fsSL https://strict.ai/install.sh | sh && strict server install
How Strict keeps Tailscale Fleets runners healthy
| Subsystem | How it applies to Tailscale Fleets |
|---|---|
| Disk Cleanup | Each tailnet host independently runs maintenance Tiers 1–5 with lock safety and updates its 300s-cached storageBreakdown. |
| Preflight Doctor | tailscale-health checks daemon connectivity and warns when node keys are expired or expiring within 14 days so tailnet runners never drop silently. |
| Tracked Toolchains | All 12 tracked toolchains plus Tailscale companion node status linking |
| Cache & Balancing | Standalone servers expose Tailnet Build Cache directly over your tailnet, while companion *-rex / *-strict Tailscale device matching links nodes automatically. |
When Strict fits vs. when hosted runners win
Use Strict for Tailscale Fleets when
- Zero open firewall ports and zero accounts behind tailscale serve
- Runners reach private staging databases, registries, and internal APIs natively
- Proactive 14-day Tailscale key expiry warnings inside strict doctor and email alerts
Use cloud-hosted runners when
- Teams prohibited from running WireGuard/Tailscale on build infrastructure
- Public open-source CI requiring ephemeral third-party isolation
Frequently asked questions
Does Strict require opening inbound ports to GitHub?
No. Both actions/runner and Strict's Python host agent use outbound HTTPS connections, while your console sits behind tailscale serve.
What happens if a Tailscale node key is close to expiring?
strict doctor's tailscale-health check and Strict's alert evaluator flag expired keys or keys expiring within 14 days before a machine silently disappears.
Can I add optional Cloud Monitoring later without re-enrolling runners?
Yes. Standalone and Cloud Monitoring share the exact same str_v1_<workspaceId>_<64-hex> token protocol and REST endpoints.
Try Strict on one spare Mac in under two minutes
Signed Apple Silicon app or single-line CLI · Zero accounts required