By Glassly

5 September 2026 · 4 min read · Updated 8 September 2026

Do I own the source code? Yes. Here is exactly what you get.

You own the generated app and can export its Expo source project free. What the ZIP includes, what needs a separate backup, and how a developer runs it.

A set of keys resting in an open hand
Photograph via Unsplash

Yes. You own your prompts and generated apps, and Glassly claims no ownership of the code or content generated for you. You can download the source project free on every plan, including apps created from free templates. This is set out in our terms; open-source dependencies keep their own licences.

How to download the project

Open your app's settings, find Your code and choose Download my project. Export uses the last complete generated version and checks it against the build gate. If no complete, passing version is available, finish or fix that version before exporting. Passing this check is not a substitute for testing the app's behaviour.

What is in the ZIP

  • The Expo (React Native) app: root component, screens, navigation, shared components and helpers.
  • The app icon and splash assets, native configuration, package list and lockfile.
  • Environment settings for the connected Supabase URL and public key, with placeholders for unresolved values.
  • Database schema and available server functions when the backend can be read.
  • A README with run instructions and warnings about anything that could not be included.

What needs a separate backup or setup

The database schema describes tables, policies and functions; it is not a copy of live records. User accounts, messages, bookings and uploaded user files are not included as a data backup. Secret credentials, platform build machinery and signing keys are also outside this source download. Some native integrations need client configuration files or credentials added before rebuilding.

If you are moving away from Glassly, connect your own Supabase project and arrange data and file backups there. Check the README's warnings, deploy the required server functions and configure external services. Keeping only the source ZIP does not preserve a running service or its users' content.

How a developer runs it

Follow the README to install dependencies with npm install and start the project with npx expo start. Native builds use Expo's build workflow, either locally with the relevant iOS or Android toolchain or through a cloud build service. The generated app uses native dependencies, so the Expo Go companion app is not a substitute for its native build. Test the exported app and its backend before a handover.

Project ownership and account ownership

Downloading code is different from moving a project between Glassly accounts. There is no self-service project transfer today. For client work, agree who controls the builder account, backend, store listings and future maintenance. See the client handover guide and pricing for the costs that may continue after a source export.

Quick answers

Do I own the source code of an app built with Glassly?
Yes. The terms state that you own your prompts and generated apps and that Glassly claims no ownership of the code. Open-source dependencies retain their own licences.
Can I export the source code for free?
Yes, on every plan. Use Download my project in the app settings. A complete version that passes the export build gate is required; read the included README for setup instructions and missing items.
Does the exported app run without Glassly?
The export is an Expo source project that a developer can run and build with the required tools and services configured. For independence from the managed starter backend, use your own Supabase project and configure the app and integrations for it.
Does the export include my live database and user files?
No. The source download can include database schema and server functions, but it is not a backup of live records, user accounts or uploaded user files. Back those up separately. Secret credentials and signing keys also need separate configuration.