AppsReference

Address, domains and limits

Every app answers at <name>.waisoapps.app — a domain of its own, separate from waiso.dev — and, on paid plans, at a domain of yours too.

6 min readBefore this: Your first app
What you will learn
  • Point your own domain at an app
  • Know each plan’s limits for apps
  • Publish apps on a self-hosted install

Use your domain

  1. Add it

    App → Domains → type www.yoursite.com → Add domain.

  2. Create the record

    At your domain’s DNS provider, create the CNAME the screen shows (name www, value custom.waisoapps.app).

  3. Wait for Active

    The certificate is issued by itself; the status moves from Waiting to Active, usually within minutes. Check now asks again.

Plans

Per planFreeProTeamBusiness
Apps1320Unlimited
Space50 MB1 GB5 GB20 GB
Versions kept per app52050100
Largest file5 MB25 MB25 MB50 MB
Your own domain—YesYesYes
“Made with Waiso” stripYes———

Space counts each distinct file once across all your apps and versions. A self-hosted install has no limits. If a plan changes, apps keep serving; publishing waits until they fit again.

Apps are kept apart

Weddingcasamento.waisoapps.app
Publish
CodeHistoryDomainsSettings
www.brunaetalisson.com.brWaiting
Create this record at your domain’s DNS provider:Check now
convite.brunaetalisson.com.brActive
Certificate issued · answering over HTTPS
An app’s Domains tab: its own address, a domain waiting for its record and one already active.
  • Each app has its own address, so one app cannot read another’s storage, cookies or pages.
  • Apps live on a domain separate from waiso.dev: nothing an app runs can reach your Waiso session.
  • On Free, the “Made with Waiso” strip belongs to Waiso’s page around the app; the app’s own code cannot hide it.

Report an app

Anyone can report an app that pretends to be someone else, spreads malware or breaks the law at waiso.dev/report-app (the Free strip links there). Reported apps are reviewed and may be taken down; their owner is told why.

On your own server

Choose a domain for apps, point a wildcard DNS record (*.apps.example.com) at the server, give it HTTPS in your reverse proxy, and set:

Shell.env
# .env of a self-hosted install
WAISO_APPS_DOMAIN=apps.example.com
# optional: your own S3 for app files (else a volume)
#WAISO_SITES_S3_BUCKET=waiso-apps
#WAISO_SITES_S3_REGION=us-east-1
#WAISO_SITES_S3_ACCESS_KEY_ID=...
#WAISO_SITES_S3_SECRET_ACCESS_KEY=...

Without WAISO_APPS_DOMAIN, apps can be made, previewed and downloaded, but not published — the Publish button says what to set. On Kubernetes, set apps.domain in the chart and keep app files in your S3.

Related topics