✅ Quick Summary

Push44 creates a live bridge between Base44 and GitHub. Every time you run Push44, it fetches the current state of your Base44 project and creates a git commit with only the files that changed. Over time, you build a complete git history of your project's evolution.

The Problem

Without a GitHub integration, Base44 projects live entirely on Base44's servers. If Base44 has downtime, changes their pricing, or you want to collaborate with developers who use Git, you have no way to access your code externally or build on top of it with standard developer tools.

How Push44 Solves It

Push44 creates a live bridge between Base44 and GitHub. Every time you run Push44, it fetches the current state of your Base44 project and creates a git commit with only the files that changed. Over time, you build a complete git history of your project's evolution.

Step-by-Step Guide

1

Generate a GitHub Personal Access Token

Go to github.com/settings/tokens and click 'Generate new token (classic)'. Give it a name like 'Push44', set an expiration (or no expiration), and check the 'repo' scope. Copy the token — you'll need it in Push44.

💡 Pro Tip
The 'repo' scope gives Push44 access to create and update both public and private repositories.
2

Get your Base44 API token

In Base44, open your profile settings and find the API Keys section. Generate a new token and copy it. This token authenticates Push44 to read your project files.

3

Connect both tokens in Push44

Open Push44, select Base44 as your platform, and paste both tokens. Push44 securely stores them in your browser's localStorage — they never leave your device or get sent to any Push44 server.

4

Choose your Base44 project

Push44 loads your Base44 projects. Select the one you want to connect to GitHub. Push44 fetches the complete file tree.

5

Set up the GitHub repository

Enter your GitHub username and repository name. Push44 supports both existing repos and new repos (it creates the repo automatically if it doesn't exist). Set your target branch — 'main' is the default.

💡 Pro Tip
For a clean first push, use a fresh empty repo. For ongoing syncing, use your existing repo.
6

Push and verify on GitHub

Click 'Push to GitHub'. Push44 creates a GitHub tree with all your files, packages them into a commit, and updates the branch reference. Open GitHub to verify — your files should appear within seconds.

Pro Tips

  • Set up a GitHub Action to auto-deploy your Base44 app whenever you push from Push44.
  • Use commit messages to document what changed in your Base44 session.
  • For team projects, all team members can use Push44 to push to the same GitHub repo.
  • The Push44 diff view shows exactly which files changed since your last push — review it before committing.

Common Mistakes to Avoid

⚠️ Watch Out For
  • Creating a GitHub token with only 'public_repo' scope — this won't work for private repositories.
  • Pushing to a GitHub repo that already has conflicting history — use a fresh repo for the first export.

Ready to Export?

Push44 is free, open source, and takes under 2 minutes to set up.

Start Exporting Now → View on GitHub

Frequently Asked Questions

Does Base44 have a native GitHub integration?
No. Base44 doesn't currently offer a built-in GitHub export feature. Push44 is a third-party open-source tool that bridges this gap.
Will Push44 overwrite my existing GitHub repo?
Push44 pushes to the branch you specify. If that branch has existing commits, Push44 creates a new commit on top of them — your history is preserved.
Can I use Push44 with a GitHub organization repo?
Yes. Enter the organization name as the username and the repo name. Make sure your GitHub PAT has access to the organization.
Is my Base44 API token stored securely?
Your tokens are stored in your browser's localStorage and never sent to any Push44 server. Push44 makes direct API calls from your browser to Base44 and GitHub.