Application Hosting

The flow above assumes you have an application to run. If what you have is a folder of built files, you do not need a repository, a runtime or an application of your own at all. Point the OSC CLI at the folder and it publishes the site and prints the live URL.

npx @osaas/cli@latest web publish mysite build/

This suits plain HTML, CSS and JavaScript, and the build output of Vite, Astro, React and Next.js static export. The command publishes to My Pages, so the site gets its own subdomain at https://mysite.pages.osaas.io/ with no bucket and no CDN setup, and it provisions no storage instance against your plan. Site names are global across OSC: 3 to 52 characters, lowercase letters, numbers and hyphens, starting and ending with a letter or digit. Running the command again re-publishes the site with the current contents of the folder.

If you already have an AI agent connected to OSC over MCP, it can do the same with create-my-page, upload-my-page-files and publish-my-page, with no shell involved. That path carries each file through the agent, so it suits small sites better than large framework builds; use the CLI for those. To replace a site and remove files that are no longer part of it, publish with prune: true and the complete file list.

One limit worth knowing before you choose: mapping a custom domain or putting a CDN in front of a My Pages site is not supported yet, so use the repository-based flow above if you need a clean domain at the root. If you need object-storage control instead, for example custom bucket names or per-object ACLs, publish-static-site creates a MinIO bucket and returns a URL ending in /index.html; its site name is 3 to 20 lowercase alphanumeric characters, and that path does provision one object-storage instance per site, which counts against the service limit on your plan.