Skip to content
Onplana Docs

Publishing apps, limits, and reporting abuse

All plans Admin

Onplana Maker lets you describe an app, have it built for you, and then publish it to a live URL at https://<name>.onplana.app. This page covers how publishing works, the fair-use limits that keep the shared hosting healthy, and the trust and safety flow: how anyone can report an abusive app, and what a takedown or appeal means if you own one.

Publish an app to a live URL

Section titled “Publish an app to a live URL”

Steps

  1. Build your app in the playground until it runs the way you want.
  2. Open the publish controls and choose Publish. Onplana builds the app to static files and serves them at https://<name>.onplana.app.
  3. Share the live URL. Re-publish any time to push a new revision; you can also roll back to a previous revision or unpublish to take it offline.

Publishing requires the Publish apps permission (Admin and above by default; configurable in your organization’s permission matrix).

Fair-use limits

Section titled “Fair-use limits”

Published apps run on shared Onplana hosting, so a few generous, mostly invisible limits keep one org from degrading the service for everyone. They scale by plan and almost never affect normal use:

PlanLive appsPublishes / dayMax app size
Free15 (2 per hour)30 MB
Starter315 (5 per hour)75 MB
Pro10100500 MB
Business254001 GB
Enterprise / Enterprise+100 / unlimitedunlimitedunlimited

A few notes:

  • App size is the built output, not your dependencies. The size cap measures the static files that actually get served at <name>.onplana.app (the result of the build), not node_modules or your source. A typical app is a few MB, so 30 MB is plenty of headroom.
  • Re-publishing the same app has a short cooldown (about a minute) so a stuck loop can’t hammer the publisher.
  • Rebuilding (the iterate-by-chat build step) has its own, far more generous throttle, so normal back-and-forth building is never the thing you hit. The AI token budget for the build step is separate, see “Understand your AI token budget.”

If you publish on the Free plan, your app carries a small “Made with Onplana” badge. Activating premium hosting on an app removes the badge; the hosting fee renews from your prepaid credit wallet, and if the wallet cannot cover a renewal there is a grace period before the app returns to the free tier (badge back, still live) or unpublishes. Publishing itself is never blocked by plan, only the number of live apps is capped. Onplana Maker workspaces get two free live-app slots, and premium-hosted apps never count against the slot cap.

Reporting an abusive app

Section titled “Reporting an abusive app”

Every published app carries a small Report this app link. Anyone who comes across an app that looks like phishing, malware, spam, or other abuse can use it to flag the app, no account required.

Steps

  1. On the live app, click Report this app (bottom corner).
  2. Choose a category (phishing, malware, spam, copyright, or other) and describe the problem.
  3. Submit. Reports are reviewed by Onplana’s trust and safety team.

Takedowns and appeals (for app owners)

Section titled “Takedowns and appeals (for app owners)”

If a report is upheld, an administrator can take the app down. A taken-down app stops serving at its onplana.app URL immediately, and:

  • You are notified (in-app and by email) with the reason.
  • The app cannot be re-published by you while it is taken down, this is different from unpublishing it yourself, which you can always reverse.
  • Your app’s revisions are retained, so a reinstated app can go live again without rebuilding.

If you believe a takedown was a mistake, you can appeal once per day from the app’s controls. An administrator reviews the appeal; the app stays down until they reinstate it.

FAQ

Section titled “FAQ”

Does publishing cost anything? No. Publishing is included on every plan. Your plan determines how many apps you can keep live at once and the fair-use limits above.

Can I stop search engines from indexing my published app? Published apps are set to not be indexed by default. If you want your app indexed, you can override that from inside your own app later.

Can my published app be embedded in another site? Yes. A published app is your own static content, so it is embeddable by default.

What happens to my app’s data if it is taken down? The app stops serving, but its stored revisions are kept so it can be reinstated on appeal without a rebuild.

Section titled “Related”