# Managed Cloud Hosting Standard

ClientOS Studio does not require physical servers, office hardware, or client-owned rack equipment to host production websites and apps.

**Default rule:** production hosting runs on managed cloud infrastructure. The client owns the domain and critical business accounts. ClientOS Studio operates deployments, monitoring, updates, and support.

## Standard Stack

- DNS, CDN, SSL, security, and edge hosting: Cloudflare.
- Static websites: Cloudflare Pages or Vercel.
- React, Next.js, and app frontends: Vercel, Cloudflare Pages, or an equivalent managed platform.
- Serverless/API logic: Cloudflare Workers, Vercel functions, Fly.io, Render, or another managed runtime chosen for the app.
- Databases: managed Postgres through Supabase, Neon, Railway, or a comparable provider.
- Files, images, and video: Cloudflare R2, S3-compatible storage, or managed platform storage.
- Monitoring: uptime checks, platform logs, error tracking, and recurring review.

## What The Client Owns

- Domain registration and registrar login.
- DNS zone access, either directly or through an invited role.
- Brand assets, website content, store listings, customer data, and analytics.
- Cloud accounts for high-risk apps, regulated workflows, sensitive portals, or projects where long-term infrastructure control must remain with the client.

## What ClientOS Studio Operates

- DNS setup and launch records.
- Deploy pipelines from Git.
- SSL/TLS configuration.
- Environment variables and secrets setup.
- Database migrations and backups where applicable.
- Uptime checks, error review, and rollback planning.
- Monthly updates, security patches, and minor improvements under a care plan.

## Hosting Models

### Studio-Managed Hosting

Best for brochure sites, landing pages, small business sites, and low-risk marketing experiences.

ClientOS Studio can host and maintain the project under a studio-managed platform account while the client keeps domain ownership. This keeps launch simple and gives the client one support contact.

### Client-Owned Cloud Hosting

Best for portals, apps with user accounts, paid products, health/legal/financial workflows, internal tools, or anything with meaningful business data.

The client creates the Cloudflare, Vercel, Supabase, or equivalent account and invites ClientOS Studio. This keeps long-term ownership and risk with the business while still letting us handle the technical work.

## What We Avoid

- Hosting production client sites from a Mac, office PC, or home internet connection.
- Running unmanaged physical servers for ordinary business websites.
- Building fragile one-off server setups without backups, monitoring, and rollback.
- Keeping client domains trapped in a studio-owned registrar account.

## Client Launch Checklist

- Domain ownership confirmed.
- DNS provider selected.
- Hosting model selected: studio-managed or client-owned cloud.
- Required platform accounts created.
- ClientOS Studio invited with appropriate access.
- Git deployment pipeline connected.
- Environment variables and secrets configured.
- SSL/TLS active.
- Backup and rollback path documented.
- Uptime check enabled.
- Care plan scope confirmed.