Skip to main content
The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data models and code, deploy resources, and run commands against any app on your account, including apps you built in the Base44 online app editor and never linked locally.
The CLI and backend service are currently in beta. We’re actively improving the platform and documentation based on user feedback. Share your thoughts and feature requests on our GitHub Discussions page.

​
Installation

Or run commands directly with npx:
Requires Node.js 20.19.0 or higher.

​
Create projects

Create new Base44 backend projects with the create command. You can choose from available templates to get started quickly. See our quickstart articles for a detailed walkthrough:

​
Start from a Base44 app

If you’ve built an app with the Base44 app editor, the CLI gives you two ways to work with it. Commands that don’t need a local project work against any app you have access to. Authenticate with login, then run commands with --app-id <id> or set the BASE44_APP_ID environment variable. Useful for tailing logs, running scripts, managing secrets, and setting up connectors from anywhere on your machine. For a full local copy of the app to develop offline or in a custom IDE, set up the GitHub integration to keep your app in sync between Base44 and your repo. Alternatively, the eject command creates a one-time local copy with a new app id. For a step-by-step eject guide, see Start from an Existing Base44 App. If you have existing Base44 backend project code, such as from an example app, use the link command to connect it to a Base44 backend. For a step-by-step guide, see Link an Existing Backend Project.

​
Manage workspaces

If you belong to multiple workspaces, the CLI can target them directly. Create new apps in a specific workspace with create --workspace or link --create --workspace, and move an app between workspaces with workspace move. Use workspace list and workspace get to find workspace IDs.

​
Manage resources

Define entity schemas as JSON files, write serverless functions in TypeScript, configure AI agents, and set up OAuth connectors for external services. The CLI validates your definitions, reports what changed, and keeps your local and remote resources in sync.

​
Develop locally

Start a local development server with dev to test your project on your machine without deploying. See the Local development guide for details.

​
Bring your own agent

The sandbox commands work the other way around. Instead of running your project locally, they connect to the app’s sandbox, the cloud environment that holds the app’s code, and runs its development server. There is no checkout and nothing to install, and writing a file is all it takes to ship the change. Explore the app with sandbox ls, sandbox read, and sandbox grep. Change it with sandbox write and sandbox edit, run builds and tests with sandbox run, and mark a known-good state with sandbox checkpoint. This is how you point your own AI coding agent at a Base44 app. It requires a Builder plan or higher.

​
Deploy your project

Deploy all your project resources to Base44 with the deploy command. This pushes entities, functions, connectors, auth config, and site files in a single operation. You can also deploy resources individually using entities push, functions deploy, connectors push, auth push, and site deploy. After deploying, use site open to open your live site in the browser.

​
Configure authentication

Manage your app’s login methods from the command line. Pull the current config with auth pull, toggle email/password with auth password-login, toggle social providers (Google, Microsoft, Facebook, Apple) with auth social-login, and push your changes with auth push. Auth config is also included when you run deploy.

​
Run scripts

Run standalone TypeScript or JavaScript scripts that interact with your app using exec. A pre-authenticated SDK client is available as a global base44 variable, so you can access entities, functions, and integrations without any setup code. Pass --app-id to target a specific app, or run it inside a linked project to use the project’s app. Useful for data migrations, seed scripts, ad-hoc queries, and automation. See the Standalone scripts guide for a full walkthrough.

​
See also