Deploy

Publish tested app versions with required production configuration.

Deploy an app when its current version is ready for users. Review the live preview and test results first.

Publish an app

1

Open the publish panel

Select Publish in the app workspace. The panel shows the last published version, its date, and the live URL.

Open or copy the URL, or select Manage Domains to manage its domain.

The publish panel.

2

Complete the publish checklist

Review the dependencies for the published app:

• Database — required; select Connect when it shows Not Configured

• External Services Used — confirm each service for Preview and Publish

• Environment Variables — confirm values for Preview and Publish

Update database, domains, integrations, or environment variables in App Config.

The publish checklist.

3

Publish the version

Select Publish Changes. The platform deploys the current version and updates the live URL.

A published app requires a configured database. Complete the checklist before publishing.

Resolve a failed publish

When publishing fails, Qore shows Publishing Failed and Failed to load preview. Select one of these actions:

• Try Again to retry the publish

• Fix with AI to send the failure to the build agent

• Close to dismiss the notification

A failed publish, with recovery actions.

Fix with AI sends the reported issue to Qore's build agent. Review the rebuilt preview before you continue.

Select View Error Details to open the deploy log. It shows numbered build steps and the underlying error. Use the log to fix the issue, then select Try Again.

The deploy log's error details.

For example, a missing package.json appears as an npm install failure with error code ENOENT.

Versions

The version selector lists builds newest first. Latest marks the newest build. Published marks the live version. Uncommitted changes marks work outside a version.

Select a version to review or return to it. The published version can differ from the latest build.

What ships

After testing, the platform packages the project as one deployment unit:

• Frontend code — UI components, state managers, and inline styles compile for production

• Infrastructure settings — connected database variables, storage links, and custom routing stay mapped to the container

• Attached agents — prompts, compliance skills, and reasoning logic travel with the app export package

Enterprise publishing

The publishing engine supports high-concurrency environments and automates server configuration.

• High-traffic infrastructure — the pipeline manages concurrent enterprise publishing requests

• Request queuing — deployments process sequentially to prevent stuck states during peak periods

• Zero-downtime rollouts — infrastructure updates migrate in the background

• Production stability — backward-compatible upgrades preserve published apps through platform updates

Staging and governance

• Isolated staging controls — deploy privately for compliance, risk, and security review

• Performance-ready clusters — published apps run on multi-region nodes optimized for sub-second load times

Publish is unavailable in Plan Mode. To gather feedback before compiling code, use the public view links from Share Project. See Plan.

---

After publishing, use Operate to track costs and acquisition.