Skip to content

License management

Day Shift licenses are signed JSON files verified locally. Normal CLI use does not require online activation after installation.

Evaluation use does not grant commercial rights. A commercial license grants the users and commercial use named by its plan for one covered release line, including that line’s patch releases.

For example, a Solo Commercial license for Day Shift 0.1.x covers 0.1.0 and later 0.1.x patch releases. You may keep using that covered 0.1.x line perpetually. Day Shift 0.2.x is a newer release line and is not covered by the 0.1.x license: remain on 0.1.x or optionally verify the prior license to purchase 0.2.x coverage at the stated upgrade price. A valid covered license suppresses commercial reminders for 0.1.x; evaluation use or an uncovered 0.2.x install continues to show them.

Your repository artifacts remain yours if you do not upgrade. The license does not lock, remove, or transfer ownership of task definitions, implementation summaries, reconciliations, or other repository files. Paid self-service plans include email help for purchase and license-delivery issues; broader support is optional or separately agreed.

Use the signed file delivered through the website-owned purchase or recovery flow:

Terminal window
day-shift license install <license-file>

The command installs the file into user-local license storage. Do not commit license files, reminder state, or state-directory overrides as repository configuration.

Terminal window
day-shift license status --format json

The JSON report identifies the resolved license path, verification state, and reminder-policy diagnostics. For a one-off inspection, use --license-file <path> rather than changing configuration.

After a suppressing license verifies successfully, preview cleanup of Day Shift-managed reminder regions:

Terminal window
day-shift license cleanup-reminders --dry-run

Review the proposed artifact edits, then rerun without --dry-run when they are correct.

Purchases, current plan terms, entitlement scope, signed-file delivery, and recovery remain on tnsds.tech. If local verification fails, continue with Troubleshooting.