On-prem delivery model

Run TjMakeBot inside customer-owned infrastructure with offline license control

This path is for customers who cannot rely on the public SaaS site and instead need on-site rollout, deployment-boundary control, and renewable offline licenses.

What this path now means

Customer buys and controls the server and network environment
Our engineers deliver the platform on site or into the customer network boundary
The platform uses a signed offline license to decide whether it remains usable
Renewal happens by issuing and importing a new license instead of continuing on public SaaS infrastructure

Current deployment fingerprint

Read the fingerprint from the environment where tj.serv.account.license is currently running, then feed it into issuance and activation.

Current fingerprint is not available yet.

On-site delivery flow

This page now covers the actual delivery engineer loop instead of only a marketing explanation.

Step 1: collect the current machine fingerprint from the running deployment environment.
Step 2: issue a customer license with that fingerprint, expiry, grace period, and feature flags.
Step 3: load the issued license into the verifier, then activate it as the current local license.
Step 4: refresh current status and archive the issued license file with the deployment handoff package.

Deployment handoff package

Download a single JSON package that captures the current fingerprint, selected license, current activation state, and the delivery checklist.

Fingerprint
-
License code
-
Current status
-
Checklist items
4

Printable delivery report

Export a printable HTML report for implementation, support, or archive use.

Fingerprint
-
License code
-
Preflight
-
Notes
-

Deployment preflight

Run a single preflight to verify that the selected license, imported handoff context, machine fingerprint, and current activation state are still aligned.

No preflight has been run yet.

Internal issuance console

Use a logged-in team account to issue a customer license and review recent issued licenses.

This panel requires a logged-in account with Access-Token and Team-Id.

Offline license verifier

Paste a signed license JSON to verify status or activate it as the current deployment license.

Current deployment status

Read the license already activated in the local deployment environment.

No current license is activated in this environment yet.
Private deployment

Need commercial scoping or deployment planning?

Use the enterprise path to align procurement, delivery window, security review, and the first license issuance.

Talk to enterpriseReview security