Deployment walkthrough
Planning a Pulsar Deployment
A public planning and validation guide for Pulsar infrastructure, network boundaries, runtime dependencies, storage, promotion, and recovery.
Key considerations
Prepare
Define environment, host, ports, DNS, proxy, storage, and ownership.
Connect
Verify the primary model runner, optional utility model, and ComfyUI.
Promote
Run readiness checks, retain rollback evidence, and validate backups.
Architecture at a glance
Define the operating model first
Assign ownership for the compute node, model runners, media runtime, DNS and TLS, identity, backups, monitoring, updates, and incident response before installation begins.
Prepare isolated environment resources
Choose a unique environment label, port plan, volumes, network, database state, object-storage location, public URL, and origin policy. Peer environments must not share mutable application data.
Prove each dependency
Validate the application API, database, Valkey, SeaweedFS object storage, selected chat runner, optional utility service, and ComfyUI before accepting the deployment.
Promote with a rollback point
Back up state, document environment-specific overrides, run the release gate, and retain the previous known-good application package and configuration.
Request the current package
Exact installer commands and package details are provided after an architecture review because the supported path depends on the target environment and current release.
Private deployment consultation
Review Pulsar against your environment.
Bring the infrastructure, security boundaries, model runners, and use cases. The Pulsar team will map the appropriate deployment path.