[Staging] Hosting documentation

HostingWorkers / Pages

Host websites, APIs, and bots

Connect a Node repository. Ramuvo detects Vite, Next static export, Hono, and Wrangler apps, then deploys them to Workers or Pages with a public URL. Long-running bots stay on the process runner.

Current availability

On the Hosting tab, paste a Cloudflare API token and click Deploy to Cloudflare. Ramuvo builds the repo and publishes it to that account. Always-on process workers still use service.type: worker.

Automatic presets

Ramuvo will inspect package files without executing repository code, then suggest an editable preset.

Pages

Next.js

Detected from next in package.json

build: npm run build

start: npm run start

Pages

TanStack Start

Detected from @tanstack/react-start

build: npm run build

start: node .output/server/index.mjs

Workers

Hono

Detected from hono in package.json

build: npm run build

start: src/index.ts

API

NestJS

Detected from @nestjs/core

build: npm run build

start: node dist/main.js

Worker

Node bot

Detected from discord.js or worker preset

build: npm run build (optional)

start: npm run start

Configuration

Detection is a starting point. A repository-level ramuvo.yaml will override it.

version: 1
service:
  type: pages     # pages | workers | worker
  build: npm ci && npm run build
  output: dist
  # workers:
  # type: workers
  # main: src/index.ts

Service types

Pages

Static Vite, React, Astro, and Next export sites served on owner--slug.run.ramuvo.com.

Workers

Hono and Wrangler fetch handlers run in an isolated Dynamic Worker.

Process worker

Always-on Node process for Discord bots and consumers; no public port required.

Deploy lifecycle

1
Detect
Read manifests and suggest a preset.
2
Review
Confirm commands, port, health check, branch, and service type.
3
Build
Install and build in isolation while streaming logs.
4
Release
Pass health checks before routing traffic.
5
Operate
Restart, redeploy, inspect logs, or roll back.

Continue to logs and troubleshooting →