General

FloopFloop is an AI app builder. You describe what you want in plain language, and our AI writes a real Next.js application, deploys it, and gives you a live URL on *.floop.tech (or your own domain). You can refine it through chat, add secrets, schedule cron jobs, and ship updates without leaving the browser. It is aimed at founders, indie hackers, and developers who want to skip the boilerplate.

No. Most users never look at the source code. You write your idea in plain English (or any of our 13 supported languages), and FloopFloop handles the technical work — choosing the framework, structuring the database, deploying the site, and provisioning SSL. If you do know how to code, you can connect your project's GitHub repo and edit it directly, but it is fully optional.

A typical first build runs 2 to 9 minutes. The pipeline has five stages: understand the prompt, write the code, create the GitHub repo, build & deploy to AWS, and wire up DNS + the database. You see live progress for each stage. Refinements (changes after the first build) usually finish in under 90 seconds because we only rebuild what changed.

Sign in, click "New project" on your dashboard, type a description of what you want to build (the more specific, the better), and pick a subdomain. FloopFloop will then design, code, and deploy your app automatically. You will see five build stages run in real time. When the build finishes, your project is live at https://your-subdomain.floop.tech and you can chat with it to make changes.

Anything from a landing page to a SaaS dashboard, a small CRM, a portfolio, a booking site, or an internal tool. The more concrete you are, the better the result. Helpful details: who the users are, what actions they take, what data the app stores, what the home page should show first, the visual style you want, and which integrations matter (Stripe, Google Sheets, an API). Vague prompts produce generic apps; specific prompts produce something closer to your idea.

Yes. The prompt box accepts images (screenshots, sketches, mockups), PDFs (for reference docs or specs), and CSV/JSON sample data the AI can use as a starting schema. The AI reads them as part of the same instruction. This is the fastest way to get pixel-close UI or to seed the database with realistic shapes. Files are stored privately and only used for your project's build.

On the very first build it does not pause to ask — it commits to the most reasonable interpretation so the build can finish in one shot. After the build is live, the chat does ask follow-up questions when something is ambiguous, especially around data shape or destructive changes ("delete all users — are you sure?"). If you want a clarification round on the first build, write "ask me before deciding" in your initial prompt.

Browse /library, open any public project, and click "Clone". A copy is created in your account with a fresh subdomain. The original is untouched — the author keeps theirs, you own yours. Cloning costs 2 credits (the same on every paid plan). After cloning, the project is fully yours: you can refine, change, deploy, or delete it independently.

Yes, on Starter and above. Open the project's Settings → Visibility and switch to "Private". The change takes effect immediately: the public URL begins requiring login, the project is removed from the library, and search engines that have already indexed it will drop it on their next crawl. You can flip back to public any time. Free-plan projects must stay public.

Archiving keeps everything (code, database, secrets, deployment URL) but takes the project offline and stops it counting against your project quota. You can unarchive any time and the URL comes back. Deleting is permanent: after a 30-day grace window the GitHub repo, S3 assets, database, and DNS records are all wiped. Use archive when you might come back, delete when you really won't.

Yes. Every successful build is snapshotted. Open the project's Versions tab, pick any past build, and click "Restore". The site is rolled back to that exact code in under a minute and any chat refinements you made after it become a fresh chain of changes on top of the restored point. You don't lose history — every snapshot stays available for 90 days.

90 days for every plan. The most recent successful build is always restorable, even past 90 days, but the longer history beyond 90 days is pruned to keep storage costs predictable. If you need a build preserved beyond that, fork it (clone) — the clone keeps its own independent snapshot timeline.