Skip to main content
superun makes it easy to publish your project and share it with teammates or users. You can iterate on the live version anytime and connect a custom domain.
Before publishing, run a quick security check to avoid leaking sensitive data. Publish may also suggest a Security scan (continue publishing / go to scan / don’t remind again—as in product).

​
Demo and Build dual versions

The same project can have both a Build version and a Demo version:
  • Build： connects to real capabilities and data for production delivery and go-live.
  • Demo： can be published, shared, or unpublished independently — suited for external demos, acceptance, or marketplace previews. You can also one-click convert the current production app into a Demo (backend, plugins, and external services replaced with local mocks).
Switch Build / Demo from the history panel (the version identity bar above the input is removed). Create a Demo with New demo (formerly “Split demo”). You can switch while generation is running; when the other side is generating, the system confirms and stops the current run to avoid cross-version bleed. Run now reads plans separately for Build and Demo. If listing detects that Build is ahead of Demo, it shows a tip and a New demo entry so you can sync Demo before listing. The Operations publish panel supports publish, share, and unpublish for both Demo and Build. Demo daily-fee copy is shown in product (e.g. Demo cloud service fee — cloud storage). For marketplace listing and Demo prep, see App marketplace.

​
How to publish

  1. In your project, go to Operations
  2. Open the Publish tab (confirm whether you are publishing Build or Demo)
  3. Click Publish to start publishing your project
  4. Wait for publishing to finish
  5. After publish, share your project through the available channels
Publish tab under Operations Multi-channel sharing after publish

​
Private publish and search indexing

When publishing, you can choose Private publish. That sets no-index so search engines are asked not to index the site in search results.
Private publish is not access control. Anyone with the link may still open the site; if content should be limited to specific users, configure login, authentication, and authorization separately.

​
Independent test environment after go-live

After publish, verify login, database, or third-party integrations via Build → Skill Library → superun Cloud → Test environment (limited-time free, as in product). See Independent test environment.

​
Cloud resources before publish

While a project is still in development and not published, it uses temporary cloud resources. If it sits unused, those resources are reclaimed, and backend features such as login verification codes stop working until you open the project again and resources are prepared. After you publish, the project gets fixed resources. Inactivity no longer reclaims them.

​
FAQ and troubleshooting

  • Publish errors: Often caused by build issues — ask the AI to investigate and fix first.

Publish App

Cloud-build the project as an Android / HarmonyOS / iOS installer and test it on a phone.

superun website

Visit the site to learn more about features and examples.