STABLE VERSION
LoadingReading signed metadataYOUR PERMANENT CONTROL PLANE
One address.
Every signed update.
A dedicated home for Digital Twin Ai software releases. Your development PC can change. Your machines keep a stable update address.
01
Original signing identity
Every package is authenticated and checked before it is served.
02
Local installation approval
A machine administrator or engineer decides when to install.
03
Independent distribution
Update packages stay hosted here, not on your desktop PC.
OWNER ACCESS
Sign in to Services
Use the private owner access key created for this deployment. It is not your Netlify or controller password.
No customer data, machine records or release files are public. This site has no machine-control authority.
SERVICES OVERVIEW
Release control
Reviewed software in. Verified packages out.
VERIFIED RELEASES
LoadingStored releases, not controller installationsDISTRIBUTION
Hosted hereIndependent of the local PCINSTALLATION
Local approvalNo automatic installationIMMUTABLE & AUTHENTICATED
Release library
REPORTED EVIDENCE
Controller update reports
Legacy credentials use a shared token. Reporting IDs below are self-declared, not verified machine identities or proof a machine is online.
STABLE ADDRESS, CHANGEABLE HOSTS
Service routing
Update distributionThis deployment
Permanent custom hostnameupdates.digitaltwinai.devDNS & controller acceptance pending
CAM processingLocal Windows host, loopback onlyPublic HTTPS route pending
Changing a processing host will not change the update download route. This portal does not yet redirect CAM or manage enrolled-machine routing. Arbitrary destination URLs and credential forwarding are not allowed.
Existing controllers still need the separately reviewed native endpoint bridge. A static dashboard release alone cannot replace their pinned downloader.
FLEET FOUNDATION
Customers, configuration profiles & device enrolment
These are strongly consistent records, not controller control. A verified device identity exists only after a one-use ticket is claimed. Serial and installation observations remain operator-asserted until a future paired-controller integration verifies them.
Integration boundary: this portal does not currently receive controller heartbeats or enforce entitlements on existing CNC software. Required-update records do not install updates on a running machine, affect motion/stops, disable native CNC, or hide safety controls. Enforcement requires the next paired-controller integration.
CUSTOMERS
Customer enrolment & eligibility
COMPATIBILITY METADATA
Configuration profiles
Profiles are immutable by ID and may update only brand, model, controller family and signed-release channel. Motion, spindle, registers, PLC parameters and URL origins are not accepted.
PENDING → PAIRED
Machine records & enrolment
One-use enrollment ticket — shown once
POLICY RECORDING
Required update
Target a signed release to a machine record, customer or customer group only after channel compatibility is checked. This is not “Force install.”
Not a control path. Current legacy shared update credentials remain unverified and unchanged. This foundation has no billing/payment integration and does not route public CAM traffic.