Everything you need
to get started.

Install cx-shipd

Download the latest Windows first-install ZIP from the button above. For Windows app releases, the ZIP contains the versioned application executable, stable launcher, project updater, and update configuration.

1. 1
   Download the package

   Use the download button on this page or the Latest release card on the home page. If the button is disabled, the maintainer has not published a valid stable manifest yet.

2. 2
   Extract the ZIP

   Extract it to a folder that your Windows user can write to, such as a folder under your user profile. Don't run the app from inside the ZIP preview.

3. 3
   Run the stable launcher

   Open cx-shipd-Launcher.exe (or the exact launcher filename provided in the package). Use the launcher instead of opening a versioned EXE directly so the update workflow can find the active release.

4. 4
   Review Windows prompts

   Windows may show a reputation or publisher warning for an unsigned or newly published app. Only continue if you trust the publisher and obtained the file from the official CX Designs site.

First launch checklist

• Extract the package into a writable folder.
• Keep the launcher, updater, versioned executable, and project_update.json together unless the release notes say otherwise.
• Launch through the stable launcher each time.
• If cx-shipd asks for backend configuration, enter only the URL and client-side key your project is designed to use.
• Test the app's main feature before relying on it for important work.

How updates work

The website serves release information and a stable JSON manifest. The local launcher/updater checks that manifest when the application starts, compares versions, and can offer to download a newer release.

If no update appears, launch through the stable launcher, check that you have an internet connection, and revisit the official site to confirm the latest version and release date.

Backends & integrations

Developers can connect compatible projects to services such as Supabase or other APIs. The correct SDK needs to be part of the project environment and included when the Windows app is built.

• Supabase: use the project's URL and a publishable/anon key with appropriate authorization policies.
• Other SDKs: install the required package in the project's Python environment and configure the release builder's backend preset if available.
• Dynamic imports: add a PyInstaller hidden import only when a required module isn't detected during the build.
• Test the packaged EXE: an app working in VS Code doesn't guarantee that every dependency or data file is included in the release.

Backend setup depends on the application. cx-shipd's website doesn't create backend accounts or supply private credentials for your project.

Security checklist

• Never package .env secrets, database administrator passwords, signing keys, or privileged service-account credentials.
• Never embed Supabase service_role or sb_secret_ keys in a public desktop app.
• Use HTTPS for the release website, manifests, and binary downloads.
• Review the release file list before publishing. Excluding common secret filenames is helpful but cannot detect every sensitive value.
• A SHA-256 hash detects mismatch or corruption; it does not protect against a compromised release host or manifest.
• Only install packages downloaded from a release site you trust.

Common problems

For developers

Code normally in VS Code. Use Designer Dashboard Studio to link only the project folder you intend to release, select the correct Python entry point, choose required backend integrations, and build a versioned release.

1. Test the project in its own virtual environment.
2. Review included files and exclude credentials and unrelated projects.
3. Build and test the release locally.
4. Import the generated netlify_site folder with publish_release.py.
5. Deploy the updated website's public folder to Netlify.
6. Test a real update from an older version before announcing the new release.