Free evaluation
Use public documentation, local validation output, and repository artifacts first. Questions sent to request@tnsds.tech receive best-effort email review; no response time, fix, compatibility result, or service level is promised.
Support boundaries
Support starts with local evidence.
Day Shift support is organized around repository-visible artifacts, local validation output, release-line license status, and requests sent to request@tnsds.tech.
Paid self-serve plans
Solo Commercial, Small Team, and Company customers can email request@tnsds.tech for installation, licensing, and reproducible defects in their covered release line. This channel does not promise a response time, fix, or compatibility outcome.
Enterprise agreements
Enterprise support scope, channels, response terms, and any service commitments exist only when stated in a written agreement. Public website copy does not add commitments to that agreement.
Automation hosts
Automation hosts can use stable customer-managed labels for diagnostics, but host credentials and private support identity records stay out of static assets.
Authenticated support boundary
Authenticated customer operations belong on server-capable routes; request@tnsds.tech is the public support intake.
Brand assets
Share Day Shift with support context.
Use the square social card when a support request, internal note, or launch handoff needs a compact Day Shift visual.
Download social card