Floot in ChatGPT - Build and publish real apps without leaving ChatGPT

@yujian Congrats yuj Building apps directly inside Chatgpt sounds really useful especially with live previews and built in hosting

@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

@mehdidjabri thanks Mehdi! that was the whole idea what would you build first?

@mehdidjabri love to hear it!

@mehdidjabri Thanks Mehdi! Database, logins and hosting all live in the same place, so there's nothing to wire up.

@mehdidjabri thanks so much Mehdi, that means a lot on launch day 🙏

@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! 🙏

@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

@gauravthapa yes it is! The gpt sidebar even more awesome try it today on floot.com

@gauravthapa thank you!

@gauravthapa Thanks Gaurav! Hope you give it a spin from the sidebar.

@gauravthapa thanks Gaurav, appreciate the support! 🚀

@mituhin thanks! Let us know what you'll build with floot without leaving gpt

@mituhin Thanks!!

@mituhin Ha, pretty much! An app builder living inside your chat. Thanks Paul!

@mituhin haha "ChatGPT inside ChatGPT" is going to live in my head now 😄 thanks Paul!

@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 😅

@thomascdaly thanks Thomas! felt like the obvious place to be, that's where people already have their ideas

@thomascdaly thanks! I think that's the trend of software though. Plug into the agent instead of trying to be the agent.

@thomascdaly Appreciate it Thomas! Meeting people in the chat they already use just made sense.

@thomascdaly thank you Thomas! appreciate you taking a look 🙌

@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