Getting started
Bring one application.
Prove one update.
The intended path is written and asynchronous. Prepare the requirements below before committing a customer installation. Production enrollment is not open yet.
Check the scope
Run the compatibility check. Confirm the host architecture, dedicated engine and supported application shape. Unknown answers need technical resolution before installation.
Write down your application contract
List image digests, service ports, named data volumes, required configuration and a meaningful health check. Document the database version and migration behavior. A generic Compose file is not automatically a supported Shipstead package.
Prepare a disposable test host
Use a dedicated host or VM and synthetic data. Record who owns the Docker engine, backup key and maintenance approval. Do not reuse production data or a shared customer engine for an initial evaluation.
Define success before testing
Measure setup time, per-update review effort and the expected final application state. Include a data check and a reviewed recovery exercise. An HTTP success response alone does not prove that customer data survived.
Follow the released installation path
When enrollment opens, the intended sequence is vendor workspace → offline signing setup → host request → signed customer kit → verified install → exact-plan approval → inspected result. Public distribution and independent onboarding still need release acceptance.