OFFLINE EDGE DEPLOYMENT
Process locally.
Keep licence checks online.
Video runs on your server. Internet is required for startup and licence renewals.
Overview & setup notes
Process warehouse camera footage on your own edge server. A perpetual camera entitlement is paid once. Online startup and automatic runtime licence checks are required, with up to ten minutes of grace during a connection outage.
What runs locally?
The Docker runtime, forklift model, camera-stream processing and local detection API run on your server. The licensed edge runtime does not require your own connection to the website's cloud database. Camera credentials, the private server identity and local recordings remain on your infrastructure.
The online trial is a separate evaluation service: footage you upload for that trial is processed online. Local edge operation and online trial uploads are different workflows.
What still needs a connection?
Website registration, invoice requests and obtaining an activation code use the online portal. Normal commercial activation exchanges a signed request with the portal over HTTPS. The production entitlement token has no expiry. Runtime operation additionally requires an exclusive signed lease, renewed every minute. Inference stops when the remaining lease grace expires. Restarting requires connectivity and may require waiting up to ten minutes for an outstanding reservation to expire.
The customer runtime requires HTTPS access to the portal at startup and for periodic renewal; a permanently air-gapped deployment is not supported. An administrator must coordinate the signed request and returned licence within the activation-code window. A completely automated air-gapped commercial installation workflow is not currently provided. Obtaining the runtime package and updates also requires an arranged transfer process.
Deployment checklist
- Validate a server capable of Linux containers, camera connectivity and detector performance on representative footage.
- Register the company and physical cameras, then request an invoice.
- After the administrator confirms settled payment and activates camera entitlements, obtain the runtime package and trusted public signing key.
- Create a private server identity and local camera map, and complete commercial activation.
- Start the runtime with its licence folder mounted read-only and a strong local API key.
- Connect each approved stream, verify detection output and establish monitoring and recording-retention procedures.
Use the full deployment and licensing guide for PowerShell and Docker examples. The supplied image is CPU-based; GPU, Jetson and in-camera deployments need separate validation.
Protect the server and camera network
Restrict the runtime to the intended local network. The guide starts with a loopback-only API binding. For access from other computers, arrange firewall rules and TLS with your IT team. Do not expose the camera credentials or detector API directly to the public internet.
Keep the private device key protected on its activated server. The licence binds the company, registered camera identities, server public key and approved stream endpoints. Do not copy that identity to another server. Software-held keys cannot prevent cloning if someone copies them; endpoint binding is not physical-camera attestation.
Perpetual use and maintenance
Commercial camera licences permit perpetual use of the licensed software version and include two years of updates and support from activation. Expiry of that support period does not expire the production token. Future upgrades are optional paid updates. The runtime does not currently enforce software-version upgrade eligibility.
Maintain the host, clock, network and recording storage. A disconnected runtime retains only its remaining signed lease grace; explicit renewal denials stop a connected runtime. The perpetual entitlement token itself is separate from runtime authorisation. Hardware failure, identity recovery and refunds require operator assistance and do not automatically permit licence transfer.
Common questions
Does an evaluation licence work offline forever?
No. Sandbox evaluation tokens are time-limited, usually up to 30 days and bounded by entitlement expiry. They need an active entitlement and an online entitlement refresh before expiry. Customer operation additionally requires online startup and runtime lease renewals every minute, with up to ten minutes of outage grace.
Can it provide guaranteed safety monitoring?
No. AICraft Ware is not a certified safety system. Validate detections at your site and retain your existing safety controls.