✓
the short answer

Push44 authenticates with Floot using a session token, reads your project's complete source file tree via Floot's reference API, and pushes all files to GitHub. The export includes all components, styles, and configuration exactly as they exist in Floot.

📖 Introduction

Floot lets you build and publish web apps using AI. But its source code stays on Floot's servers. Push44 connects to Floot's API to export your complete project source code and push it to GitHub — giving you full ownership of your app.

The Problem with Walled Gardens

Floot is a web app builder that publishes apps to the web, but it doesn't provide a native way to download or version-control your source code. Your project files — components, styles, logic — exist only within Floot's platform.

The Push44 Solution

Push44 authenticates with Floot using a session token, reads your project's complete source file tree via Floot's reference API, and pushes all files to GitHub. The export includes all components, styles, and configuration exactly as they exist in Floot.

Step-by-Step Walkthrough

4 steps
1

Get your Floot session token

The Floot authentication uses a session token. Open Floot in your browser, open Developer Tools (F12), go to Application → Cookies, and find the session cookie. Copy its value. This is your Floot token for Push44.

💡 expert tip

Push44 also supports Floot's magic link authentication flow — if you have trouble with the cookie approach, try generating a magic link from Floot's login page.

2

Connect Floot in Push44

Open Push44 and select Floot as your platform. Paste your session token. Push44 verifies the token and loads your Floot workspace.

3

Select your Floot project

Push44 shows your Floot workspace and available projects. Select the app you want to export. Push44 reads the project's source file tree via the workspace reference API.

4

Push to GitHub

Enter your GitHub repository details and click 'Push to GitHub'. Push44 exports all your Floot source files — components, styles, routing, and configuration — to your GitHub repo.

Pro Recommendations

✓

Floot session tokens expire — if Push44 shows an auth error, get a fresh token from your browser cookies.

✓

Export before making major changes in Floot so you have a rollback point.

Common Pitfalls to Avoid

⚠️

Copying only part of the session cookie value — they can be quite long.

⚠️

Not refreshing the Floot token when it expires — check Push44's error message for auth issues.

Frequently Asked Questions

Does exporting Floot remove my app from Floot?

No. Push44 only reads your project. Your Floot app continues to run and be hosted by Floot normally.

Does the Floot export include published pages or just source code?

Push44 exports the source code — the actual files and components. The published/hosted version is separate and remains on Floot's servers.

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