✓
the short answer

The Push44 client-side method provides seamless Git integration. Leveraging your personal Base44 API authentication token, Push44 connects directly to Base44's sandbox endpoint (GET /apps/:appId/sandbox/files) to fetch your full project tree. It then constructs a cryptographic SHA-1 Git tree object locally in WebAssembly and posts directly to GitHub's REST API (POST /repos/:owner/:repo/git/trees and POST /repos/:owner/:repo/git/commits). No intermediaries, zero server telemetry, and completely open source.

📖 Introduction

Exporting applications built with Base44 into an independent GitHub repository enables professional source control, version branching, and team collaboration. In this guide, we introduce the direct method to connect Base44 to GitHub using Push44's zero-backend Trees API engine. This protocol reads your sandboxed React, TypeScript, and Tailwind files directly in browser memory and commits them into your GitHub repository with complete version history in one click.

The Problem with Walled Gardens

Developers who build applications on AI prototyping platforms need standard Git version control to manage releases, branch features, and maintain automated backups. Downloading flat ZIP archives strips commit history and makes differential tracking impossible.

The Push44 Solution

The Push44 client-side method provides seamless Git integration. Leveraging your personal Base44 API authentication token, Push44 connects directly to Base44's sandbox endpoint (GET /apps/:appId/sandbox/files) to fetch your full project tree. It then constructs a cryptographic SHA-1 Git tree object locally in WebAssembly and posts directly to GitHub's REST API (POST /repos/:owner/:repo/git/trees and POST /repos/:owner/:repo/git/commits). No intermediaries, zero server telemetry, and completely open source.

Step-by-Step Walkthrough

5 steps
1

Obtain your Base44 Personal Auth Token

Log in to your Base44 account at app.base44.com. Open browser DevTools (F12) > Application > Cookies to copy your access_token (or generate a personal access token in Account Settings > API Keys).

💡 expert tip

Your credentials remain securely in your local browser sandbox and are never transmitted to any third-party server.

2

Generate a GitHub Personal Access Token (PAT)

Visit GitHub.com > Settings > Developer Settings > Personal Access Tokens (Classic or Fine-Grained). Create a token with the 'repo' scope enabled so Push44 can create and update repositories on your behalf.

💡 expert tip

For maximum security, fine-grained tokens can be scoped strictly to the specific repository you designate for your Base44 project.

3

Connect your accounts in Push44

Open Push44 (push44.vercel.app) or launch the terminal CLI ('p44'). Go to Settings and enter your Base44 token alongside your GitHub PAT. Push44 validates the connections in milliseconds and lists your active Base44 apps.

💡 expert tip

Push44 instantly verifies token validity via Base44's GET /auth/me and GitHub's GET /user endpoints.

4

Select your Base44 app and configure repository target

Navigate to the Push dashboard. Select your target Base44 app from the visual picker. Choose an existing GitHub repository from your account or type a new repository name for Push44 to create automatically.

💡 expert tip

You can customize your target branch (e.g. main, dev, or base44-backup) and specify a custom commit message.

5

Execute one-tap push to GitHub

Click 'Push to GitHub'. Push44 computes the file differential in memory, displays modified and new files, builds the Git tree, and pushes the commit directly to GitHub in under 5 seconds.

💡 expert tip

You can view your live repository immediately on GitHub with complete file formatting and folder structure preserved.

Pro Recommendations

✓

Run Push44 after every major AI prompting session in Base44 to maintain an immutable commit log of your application's evolution.

✓

Push44 ensures exported code components adhere to standard React structure and clean production styling.

✓

You can also use Push44 CLI ('p44 push') directly in your terminal for automated CI/CD and cron backup workflows.

✓

Push44 works entirely client-side, meaning there are no file size restrictions or third-party queue delays.

Common Pitfalls to Avoid

⚠️

Downloading manual ZIP snapshots instead of using Git trees, which makes tracking incremental code changes impossible.

⚠️

Leaving your Base44 app unbacked up during rapid prompting sessions, risking unintended AI code regressions.

⚠️

Sharing your GitHub PAT or Base44 API keys publicly — always keep them isolated in your secure browser storage.

Frequently Asked Questions

Is this new Base44 export method really 100% free?

Yes, absolutely. Push44 is an open-source, zero-backend web application and CLI. There are no paywalls, subscriptions, or AI credit deductions required to sync your code.

Does this method work with complex full-stack Base44 applications?

Yes. Push44 exports the entire project structure, including React frontends, Tailwind configuration, Vite build scripts, API route handlers, and environment schemas.

Do I need to install Node.js or Git on my computer to use this?

No. The Push44 web app runs entirely in your web browser on desktop, tablet, and mobile. If you prefer the terminal, a lightweight standalone CLI is also available.

Can I push to private GitHub repositories?

Yes. You have full control over whether your target repository is created as public or private on your GitHub account.

Will syncing to GitHub disrupt my live deployment on Base44?

Not at all. Push44 reads the source files via non-invasive read APIs. Your live app hosted on *.base44.app continues running smoothly without any interruption.

100% free · zero backend · client-side

Export and push your code in seconds.

Connect your platform, preview the visual diff, and create atomic commits on GitHub with zero server data retention.

Start exporting now → Learn more