Skip to content

Choose a deployment task ​

Hosting viewer software, publishing workflow files and deploying contracts are different jobs. Choose the outcome below; each procedure states its prerequisites and what it changes.

To open an app that is already deployed, use the Gallery. None of the operator procedures below is needed just to browse.

Create or host

Deploy a new app instance
Create contracts and a CAM publication through separately approved transactions, with an explicit pause to host the files.
Host the stand-alone viewer
Serve browser software at your own HTTPS hostname. This creates no contracts or CAM publication.
Open a saved publication locally
Inspect existing contracts using the retained instance and a browser-accessible RPC.

Maintain an existing instance

Update a published app
Choose a compatible CAM-only change, projection replacement or an explicit business-contract migration. Preparation does not publish.
Recover an interrupted release
Inspect retained evidence and resume only what remains. Do not start another deployment to repair incomplete records. See its stop and cancellation procedure for uncertain outcomes.
Publish or recheck contract sources
Verify the original compiler inputs with Sourcify. A failed verification request does not undo a deployment.

Practice and prepare

Rehearse the release workflow
Use a retained local chain or an isolated approval/publication rehearsal, without public funds.
Test an approval image
Exercise the reviewed approval input and fixture-only acceptance or rejection. For a simpler first experience, follow the local-wallet tutorial.

App-specific settings

Choose the business contract's authorities and configuration before starting the shared deployment procedure:

Bike NFT · Escrow · Pay-to-Play.

Operational reference

For the underlying evidence, authority and runtime boundaries, consult the operations reference. Its Docker identity section covers private-file access, while handoffs explains separate nominee acceptance.

For failed operations, use bounded diagnostics. For transport choices, use Networks and RPC services. Catalog entries do not authenticate contracts.