Floot Connector plugs Floot into Claude and ChatGPT, so you can describe an app in the chat you already use and get a real full-stack app back with a database, user logins, and a live URL. Floot doesn't charge for AI credits. Your Claude or ChatGPT subscription does the thinking, and Floot handles the build, hosting, and deploy. And it's not just web anymore. Tell Floot to publish to iOS and Android, sign in to Apple or Google Play once, then keep shipping to the app stores from the same chat.
Build and publish real apps without leaving ChatGPT
Floot is now a native app in your ChatGPT sidebar. Describe what you want, watch it build in a live preview inside the chat, and publish it with a real link. Database, logins and hosting are built in, and the AI runs on your ChatGPT plan.
Floot MCPBuild and ship web and mobile apps inside Claude or ChatGPT
Launched on September 24th, 2026
FlootBuild serious apps with AI without getting stuck
Launched on August 7th, 2025
4.4
Based on 21 reviews
Review Floot?
Reviewers mostly see Floot as an accessible AI app builder that helps non-coders ship real websites and apps quickly, with a clean UI, strong support, solid hosting performance, and features like drawing changes directly on a page. Several users say it handles prompts more cleanly than rivals and avoids some common error loops; the maker of Panorama says it was easy enough to build internal tools with. But criticism is sharp where it appears: some users report arbitrary AI changes, weak revert flow, heavy quota burn, pricing friction, export and lock-in concerns, and, in one detailed case, risky production workflow issues around shared databases and staging.
user-friendly interface (8)built-in tech stack (6)no-code support (11)
Floot is allowing me to attempt to build a dream based on a lifelong obsession with nature, it's layers and connections, and the desire to share my vision with the world.
What needs improvement
mobile app limitations (2)
Would love to see options to top up build actions in small increments. I am one person on a limited budget trying to build a massive vision. I'm 2.5 weeks in and have barely scratched the surface, yet I run out of my 1000 build actions on the $25/month paid account daily. 5000 is too many, and I can't currently afford the $100/ month plan. Having a 500-1000 build action top up option would be amazing.
It lets you focus on building the app, not the technical nitty-gritty. For non-coders, it removes the barrier of backend management, hosting, and all that headache, while still giving you a powerful toolset. It’s like giving a designer access to a full development environment, but with a simplified, intuitive UI. Makes the whole building process feel way more accessible without compromising on functionality.
What needs improvement
One thing I'd tweak is offering a bit more flexibility for advanced users, like me. While it's great for non-coders, it’d be awesome to have more customization options for backend logic or integrations. A bit more room to grow for complex features could make it the go-to platform for both beginners and experienced devs.
vs Alternatives
I chose Floot because it simplifies the app-building process without sacrificing functionality. As someone who’s always juggling side projects, I needed a tool that could handle the full stack, from backend to hosting, without taking up too much time. Floot lets me quickly prototype and launch ideas without getting bogged down by setup or maintenance—perfect for turning concepts into working apps fast.
I've used most of the common site builders (wix, webflow, wordpress, etc) and Floot is the best by far. It's model agnostic and user friendly. Any issues were resolved within an hour or less which i'm not used to at all. Maybe most importantly the performance of the sandbox site and the prod site is great, seo friendly, etc. Can't say enough good things. Thanks Floot Team!
What needs improvement
putting guardrails on the AI so it doesn't go rogue and decide to do a full rebuild of the code and making the revert process a little more smooth. I was afraid to revert sometimes b/c it's not that intuitive like the rest of the site.
vs Alternatives
Faster, more user friendly, and overall product delivered is a magnitude better in terms of quality and performance. Service is also lightning fast
Floot was already one of the most used ways to build apps over MCP, and it’s the top-ranked app builder in ChatGPT. Now it’s a native app in your ChatGPT sidebar, which means it can:
→ Show a live preview of your app right inside the chat → Pick up what you’ve been discussing, so you don’t have to re-explain or copy and paste → Send prompts to ChatGPT for you while it builds
Then you can:
→ Publish to a real link, plus the App Store and Google Play → Get a database, user logins and hosting built in → Build on your ChatGPT plan. We don’t charge for AI tokens, and you get 100 free build actions a day
To try it: install Floot from ChatGPT’s app directory, sign in, type @Floot and tell it what to build.
What’s the first app you’d build from your ChatGPT sidebar? Our team is in the comments all day.
Report
@yujian Congrats yuj Building apps directly inside Chatgpt sounds really useful especially with live previews and built in hosting
The project contains a server-side integration-test endpoint at `POST /_api/integration/venueVerification`. This endpoint can execute database mutations within the sandbox's dedicated PostgreSQL database. It is intended exclusively for controlled integration testing.
Our read-only investigation confirmed that the project is unpublished but reports public visibility. We could not identify a documented, supported control for restricting access to this endpoint, making the project private, or disabling the endpoint without modifying application source.
The endpoint's fixed invocation header is not being treated as an authentication mechanism. We have not invoked the endpoint during this investigation.
Could you please clarify:
1. Does Floot support private or owner-only access for unpublished projects and their server-side API endpoints?
2. If so, what documented project or account setting controls that access?
3. Does unpublished status restrict access to `/_api/` endpoints, or can those endpoints remain reachable independently of the preview interface?
4. Is there a supported way to disable a single server-side endpoint or restrict it to authenticated project owners?
5. If no such control exists, what security approach does Floot recommend for a mutation-capable test endpoint?
6. Can Floot confirm whether the project's current visibility setting has implications for access to its server-side endpoints?
We have deliberately avoided probing the endpoint or making configuration changes while this remains unresolved.
We would appreciate documented instructions or confirmation of the supported approach. We will not resume integration testing until an appropriate access-control mechanism has been established.
@byalexai thank you Aleksandar! and yes — you publish straight from the chat and get a real live link, and you can push to the App Store and Google Play from there too
Report
This is so tempting — I love not having to re-explain an app idea sitting in my ChatGPT history. What's a good first app to try for a first build?
@ms_harita_kanuri haha that's exactly why we built it! a good first one is something small you'd use yourself, like a booking page, a habit tracker or a simple client form. try "@Floot build a booking page for a yoga studio with a login" and you'll see the whole flow in a few minutes
@ms_harita_kanuri Pick the idea you've already talked through most in ChatGPT, since Floot picks up that context. Small internal tools are a great first build.
@ms_harita_kanuri once you've picked one, come back and tell us how the first build went :) that re-explaining pain was basically the reason we made this
The part that would make or break this for me is picking up the earlier discussion in ChatGPT — if I've been going back and forth about an idea in a long thread, how much of that does Floot actually carry into the build? Does it use the whole thread's decisions, or mainly the prompt where I bring Floot in, and what happens if I change my mind partway through?
@jcbuilds great question JC. when you bring Floot in, ChatGPT passes along what you've been discussing, so you don't have to re-explain the idea or copy paste it. and if you change your mind partway, just say it in the chat and Floot updates the same project, since the project itself lives in Floot. @yujian can share more on exactly how much of the thread carries over
@jcbuilds honestly that's up to chatGPT which is pretty damn good at these. That's part of the magic - Floot gives chatGPT the power to build real websites and apps and you get to use the best capabilities of your agent instead of us forcing one on you.
@jcbuilds Great question. Since the project lives in Floot, you can keep changing your mind in the same chat and it keeps editing the same app, so nothing starts over.
@jcbuilds the long back-and-forth thread case is exactly what we tested on most. if you try it on one of yours I'd genuinely love to hear how it holds up
Scroll back through your ChatGPT history and you'll find at least one app idea that never got built. A booking page, a tracker your team keeps asking for, a client portal you've been "about to make" for months.
That's the gap Floot fills. A few things people already run on Floot:
→ a camera rental company in Czechia runs its bookings, payments and shipping on one app
→ Halfway, a finance app, is live on the App Store with a 5.0 rating
→ small teams replacing SaaS tools they were paying for every month with their own apps
If you try it today, one tip: in ChatGPT open Floot's app settings and choose "Allow all actions", otherwise the build pauses on every step.
What's the idea sitting in your ChatGPT history? Drop it below and I'll help you get it live.
Hey Product Hunt!
Yuj here, founder of Floot (YC S25).
Floot was already one of the most used ways to build apps over MCP, and it’s the top-ranked app builder in ChatGPT. Now it’s a native app in your ChatGPT sidebar, which means it can:
→ Show a live preview of your app right inside the chat
→ Pick up what you’ve been discussing, so you don’t have to re-explain or copy and paste
→ Send prompts to ChatGPT for you while it builds
Then you can:
→ Publish to a real link, plus the App Store and Google Play
→ Get a database, user logins and hosting built in
→ Build on your ChatGPT plan. We don’t charge for AI tokens, and you get 100 free build actions a day
To try it: install Floot from ChatGPT’s app directory, sign in, type @Floot and tell it what to build.
What’s the first app you’d build from your ChatGPT sidebar? Our team is in the comments all day.
@yujian Congrats yuj Building apps directly inside Chatgpt sounds really useful especially with live previews and built in hosting
@yujian @shivam_kushwaha16 Thanks Shivam! The live preview was the part we were most excited to get into the chat.
@yujian @shivam_kushwaha16 thank you Shivam!! would love to hear what you end up building 🙌
@yujian Congratulations @yujian I am seeking guidance on securing a dedicated integration-testing project created for our BallFanx application.
Project details
- Project name: BallFanx Integration Test Sandbox
- Project ID: `35d3de03-4cff-41f9-9bac-5eedb61bf9af`
- Current publication state: Unpublished
- Reported visibility: Public
The project contains a server-side integration-test endpoint at `POST /_api/integration/venueVerification`. This endpoint can execute database mutations within the sandbox's dedicated PostgreSQL database. It is intended exclusively for controlled integration testing.
Our read-only investigation confirmed that the project is unpublished but reports public visibility. We could not identify a documented, supported control for restricting access to this endpoint, making the project private, or disabling the endpoint without modifying application source.
The endpoint's fixed invocation header is not being treated as an authentication mechanism. We have not invoked the endpoint during this investigation.
Could you please clarify:
1. Does Floot support private or owner-only access for unpublished projects and their server-side API endpoints?
2. If so, what documented project or account setting controls that access?
3. Does unpublished status restrict access to `/_api/` endpoints, or can those endpoints remain reachable independently of the preview interface?
4. Is there a supported way to disable a single server-side endpoint or restrict it to authenticated project owners?
5. If no such control exists, what security approach does Floot recommend for a mutation-capable test endpoint?
6. Can Floot confirm whether the project's current visibility setting has implications for access to its server-side endpoints?
We have deliberately avoided probing the endpoint or making configuration changes while this remains unresolved.
We would appreciate documented instructions or confirmation of the supported approach. We will not resume integration testing until an appropriate access-control mechanism has been established.
Thank you for your assistance.
Best regards,
BallFanx Development Team
Congrats on the launch!
Building directly inside ChatGPT with a live preview is amazing. Can we also deploy apps from here?
@byalexai thank you Aleksandar! and yes — you publish straight from the chat and get a real live link, and you can push to the App Store and Google Play from there too
This is so tempting — I love not having to re-explain an app idea sitting in my ChatGPT history. What's a good first app to try for a first build?
@ms_harita_kanuri haha that's exactly why we built it! a good first one is something small you'd use yourself, like a booking page, a habit tracker or a simple client form. try "@Floot build a booking page for a yoga studio with a login" and you'll see the whole flow in a few minutes
@ms_harita_kanuri honestly anything! Just ask ChatGPT after you connect.
@ms_harita_kanuri Pick the idea you've already talked through most in ChatGPT, since Floot picks up that context. Small internal tools are a great first build.
@ms_harita_kanuri once you've picked one, come back and tell us how the first build went :) that re-explaining pain was basically the reason we made this
I just built a product‑marketing internal tool inside Claude using Floot. So cool! Congratulations to the launch team; I love it.
@abhishek_nellikkalaya ah love this! what does the tool do? you can open the same project from chatgpt now too
@abhishek_nellikkalaya Great to hear!
@abhishek_nellikkalaya Love that you built it in Claude first. Same Floot account works in ChatGPT too, so you can keep going from either one.
@abhishek_nellikkalaya this is the best kind of comment to wake up to on launch day, thank you Abhishek! 🙏
The part that would make or break this for me is picking up the earlier discussion in ChatGPT — if I've been going back and forth about an idea in a long thread, how much of that does Floot actually carry into the build? Does it use the whole thread's decisions, or mainly the prompt where I bring Floot in, and what happens if I change my mind partway through?
@jcbuilds great question JC. when you bring Floot in, ChatGPT passes along what you've been discussing, so you don't have to re-explain the idea or copy paste it. and if you change your mind partway, just say it in the chat and Floot updates the same project, since the project itself lives in Floot. @yujian can share more on exactly how much of the thread carries over
@jcbuilds honestly that's up to chatGPT which is pretty damn good at these. That's part of the magic - Floot gives chatGPT the power to build real websites and apps and you get to use the best capabilities of your agent instead of us forcing one on you.
@jcbuilds Great question. Since the project lives in Floot, you can keep changing your mind in the same chat and it keeps editing the same app, so nothing starts over.
@jcbuilds the long back-and-forth thread case is exactly what we tested on most. if you try it on one of yours I'd genuinely love to hear how it holds up
Hey PH, Surya from the Floot team 👋
Scroll back through your ChatGPT history and you'll find at least one app idea that never got built. A booking page, a tracker your team keeps asking for, a client portal you've been "about to make" for months.
That's the gap Floot fills. A few things people already run on Floot:
→ a camera rental company in Czechia runs its bookings, payments and shipping on one app
→ Halfway, a finance app, is live on the App Store with a 5.0 rating
→ small teams replacing SaaS tools they were paying for every month with their own apps
If you try it today, one tip: in ChatGPT open Floot's app settings and choose "Allow all actions", otherwise the build pauses on every step.
What's the idea sitting in your ChatGPT history? Drop it below and I'll help you get it live.
ooh I like the part about AI running on my ChatGPT plan. V cool! Congrats on this launch 🚀
@thisiskp_ thanks KP! yeah that one's a favorite. no extra ai bill, you build on the plan you already have
@thisiskp_ that’s the obvious benefit but even better you have an ai that knows about you build for you
@thisiskp_ Thanks KP! Using the plan you already pay for felt like the right model. No second AI bill.
@thisiskp_ thanks KP!! honestly the no-extra-AI-bill part was the hill we were willing to die on 😅