Install CrateSphere on a Windows PC
Set up a private portal on one Windows computer, then publish it to your own HTTPS address when collaborators need in.
Read the full guideCrateSphere deployment
Self-host CrateSphere.
Run a dedicated portal for one label, on infrastructure you control. Your label chooses the host, storage, public address, backups and maintenance window.
Your installation, your operational data
In the current self-hosted model, CrateSphere does not run the label's portal, database, file storage, user accounts or credential vault. Catalogue material, contacts, project activity and mobile sessions remain with the label's own installation and infrastructure.
CrateSphere may receive information only when you choose to contact us for a demo, support or product discussion. A self-hosted installation does not automatically send customer information back to CrateSphere.
Choose the route that fits
Install CrateSphere on a cloud server
Run a permanently available portal on a rented Linux server, with your own database, storage and public address.
Read the full guideMove a portal from Windows to a cloud server
The supported procedure for moving an existing Windows installation onto an always-on cloud server.
Read the full guideWhat the supported setup covers
- A separate application stack for each label, with its own database, storage and credentials.
- A label-controlled HTTPS address for browser access, invitations and companion-device pairing.
- Storage, backup and recovery choices that stay under the label's operational control.
- A controlled update process that keeps source updates separate from database, media, credentials and runtime data.
Mobile companion connection
The iOS companion connects to the label's own verified portal address. QR pairing hands that address and a short-lived pairing token directly to the device; the self-hosted connection route does not use a shared CrateSphere mobile API base URL.
Device credentials are stored in the iOS Keychain. Only authorised AAC/M4A preview derivatives can be cached for offline listening; source masters and storage keys are not transferred to the device. Cached previews are device-protected, excluded from iCloud backup and removed when the portal is removed or the user signs out.
Cloud discovery is a separate optional feature for cloud-configured app builds. It is not used to connect to a self-hosted portal, and any live cloud service will have its own published privacy and service terms.
Where these instructions come from
Each guide on this site is generated from the installation documentation that is versioned alongside the software, so the prerequisites, commands, security checks, update procedure and recovery steps match the release they describe rather than drifting away from it.
You do not need an account anywhere to read them, and you do not need one to run CrateSphere on your own infrastructure.