version: "1.0.1" name: cloud-hosting-expert description: "Expert guide for deploying SaaS applications with multiple entry points on modern edge and serverless platforms like Vercel and Cloudflare / Panduan ahli untuk mendeploy aplikasi SaaS dengan multiple entry points di platform edge dan serverless modern seperti Vercel dan Cloudflare." author: "Roedy Rustam"

Cloud Hosting Expert (2026 Edition)

English | Bahasa Indonesia

<a name="english"></a>

English

Orchestration & Integration

Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.

Description

Expert guide for deploying SaaS applications and their multiple entry points (landing page, app, super admin subdomain) on modern edge and serverless platforms. Covers Vercel, Cloudflare Workers & Pages, Railway, Fly.io, and Cloudflare Workers AI for AI-powered edge workloads.

Trigger Conditions

• Deploying a Next.js, Hono, or Astro application to Vercel, Cloudflare, or Railway.
• Configuring custom domains and subdomain routing (e.g., app.domain.com, admin.domain.com).
• Setting up Edge Middleware for multi-tenant tenant identification.
• Deploying AI inference workloads to Cloudflare Workers AI.
• Deploying long-running backend services to Railway or Fly.io.
• Implementing CDN caching strategies for SaaS applications.

Platform Selection Guide (2026)

Multi-Entry Point Deployment Architecture

For SaaS applications, separate deployments for each entry point:

myapp.com         → Vercel (Marketing/Landing — Next.js static)
app.myapp.com     → Vercel (SaaS App — Next.js dynamic)
admin.myapp.com   → Vercel (Super Admin — Next.js, restricted access)
api.myapp.com     → Railway/Fly.io (Backend API — long-running)
cdn.myapp.com     → Cloudflare R2 (Static assets & user uploads)

Vercel — Next.js Deployment

Multi-Domain Configuration

// vercel.json
{
  "rewrites": [
    { "source": "/(.*)", "destination": "/$1" }
  ],
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        { "key": "X-Content-Type-Options", "value": "nosniff" },
        { "key": "X-Frame-Options", "value": "DENY" },
        { "key": "Strict-Transport-Security", "value": "max-age=63072000; includeSubDomains; preload" }
      ]
    }
  ]
}

Edge Middleware for Tenant Routing

// middleware.ts — runs at the edge before every request
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';
export function middleware(request: NextRequest) {
  const hostname = request.headers.get('host') ?? '';
  const subdomain = hostname.split('.')[0];
  // Route admin subdomain — enforce strict auth check
  if (subdomain === 'admin') {
    const adminToken = request.cookies.get('admin-session')?.value;
    if (!adminToken) {
      return NextResponse.redirect(new URL('/login', request.url));
    }
  }
  // Identify tenant from subdomain for multi-tenant apps
  if (subdomain !== 'www' && subdomain !== 'app' && subdomain !== 'admin') {
    const response = NextResponse.next();
    response.headers.set('x-tenant-slug', subdomain);
    return response;
  }
  return NextResponse.next();
}
export const config = {
  matcher: ['/((?!_next/static|_next/image|favicon.ico).*)'],
};

Cloudflare Workers — Edge APIs

Hono on Cloudflare Workers

// src/index.ts
import { Hono } from 'hono';
import { cors } from 'hono/cors';
import { rateLimit } from '@/middleware/rateLimit';
const app = new Hono<{ Bindings: Env }>();
app.use('*', cors({ origin: ['https://app.myapp.com'] }));
app.use('/api/*', rateLimit(100)); // 100 req/min via KV
app.get('/api/health', (c) => c.json({ status: 'ok', region: c.env.CF_REGION }));
app.get('/api/data', async (c) => {
  // Access Cloudflare D1 (SQLite at edge)
  const result = await c.env.DB.prepare('SELECT * FROM items LIMIT 20').all();
  return c.json(result.results);
});
export default app;

Cloudflare Workers AI (On-Device Edge Inference)

Run AI models directly at Cloudflare's edge — no external API calls needed:

export default {
  async fetch(request: Request, env: Env) {
    const { text } = await request.json() as { text: string };
    // Run Llama 3 or Mistral at the edge
    const response = await env.AI.run('@cf/meta/llama-3.1-8b-instruct', {
      messages: [
        { role: 'system', content: 'You are a helpful assistant.' },
        { role: 'user', content: text }
      ],
      stream: true,
    });
    return new Response(response, {
      headers: { 'Content-Type': 'text/event-stream' }
    });
  }
};

Available models on Workers AI:

• @cf/meta/llama-3.1-8b-instruct — Fast general-purpose chat
• @cf/mistral/mistral-7b-instruct-v0.2 — Fast instruction model
• @cf/baai/bge-small-en-v1.5 — Text embedding (for RAG)
• @cf/stabilityai/stable-diffusion-xl-base-1.0 — Image generation

Railway — Bun / Node.js Long-Running Services

# Dockerfile for Railway (Bun runtime)
FROM oven/bun:1.2-alpine
WORKDIR /app
COPY package.json bun.lockb ./
RUN bun install --frozen-lockfile
COPY . .
EXPOSE 3000
CMD ["bun", "run", "src/server.ts"]

# railway.toml
[build]
builder = "DOCKERFILE"
 
[deploy]
startCommand = "bun run src/server.ts"
healthcheckPath = "/health"
healthcheckTimeout = 10
restartPolicyType = "ON_FAILURE"

Environment Variables & Secrets Management

• Vercel: Use Vercel's built-in secrets panel — supports preview/production scoping.
• Cloudflare: Use wrangler secret put SECRET_NAME or the dashboard.
• Railway: Use Railway's variable groups for shared secrets across services.
• Never commit .env files — use .env.example as documentation only.

Caching Strategy

// Vercel: Cache API responses at the edge
export async function GET() {
  const data = await fetchData();
  return Response.json(data, {
    headers: {
      'Cache-Control': 'public, s-maxage=60, stale-while-revalidate=300',
    }
  });
}
// Cloudflare: Use Cache API
const cache = caches.default;
const cached = await cache.match(request);
if (cached) return cached;

<a name="bahasa-indonesia"></a>

Bahasa Indonesia

Integrasi Orkestrasi

Terhubung dan mengorkestrasi skill domain yang relevan seperti brainstorming, zero-to-prod-orchestrator, dan project-context-mapper untuk memastikan eksekusi yang kohesif.

Deskripsi

Panduan ahli untuk men-deploy aplikasi SaaS dan multiple entry points-nya (landing page, aplikasi, subdomain super admin) di platform edge dan serverless modern. Mencakup Vercel, Cloudflare Workers & Pages, Railway, Fly.io, dan Cloudflare Workers AI untuk workload AI di edge.

Kondisi Pemicu

• Men-deploy aplikasi Next.js, Hono, atau Astro ke Vercel, Cloudflare, atau Railway.
• Mengonfigurasi domain kustom dan routing subdomain.
• Menyiapkan Edge Middleware untuk identifikasi tenant multi-tenant.
• Men-deploy workload inferensi AI ke Cloudflare Workers AI.
• Men-deploy layanan backend long-running ke Railway atau Fly.io.

Panduan Pemilihan Platform (2026)

Pilih Vercel untuk Next.js dan aplikasi full-stack. Cloudflare Workers untuk API dengan latensi ultra-rendah dan logika edge. Railway/Fly.io untuk layanan backend long-running (Node.js, Bun, Go, Python). Cloudflare R2 untuk penyimpanan objek (pengganti S3 yang lebih murah).

Arsitektur Deployment Multi-Entry Point

Pisahkan deployment untuk setiap entry point SaaS:

• domain.com → Landing page (Vercel, statis)
• app.domain.com → Aplikasi SaaS (Vercel, dinamis)
• admin.domain.com → Dashboard Super Admin (Vercel, akses terbatas)
• api.domain.com → Backend API (Railway/Fly.io, long-running)
• cdn.domain.com → Aset statis & upload pengguna (Cloudflare R2)

Edge Middleware (Vercel)

Gunakan middleware.ts untuk routing tenant berdasarkan subdomain dan perlindungan rute admin — berjalan di edge sebelum setiap permintaan.

Cloudflare Workers AI

Jalankan model AI (Llama 3.1, Mistral, BGE embedding) langsung di edge Cloudflare — tanpa panggilan API eksternal, latensi sangat rendah, dan ditagih per token.

Railway — Layanan Long-Running

Gunakan Railway untuk backend yang tidak cocok dengan model serverless (WebSocket, background job, koneksi database persisten). Mendukung Bun, Node.js, Go, Python, Rust dengan deployment otomatis dari GitHub.

Manajemen Environment Variable & Secret

Gunakan panel secret bawaan di masing-masing platform. Jangan pernah commit file .env — gunakan .env.example sebagai dokumentasi saja.