How source export works in Buildy

How Buildy keeps its hosted editor and preview separate from exportable project source, and which dependencies still need your review.

Source is useful only if it can move into a normal development workflow. Buildy keeps the hosted editor and preview separate from the project files you export.

What a paid plan can export

Export downloads the project for the selected target: Expo, Kotlin, SwiftUI, or React with Vite. The archive contains the source and project configuration; Buildy's hosted preview service is not added to it. GitHub sync provides another route into your own repository.

What can still be hosted

While you build, the editor, chat history, and preview compiler run on Buildy. A project can also depend on services you choose, such as Supabase or the optional Buildy AI Gateway. Those runtime dependencies do not disappear when source is exported, so review them as part of handoff.

A practical handoff

Run the project with its standard toolchain, review dependencies and environment variables, test a release build, and document any external service the app uses. Source access removes a Buildy-specific preview dependency; it does not make every third-party service portable automatically.