AppsinityAPPSINITY
Ads, streams and hosted pages

Studio webpages hosting

Studio can host a static webpage for your project at a subdomain of Appsinity's own domains, and can attach a custom domain to it.

Open Appsinity Studio

Choosing the subdomain

The address is validated against a narrow rule: it must be a subdomain of appsinity.com or appsinity.space.

  • A reserved list blocks administrative, store and platform names — you cannot claim www, api, studio or similar.
  • A name already taken by another project is refused.
  • Characters are limited to the normal subdomain alphabet; underscores are not valid host labels.
  • The route is a Studio API action, so a change takes effect on save rather than after review.
Watch out: Your page is served from an Appsinity domain, which means your content is publicly attributed to Appsinity. A page that misrepresents itself, or that the platform has to take down, damages the domain it is on.

Caching and freshness

This is the reason a page looks un-updated after a successful publish. Hard-refresh before you report it, and version asset URLs when you change CSS.

ContentCacheConsequence
Web build outputmax-age=86400A republish can appear unchanged for up to a day
Static assetsmax-age=3600An hour before a new asset is served
Store /assets sheetsFour hours at the CDN edgeStyle changes need a query-string version bump

Custom domains

A connect-domain action exists for attaching a domain you own. It is a DNS-dependent operation, so the practical checklist is: the zone must be reachable, the record must propagate, and the certificate must be issued before the page resolves.

Expect DNS to be the cause of any failure. There is no in-dashboard diagnostic beyond the response from the connect call.

Note: Changing a domain is a hosting operation with an external effect. If you are not the account owner, get the owner's confirmation before connecting one.

What a hosted page is good for

What it is not: a backend. Static hosting serves files; anything needing a database, authentication or a server process belongs on your own infrastructure.

  • A privacy policy on a stable URL, so a listing's Privacy row never breaks.
  • A support or contact page, which is otherwise the hardest thing to publish.
  • A marketing page for a game before the build exists.
  • A legal notice or terms page for your own brand.
  • A redirect page to your store listing.

Frequently asked questions

Is there a file-size or page-count limit?

The upload ceilings in Upload limits and file types apply. There is no separate quota for hosted pages.

Can I host a full web game this way?

Yes, and the web-game path is the better option because it gets the player frame, see Web game builds.

Can I remove a page?

The webpage routes support deletion. Take the page down before you unpublish the listing so the two do not disagree.

Need help?

Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]