Skip to main content
Deploy all your project resources to Base44 in a single command. This includes entities, functions, connectors, agents, agent skills, auth config, and the build code for your frontend. The command provides a summary of what will be deployed and asks for confirmation before proceeding.
The confirmation summary lists resource counts, but does not call out which resources will be deleted. Review the Sync behavior section below before running deploy on a project where you may have removed local entities, connectors, agents, or agent skills.
If any connectors require OAuth authorization, the deploy command will prompt you to authorize them in your browser, similar to running connectors push. You can also deploy resources individually using entities push, functions deploy, connectors push, auth push, and site deploy. Before running this command, ensure that your built frontend files are in the directory specified by site.outputDirectory in your config.jsonc file.

Usage

Flags

Sync behavior

The deploy command creates and updates all resource types, but handles deletions differently for functions than for entities, connectors, agents, and agent skills.

Entities, connectors, agents, and agent skills

Entities, connectors, agents, and agent skills are fully synced, the same way as entities push, connectors push, agents push, and agent-skills push. Remote resources not found locally are removed:
Removing an entity removes its schema from Base44. Existing data is not deleted, but the entity will no longer be accessible through the SDK.Removing a connector removes the OAuth connection from Base44. Functions that use the connector will fail until it’s reconnected.If your project has no local agents, or no local agent skills, that resource type is left untouched rather than deleted. Otherwise, any remote agent or agent skill missing from your local files is removed, even though the confirmation summary does not list it separately.

Functions

Functions are deployed but not pruned. Remote functions not found locally are left unchanged. To remove remote functions that are no longer in your project, use functions deploy --force.

See also