Robomap Hosting documentation

Overview

Robomap Hosting serves static files and SPAs under the ws.robomap.ai zone. Each customer project receives a subdomain such as your-project.ws.robomap.ai or can map a custom domain after verification.

Hosted pages can call Robomap backend services through the same-origin /api reverse proxy, which forwards requests to api.robomap.ai with cookies and authorization headers preserved.

Manage projects from the signed-in Web Services dashboard. Self-serve project creation is rolling out; until then, request a workspace after you sign up.

Domains & SSL

• Default hostnames use the *.ws.robomap.ai zone.
• Custom domains require a CNAME to the Robomap hosting endpoint provided for your project.
• TLS certificates are issued automatically once DNS verification succeeds.
• HTTP requests redirect to HTTPS.

Deployment

Upload a directory of static assets (HTML, CSS, JS, images, fonts). Supported layouts:

dist/
├── index.html
├── css/
├── js/
└── assets/

Single-page applications should include a fallback index.html for client-side routing. After you create an account, open the dashboard or contact support to provision your first project workspace.

API proxy

From any hosted page on ws.robomap.ai, relative API calls are proxied:

fetch('/api/ws/health')
  .then((r) => r.json())
  .then(console.log);

In local development, the gateway on port 8892 provides the same behaviour.

Platform endpoints

Public read-only endpoints available through the proxy:

Limits & fair use

• Maximum upload size per request follows the hosting edge nginx limit.
• Scrape endpoint accepts public URLs only; private networks are blocked.
• Static asset caching defaults to six months for fingerprinted files.
• Abuse or crypto-mining pages will be suspended without notice.