Publish your app
Publishing gives people a link to the experience you created. Your app’s data, models, access, and usage continue to matter after that first release.
Before publishing
Section titled “Before publishing”Try the main journey with representative data. Confirm who may see each record or file and who can change it. Check the current app status, account allowance, and any service configuration required by the experience. The live app keeps its own keys: if the app sends email or uses another outside service, add that service’s key in the app’s Settings for the live app as well, not only for the preview.
Your plan decides which apps can go live. Every plan builds and previews any kind of app. Free puts one one-page site live, with no expiry; putting an app with several pages, saved data, sign-in, email or AI live needs Go ($8 a month) or Pro ($25 a month). See Plans.
For an agent, review its source material, permitted actions, and the point where a person should check the result. For media or voice, run a small trial before inviting wider use.
Publish in Studio
Section titled “Publish in Studio”Use the publishing controls for the app and wait for the reported result. Copy the published link shown there. Open it separately and repeat the essential task; do not infer success only from the preview.
On Free and Go, a live app shows a small “Made with Exepad” link in the bottom-right corner of its pages. Pro removes it. A plan change updates the badge on your live apps.Keep it useful
Section titled “Keep it useful”Collect concrete feedback, make focused changes in Studio, and check each change in the preview before publishing again. Each publish replaces the live app. App reachability, access permission, and available usage are different conditions. Check the app’s actual status if a link stops working.