✅ Quick Summary
Push44 reads your project files directly from each platform's API and pushes them to GitHub. The process is identical for all four supported platforms. Once on GitHub, your code is safe, version-controlled, and completely platform-independent.
The Problem
Most AI app builders don't provide native export or backup features. Your app's source code lives exclusively on their platform. This creates three risks: (1) You lose access if you can't pay for the platform, (2) The platform could shut down or change terms, (3) There's no version history if AI generation goes wrong.
How Push44 Solves It
Push44 reads your project files directly from each platform's API and pushes them to GitHub. The process is identical for all four supported platforms. Once on GitHub, your code is safe, version-controlled, and completely platform-independent.
Step-by-Step Guide
Choose which platform to back up first
Start with your most important project. Push44 supports Base44, Rocket.new, Floot, and Zite. Pick the platform where you've invested the most time.
Create a GitHub repository for backups
In GitHub, create a new private repository for your project. A good naming convention is 'projectname-platform-backup' (e.g., 'myapp-base44-backup'). Initialize it without a README so the first push is clean.
Connect your platform in Push44
Open Push44 and select your platform. Enter the required credentials (API token for Base44, session tokens for Floot/Zite, API token + company ID for Rocket.new). Push44 loads your projects.
Do your first backup export
Select your project, enter your GitHub repository details, and click 'Push to GitHub'. This is your baseline backup — a complete snapshot of the current state.
Set up a recurring backup schedule
Commit to running Push44 after each development session, or at minimum once a week. Each export creates a new git commit, building a timeline of your project's history.
Pro Tips
- Back up all your AI projects, not just the ones you're actively developing.
- Keep backup repos private to protect your intellectual property.
- Consider tagging important commits in GitHub (e.g., 'v1.0', 'before-redesign') for easy reference.
- Push44 shows a file count after each export — verify the count stays consistent to ensure all files are included.
Common Mistakes to Avoid
- Only backing up once and never updating — your backup becomes useless as the project evolves.
- Using a public repo for sensitive business logic — keep backups private unless intentionally open-sourcing.
- Not verifying that the backup is complete — spot-check a few files in GitHub after each export.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.