Support

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.

One project, one initial build, and three free refinements. Your project lives at *.floop.tech with a small "Built with FloopFloop" badge and stays publicly visible. You get 500 MB of storage and 10 K AI tokens per day. There is no time limit — you can stay on Free as long as you want. To remove the badge, go private, or build more than one project, upgrade to Starter or higher.

Credits are FloopFloop's currency for AI work. A new project build costs 5 credits, a chat refinement costs 1, redeploying without changes costs 1, and cloning a public project costs 2. Paid plans include a monthly credit allowance (Starter 75 / Pro 200 / Business 500). If you need more, you can buy top-up packs at any time without changing your plan.

Existing projects keep running normally — public URLs do not go down, scheduled jobs keep firing, custom domains stay live. What stops is new AI work: you cannot start new builds, run refinements, or clone from the library until you either buy a top-up pack, upgrade your plan, or wait for next month's allowance to reset on your billing date.

Yes, but only for a limited window. Unused credits from your monthly allowance roll over for one month on Starter and two months on Pro and Business. After that they expire. Top-up credits you buy à la carte don't expire — they sit in your account until you spend them. Free-plan refinements don't roll over.

Yes. Open Billing → Top-up and pick a pack: 25 credits for $5, 75 for $12, or 200 for $25. Top-ups are charged once, applied instantly, and don't change your subscription. Top-up credits never expire, and they are spent only after your monthly allowance is used up — so you don't accidentally burn the pack you paid for.

First, open the build's status page — every stage has a Logs button that shows exactly where it failed. Most failures fall into three buckets: a transient infrastructure hiccup (just click Retry), a code error the AI can fix on its own (start a chat with "the build failed, the error is: …" and paste the relevant log line), or an upstream issue with a connected service (Stripe, GitHub, your custom domain provider). If none of those apply, message support with the project ID — we can re-run the pipeline manually.

Three common causes. (1) The DNS hasn't fully propagated yet — wait 5–15 minutes and hard-refresh. (2) Your browser cached an older asset — open in an incognito window. (3) The first build's output was syntactically valid but logically wrong — start a chat with "the page is blank when I open the home page" and the AI will fix it on the next refinement. The browser console (F12 → Console tab) usually shows the underlying error.

Builds run in a shared queue. Free and Starter plans have standard priority and may wait a few minutes during peak hours; Pro and Business get priority slots and almost never queue. If your build has been queued for more than 10 minutes, that's unusual — refresh the page (the status updates over websocket and sometimes the connection drops), and if it still hasn't started, message support with the project ID.

Yes. Open the project, click the three-dot menu, and choose "Redeploy". Your code stays exactly the same — but new environment variables get picked up, expired build artifacts get rebuilt, and any platform-side improvements (security patches in the runtime, for example) are applied. A no-change redeploy costs 1 credit and finishes in under a minute.

On AWS, in the us-east-1 region by default. Static assets serve from CloudFront's global edge network, so your visitors hit a nearby PoP regardless of where the origin lives. Server-side rendering runs on AWS Lambda, your project's database is on Amazon RDS Postgres, and uploaded files live in S3. EU data residency is on the roadmap but not yet available — let support know if it is a hard requirement for you.

On the sign-in page, click "Forgot password". Enter the email on your account and we'll send a reset link that's valid for 30 minutes. The email comes from `accounts@floop.tech` — check spam if you don't see it. If your account was created via Google sign-in only, there's no password to reset; sign back in with the same Google account instead.

Yes. The sign-in screen has a "Continue with Google" button. If you already have an account with the same email as your Google address, the two are linked automatically — both methods work from then on. New accounts created via Google can add a password later under /account/security so they're not locked into one auth method.

Open /account/security → Two-factor auth, scan the QR code with any TOTP app (Google Authenticator, 1Password, Bitwarden, Authy, etc.), and enter the 6-digit code to confirm. Save the recovery codes we show you afterwards somewhere safe — they're the only way back into the account if you lose your authenticator. Once 2FA is on, every new browser session and CLI device authorisation will ask for a code.

Sign in with one of the recovery codes you saved when you enabled 2FA — at the code prompt, click "Use a recovery code instead". Each code works exactly once. Once you're back in, regenerate a fresh set under /account/security. If you've lost the device and don't have any recovery codes, contact support from the email address on the account; we'll verify your identity manually before unlocking the account, which usually takes 24–48 hours.

Open /account/profile, edit the email field, and click Save. We send a confirmation link to the new address — clicking it completes the change. The old address gets a notification (in case it wasn't you), and any pending sessions on the account are kept active. If your account uses Google sign-in tied to a Google address, change the Google email itself or unlink Google first under /account/security.