YourHost is a service provided by CLOUDPAGE LLC.

Create it with your AI, and YourHost gives it a home so you can publish it.

From your project folder to an HTTPS address. You approve the project in the portal; your AI can publish if it has access to your files and a terminal.

First: a new website or an update to your existing one?

Tell your AI which website to change and share this guide. Reading it grants neither account access nor permission to publish.

My website does not exist yet
Prepare the complete delivery, check the files and authorize creating the first website in the portal.See first publication
My website already exists, even if created with a ZIP
Identify its address and keep that same website. When connecting another folder for the first time, approve the existing website: do not create a duplicate.See updating the same website

Choose one workflow; do not run both in sequence. An AI without files and a terminal can guide you, but cannot claim publication. Asking only for a review does not authorize uploading files or changing your website.

Share official instructions with your AI

Read plain-text instructions without signing in
Share official instructions with your AI
https://yourhost.us/en/guia/ia.md

Index for AI assistants

Publish from your project with your AI.

Recommended workflow with CLI 0.3.3 and Node.js 22 or later. A chat without files or a terminal can help prepare a delivery, but cannot execute publication. You can also run the commands yourself.

  1. Prepare your account

    Create your account, confirm your email and check hosting access in My dashboard. If activation is pending, check its status: do not buy the plan again.

  2. Approve this project

    Run publish in the folder. The first time it shows a URL and code. Open the portal, sign in and confirm the code, project and website: create your first website or approve an existing one. Permission is scoped to that project and website; do not copy tokens or passwords into chat.

    Approve a project in the portal
  3. Publish and check

    After approval, the CLI transfers the project and follows the result. Share the HTTPS address only after publication is confirmed. To update, repeat publish from the same folder and keep the same website.

Ask your AI · copy this message

Install CLI 0.3.3
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz

First publication: run each step once
yourhost check .
yourhost publish . --name "My project"
yourhost publish-status . --wait

Resume the same submission

CLI 0.3.3 and the JavaScript portal transfer blocks of up to 1 MiB. Query without publishing using yourhost publish-status .: it only makes GET requests for the submission saved in that folder; add --wait to follow it. It does not automatically query a later repair made by support. While a submission is pending, repeat yourhost publish . in the same folder: it recovers snapshot and UUID even if sources changed. After a confirmed terminal result, identical sources only check status; different sources create an update for the same website using normal publish, including when the previous result was failed. Do not use --retry to incorporate changes. yourhost publish . --retry is reserved for a confirmed transient failure and identical content; it requires confirmed failed, complete transfer and published other than true. It creates a new UUID: it is not a query or a format correction. For PUBLICATION_FAILED without a specific cause, consult support before repeating that content. yourhost publish . --reconnect only renews expired/revoked access with a confirmed terminal result and approval of the same website; it does not publish changes or resolve uncertainty. Combine --reconnect --retry only when both conditions hold. Use yourhost publish . --recover-lock only if the CLI verifies that the recorded process ID (PID) no longer exists. Legacy locks without the new process metadata are not removed automatically. Never delete receipts to start another submission. If the portal closes before transfer completes, return with the same file. Only durable server acceptance lets work continue without the window. --no-wait is an alternative that skips waiting for the build: it waits for approval and upload; do not run it as a second submission. A wait ending confirms neither failure nor publication.

check inspects local files: it does not authenticate, upload or run scripts and does not guarantee server compatibility or admission. CLI 0.3.3 check/publish accepts up to 2048 files in its folder, even though some portal ZIP formats accept 4096. check uses the normal 20 MiB ZIP limit; publish negotiates the normal 20 MiB or up to 128 MiB with Owner permission, without expanding format limits or quotas. HTML accepts local MP4/WebM and up to 10 MiB per file. HTML, Node.js/Next.js, Vite and WordPress backups require compatibility. Generic DB, SMTP, secrets, persistence and egress are not available. Exclude .env files (including examples), keys, wp-config.php and pb_data from the publishable copy; preserve originals.

SOURCE_UNSUPPORTED calls for reviewing the delivery, not blindly converting it. Do not remove package.json, lockfiles, backend code or requirements to force HTML, or replace an application with a mockup. A static export is appropriate only if it actually exists, preserves the agreed functionality and you authorize that change.

Prefer uploading a ZIP? See the portal alternative

1. Open your space.

All you need is an email address and a strong password.

  1. 1.Create your account

    Enter your name, email and password.

  2. 2.Confirm your email

    Open our message and follow the link.

  3. 3.Open My dashboard

    Find your account, subscription and websites here.

2. Choose your web hosting plan.

To publish a website, manage these plans under View my subscription. This table is not a standalone email catalogue.

Free

$0

USD · for 3 months

1 website

1 GB

Basic

$10

USD · per month

5 websites

10 GB

Professional

$20

USD · per month

30 websites

50 GB

Enterprise

$100

USD · per month

Unlimited websites

200 GB

Free: three months at no charge. No minimum term or automatic charge at expiry.

Read the terms

Find your way around.

Visual example · not your account data

My dashboard shows the next step: confirm email, activate hosting or publish. The portal checks your current plan or access grant; registration does not grant hosting. If you already subscribed and activation is pending, check the status or contact support: do not buy the plan again.

3. Prepare a clean delivery.

First, keep a copy of the project on your own computer.

Inside the ZIP

  • Your website files
  • Images and stylesheets
  • Your workflow's file layout

Outside the ZIP

  • .env and passwords
  • node_modules
  • Docker and temporary files
ZIP limits
ZIP admission
Standard: 20 MiB. Authorized Owner: up to 128 MiB; detected format limits still apply.
Without JavaScript
20 MiB, including Owner. Larger ZIP uploads require JavaScript.
HTML / Vite output
50 MiB · 512 files · 10 MiB per file; local MP4/WebM supported
Project source / WP
50 MiB · 4096 files · 20 MiB per file
Owner project source
Only for the authorized profile: 128 MiB total and per file. Physical quotas and all other requirements still apply.

Alternative: name your website and upload a ZIP.

Under My websites, creating a website requires a name and a ZIP containing your files. You do not choose a technology: YourHost inspects the files to detect HTML, Next.js/Node.js, Vite or a compatible WordPress backup. This is not a universal installer: missing requirements or a format that is not enabled block publication and are explained in the portal.

  1. 1.Name your website

    Enter a name and check the suggested address.

  2. 2.Attach your ZIP

    The file is required. This form does not create example pages or empty WordPress sites.

  3. 3.Create and review

    Select Create and publish. Receiving files and reserving an address do not mean your website is online yet.

  4. 4.Check the result

    Wait for Online and open Visit site. If a requirement is missing, fix it from the same website without creating another.

HTMLA page ready to upload

HTML, CSS and images, or an already compiled export.

website.zip
├─ index.html
├─ styles.css
└─ images/
Visual example · not your account data

Create a website

Website name
my-website
Required ZIP file
my-website.zip
Create and publish

Automatic detection: Static website (HTML)

  1. 1.Prepare index.html

    Place it at the root alongside the website assets.

  2. 2.Name your website

    Check the address shown in the dashboard.

  3. 3.Attach your ZIP

    The portal detects HTML content automatically.

  4. 4.Create and publish

    Wait for Online and open Visit site.

How to check that it worked

Your HTTPS address opens the website and its images.

A ZIP containing your files is required; the form does not generate an example page.

Next.js / Node.jsAn application with a server

Upload your code and its npm configuration.

application.zip
├─ package.json
├─ package-lock.json
├─ app/ or server.js
└─ public/
Visual example · not your account data

Create a website

Website name
my-website
Required ZIP file
my-website.zip
Create and publish

Automatic detection: Project (Next.js, Node.js or Vite)

  1. 1.Review requirements

    Check the scripts and what your application needs.

  2. 2.Name your website

    Check the suggested subdomain.

  3. 3.Upload the project

    Include package.json and package-lock.json; the format is detected automatically.

  4. 4.Create and publish

    Use Refresh status, then visit the website.

How to check that it worked

Check the home page and your application routes.

This profile has no DB, persistent disk or outgoing server network.

Vite / ReactA frontend that builds

Deliver Vite source; we publish its dist/ output.

frontend.zip
├─ package.json
├─ package-lock.json
├─ index.html
└─ src/
Visual example · not your account data

Create a website

Website name
my-website
Required ZIP file
my-website.zip
Create and publish

Automatic detection: Project (Next.js, Node.js or Vite)

  1. 1.Prepare your project

    Vite is detected automatically; you do not need to select it.

  2. 2.Check build

    It must produce the dist/ folder.

  3. 3.Upload and publish

    Enter a name and attach the code and npm lockfile in a ZIP.

  4. 4.Check your routes

    Also open an internal SPA route directly.

How to check that it worked

Your website, images and internal routes respond over HTTPS.

Already have compiled dist/? Upload its contents as HTML.

WordPressImport a WordPress backup

Upload a ZIP with a compatible database backup and wp-content/.

backup.zip
├─ database.sql
└─ wp-content/
   ├─ uploads/
   ├─ plugins/
   └─ themes/
Visual example · not your account data

Create a website

Website name
my-website
Required ZIP file
backup.zip
Create and publish

Automatic detection: WordPress

  1. 1.Prepare your backup

    Include database.sql and wp-content/.

  2. 2.Name and attach

    The ZIP is required; WordPress is detected from its contents.

  3. 3.Create and publish

    Wait for the Online confirmation.

  4. 4.Edit your content

    Open WordPress admin under Manage your website.

How to check that it worked

Check pages, images and access to /wp-admin/.

Plugins must be compatible: PHP has no outgoing network or online updates.

Improve the same website.

Your address stays the same. There is no need to create another website.

Update from your connected project

Save new files in the same bound publishable folder. Keep the website, permission and receipts. Once the previous submission has a confirmed terminal result, review the changes and authorize a normal publication; a valid permission does not need reconnecting.

publish and ZIP need a complete delivery of the updated project, not only changed files. Omitted source files are removed from the new version. Preserve required assets and functionality; prepare a publishable copy without secrets, without deleting originals. The advanced delta has a different contract.

New sources: check and publish once
yourhost check .
yourhost publish .

Different sources and a finished previous submission
Use normal publish, without --retry or --reconnect. Keep the folder and website: a new UUID is created for that version. After confirmed success, open HTTPS and check the content.
Pending submission or uncertain result
Query yourhost publish-status .; add --wait to follow it. Resuming publish preserves snapshot and UUID even if you edited files. It does not create the new version yet. Do not delete locks or receipts to force another submission.
Repeat exactly the failed content
--retry is only for a confirmed transient failure. PUBLICATION_FAILED without a specific cause needs support before repeating that content; keep requestId, uploadId and attemptId. Received files do not mean publication.
Expired or revoked permission
--reconnect requires a confirmed terminal result and approval of the same website. It renews access, not publication. Do not use it to resolve an old failed result with a valid credential.

Signing in does not replace hosting or website permission, or remove quotas and validation. For a new rejection, keep its code and UUID and ask support; do not create another website or buy another plan to bypass it. Never send passwords or tokens.

Ask your AI to update without duplicating

Alternative: upload a ZIP to the same website

ZIP · v1ZIP · v2https://my-website.yourhost.us
  1. 1.Find your website

    Open My websites.

  2. 2.Upload the new version

    Select Upload ZIP file.

  3. 3.Check the status

    Wait without repeating the upload.

  4. 4.Visit and check

    Open the same HTTPS address.

  1. Preparing

    We are checking your files.

  2. Publishing

    We are confirming the new version.

  3. Online

    Open your website and check its content.

  4. Needs attention

    Read the error and fix it from this same website.

Advanced: update an eligible source delta.

This advanced workflow compares selected files with an already published website and prepares a source delta plan over HTTPS. It does not replace publish for first publication. Check eligibility before preparing a plan.

The advanced example in this guide concerns an active website with the cloudpage-pocketbase-v1 persistent profile, which requires Owner authorization and an available binding. The server determines eligibility for each website: continue only with eligible: true. Do not infer access from using Next.js, Node.js or Vite. Persistent data and configuration have their own procedure. Update my website: CLI or ZIP

Set up access once

  1. Open the right website

    Under My websites, find your website and select Domains and publishing tools. Check its address on Manage your website.

  2. Create a publishing key

    Find New key, give it a recognizable name and leave domain management disabled. Save the key when it appears: it is shown only once.

  3. Prepare your terminal

    With Node.js 22 or later, install the CLI and set YOURHOST_SITE_TOKEN in your computer's environment. The CLI is YourHost's publishing tool.

Install the YourHost tool
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz

Set the key in your terminal

Choose your terminal, run the block, then enter or paste your key when prompted. Input stays hidden and is not added to command history. Keep this terminal open to publish; if you close it, set the variable again.

Windows · PowerShell
$key = Read-Host "Website key" -AsSecureString
$env:YOURHOST_SITE_TOKEN = [System.Net.NetworkCredential]::new("", $key).Password
Remove-Variable key

macOS · zsh
read -rs 'YOURHOST_SITE_TOKEN?Website key: '
export YOURHOST_SITE_TOKEN
printf '\n'

Linux · Bash
read -rs -p "Website key: " YOURHOST_SITE_TOKEN
export YOURHOST_SITE_TOKEN
printf '\n'

The key only authorizes publishing to that website, expires after 90 days and can be revoked in the portal. Do not paste it into a shared command, an AI conversation or files you will publish. Administrative keys and management SSH access are not needed.

  1. Save and review your changes

    Open a terminal in your project folder. Check that the local version works and choose the files to update.

  2. Prepare a plan

    The command compares your files with the remote version and saves changes in a plan. It does not publish yet. Replace the example path with one that exists in your project; repeat --files to add more files.

    Prepare a plan
    yourhost source plan . --files src/app/page.tsx

  3. Find the plan code

    Look for the id field in the response. This is the code used to publish and check the result. The requestId field identifies the submission; do not use it as the plan code.

    Visual example · not your account data · How to read the plan response
    idPlan code · use this value
    PLAN_ID
    requestIdSubmission code · not used with apply
    REQUEST_ID

    The codes shown here are examples. Copy the real id value from your own response, without quotation marks.

  4. Publish and check

    Replace PLAN_ID with the real id value. When publication finishes, open the same website address and review the pages you changed.

    Publish and check
    yourhost source apply PLAN_ID --wait

Up to 1 MiB and 128 files per change, under src/, messages/ or public/. The plan and its file snapshot expire after 24 hours. Omitted files are preserved. This channel does not install a new application or change dependencies, private configuration, databases or PocketBase hooks/schema.

Did the terminal close or the wait end?

An accepted publication can continue after you close the terminal. Check the same plan; if the response asks you to resume, use resume with that same code. Do not create another publication just to find out what happened.

Check the status
yourhost source status PLAN_ID

Did the terminal close or the wait end?
yourhost source resume PLAN_ID --wait

unchanged means the selected files already match the remote version. No extra publication is created. If a plan expired, check its status first, then prepare a new one with your current changes.

Does your AI work inside your project?

Ask for support from your project with your AI.

Your AI with files and a terminal can submit a request to support@yourhost.us using CLI 0.3.3 and Node.js 22 or later. Creating SMTP-INTEGRATION.md on your computer sends nothing.

Install CLI 0.3.3
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz

  1. Prepare and review the request

    Describe the issue, expected result and reproduction steps in SMTP-INTEGRATION.md. Do not include passwords, tokens, keys or other secrets. Review the content and explicitly authorize submission.

  2. Send one identifiable request

    If YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Generate one real UUID and save it with the exact subject and file before submission; replace <UUID>, do not run it literally.

    Generate this request's UUID just once
    node -e "console.log(crypto.randomUUID())"

    Submit only after review and authorization
    yourhost support submit SMTP-INTEGRATION.md --subject "Contact form" --request-id <UUID>

  3. Save the ticket and check its status

    The response returns the ticket UUID with status: received before sending the SMTP notification. Save that ticket and replace <TICKET_UUID> to check it. support list shows up to your website's 50 most recent requests without resending them. The request UUID is not the ticket UUID.

    Check the same ticket
    yourhost support status <TICKET_UUID>
    yourhost support list

If YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Keep the token private, without displaying it or sharing it in chat; never print its value. To use privateStore you may unset the variable only in your own safe environment, with your authorization; do not delete local credentials. You do not need administrator access and must not add credentials to the support file.

A received ticket does not mean an email was read

notificationState describes the email notification: queued (waiting), retry (safe retry), sending, sent (accepted by SMTP), failed or uncertain. sent proves neither inbox delivery nor reading. uncertain needs review: do not blindly resend.

If the response is lost, keep the same request UUID, subject and exact file for replay; check support list and the ticket if known. Do not generate a new UUID to resolve uncertainty. Changing content with the same UUID is not a replay. An empty list does not prove the local MD was submitted: check the bound folder or --folder and query the real ticket UUID if already received; do not reconnect or create another ticket to force it to appear.

Maximum: 12,000 message characters, 20 KiB JSON body and 160 subject characters. Up to 20 new requests in the last 24 hours and 200 retained per account; an identical replay does not create another ticket. These limits do not permit secrets.

Copy this message to your AI with a terminal

Your email service has its own access.

Website and email permissions are independent. You do not need to create a website to view an email service already authorized and associated with your account.

Website only

Publish your websites without creating mailboxes or granting email access.

Email only

An authorized email service can exist without a website or a web hosting plan.

Website and email

Use both services with the same portal account and separate permissions.

Available now: a read-only view of associated domains and mailboxes. Automated purchasing and provisioning of standalone email are still pending; no prices or immediate activation are offered here. Unified webmail sign-in is also pending.

  1. Open the email view

    Sign in to the portal and open Your domain email using this guide's link. A current email access grant is required.

  2. Select your domain

    Choose a domain associated with your account to view its mailboxes. Other customers' domains are not shown.

  3. Review and refresh

    Check mailboxes, their status and configured quota. Use Refresh email details whenever you need a recent reading.

View my email service in the portal
Visual example · not your account data

Your domain email

Email domainexample.com

Mailbox
info@example.com
Configured quota
The limit associated with your mailbox
Mailbox status
—

Configured quota is the mailbox limit, not storage you have used. This view does not show or change messages, passwords, mailboxes or quotas.

To read and send messages

Select Open webmail in the email view. An external site opens: sign in with your email address and mailbox password. Your portal session does not sign you in there automatically.

No domains, or access not available?

Check that you are using the right account and that the email service is associated and authorized. A website subscription alone does not activate email. If your session expired, sign in again; if the service is not associated, contact support. Do not change MX records to resolve this message.

Connect your own domain.

With a paid plan: up to five domains per website.

Visual example · not your account data
www.example.comTXT + CNAME / AHTTPS
  1. 1.Add your domain

    Open Manage your website → Connect your domain.

  2. 2.Copy the records

    Use the TXT and CNAME or A shown in the portal.

  3. 3.Verify DNS and HTTPS

    Allow DNS propagation, then select Verify DNS and HTTPS.

Your domain, from your provider.

A complete example: connect www.example.com to your website on YourHost.us. Choose the company managing your DNS, even if you bought the domain or hosted your website elsewhere.

  1. Registrar: where you bought the domain
  2. DNS: where you edit the records
  3. YourHost: where you publish your website
Which dashboard should I use?

At your registrar, open Nameservers and check who manages them. If you bought the domain at GoDaddy but use Cloudflare nameservers, follow Cloudflare. If you do not recognize the servers, ask domain support who manages the active DNS zone. You do not need to transfer your domain or change nameservers to connect www.

  1. 1. Publish your website first

    Upload your files or import WordPress into YourHost and check your subdomain. Changing DNS does not copy content, databases or email from your previous host. Keep a backup and coordinate the switch if your website receives orders or data.

  2. 2. Add www in YourHost

    With an active website and a paid plan, open Manage your website → Connect your domain. Enter www.example.com, without https:// or a path. Add it and keep the records displayed by the portal handy.

In your YourHost portal
Domain you are connecting
www.example.com
Your website’s CNAME destination
mi-web.yourhost.us
TXT value from your portal
yourhost-verify=TOKEN_FROM_YOUR_PORTAL

Illustration only: replace example.com, mi-web.yourhost.us and the token with your actual portal values. Do not point to yourhost.us or portal.yourhost.us.

You can also open any provider in the list.

Cloudflare

www

For the CNAME, select Proxy status → DNS only (gray cloud) and TTL → Auto. Keep DNS only: the orange proxy hides the destination YourHost checks. If you flatten all CNAME records, turn that off for this name; the TXT still proves ownership. Do not change nameservers for an already active zone.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Cloudflareexample.comDNSRecords
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add recordTXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www
    Content
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add recordCNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www
    Target
    mi-web.yourhost.us
    Proxy status
    DNS only · gray cloud

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Cloudflare

Google

www

Bought it through Google Domains? Those domains migrated to Squarespace. Sign in at account.squarespace.com/domains and follow this route if it manages your DNS. Google Workspace, Gmail, Google Sites and Search Console alone do not tell you where to edit DNS. If your nameservers belong to another provider, use its guide. For Cloud DNS, open the alternative below.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Squarespace Domainsexample.comDNSDNS SettingsCustom records
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add recordTXT

    TXTRecord fields
    Type
    TXT
    Host / Name
    _yourhost-verify.www
    Data
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add recordCNAME

    CNAMERecord fields
    Type
    CNAME
    Host / Name
    www
    Data
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · GoogleWhat happened to Google Domains
Is your DNS in Google Cloud DNS?

Only if a public Cloud DNS zone already manages your DNS. Select the correct project and zone. Enter the prefix in DNS name and check the full name appended by the console. Use a 300-second (5-minute) TTL if allowed; do not create a private zone or switch nameservers to follow this example.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Google Cloud ConsoleCloud DNSexample.comZone details
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add standardTXT

    TXTRecord fields
    Type
    TXT
    DNS name
    _yourhost-verify.www
    TXT data
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Create

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add standardCNAME

    CNAMERecord fields
    Type
    CNAME
    DNS name
    www
    Canonical name
    mi-web.yourhost.us.

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Create

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Google Cloud DNS

GoDaddy

www

Edit the existing www CNAME if it points to @ or an old website. Enter the portal destination in Value, not @ or a URL. If Domain Protection requests identity verification, complete it to save. If GoDaddy only registers the domain and DNS is external, make these changes at that other provider.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Domain Portfolioexample.comDNSDNS Records
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add New RecordTXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save / Save All Records

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add New RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www
    Value
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save / Save All Records

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · GoDaddy

Hostinger

www

Use hPanel’s DNS zone editor; some accounts also expose it through Websites → Dashboard. If Hostinger CDN controls www, disable that connection for the name you are moving before replacing it. Do not use a wizard to point to Hostinger hosting: the destination is your website’s YourHost subdomain.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    hPanelDomainsDomain portfolioexample.comDNS / NameserversDNS records
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add recordTXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www
    TXT value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add Record / Update

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add recordCNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www
    Target / Points to
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add Record / Update

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Hostinger

Network Solutions

www

For TXT, choose Other Host and enter _yourhost-verify.www; for CNAME, choose www. Alias to must point to the external hostname shown by YourHost. In classic view: Advanced Tools → Advanced DNS Records → Manage; edit Host Aliases (CNAME) and Text (TXT), then confirm Save Changes. Do not switch nameservers just to enable this editor.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Account ManagerDomainsexample.comManageDNS
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    + Add RecordTXT

    TXTRecord fields
    Type
    TXT
    Refers to / Host Name
    _yourhost-verify.www
    TXT Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add / Edit

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    + Add RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Refers to / Host Name
    www
    Alias to
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add / Edit

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Network Solutions

IONOS

www

If the menu opens Manage Subdomains, select www → DNS. Add the TXT from the example.com zone with the relative name shown. IONOS may ask you to disconnect another product using www before accepting a CNAME; review the affected service. This connects www, not the root domain automatically.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    IONOSDomains & SSLexample.comDNS
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add recordTXT

    TXTRecord fields
    Type
    TXT
    Host name
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add recordCNAME

    CNAMERecord fields
    Type
    CNAME
    Host name
    www
    Points to
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · IONOS

Bluehost

www

The primary route is Domains → DNS in the current portal. If your account manages that zone in cPanel, use Domains → Zone Editor → Manage and full names www.example.com. and _yourhost-verify.www.example.com.; check the suffix before saving. Do not use a DNS template that replaces the entire zone.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Bluehost PortalDomainsexample.comDNSManage Advanced DNS Records
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    + Add recordTXT

    TXTRecord fields
    Type
    TXT
    Host / Name
    _yourhost-verify.www
    TXT Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add / Save

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    + Add recordCNAME

    CNAMERecord fields
    Type
    CNAME
    Host / Name
    www
    Points to / Value
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add / Save

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Bluehost

SiteGround

www

Choose the TXT and CNAME tabs under Create New Record. If your interface shows Site Tools → Domain → DNS Zone Editor, open the same editor there. To update www, use the pencil under Manage DNS Records. Changes only take effect if the active nameservers belong to SiteGround.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Client AreaServicesDomainsexample.comSettingsDNS Zone Editor
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Create New RecordTXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Create / Confirm

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Create New RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www
    Resolves to
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Create / Confirm

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · SiteGround

HostGator

www

In Zone Editor, enter full names and check the trailing dot. If you bought the domain at HostGator, your Customer Portal may also offer Domains → domain → DNS. Use the editor for the zone actually serving your DNS, not both. The CNAME Record field takes a hostname, never an IP address.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    cPanelDomainsZone Editorexample.comManage
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    + Add RecordTXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www.example.com.
    Record / Text
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save Record

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    + Add RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www.example.com.
    Record / CNAME
    mi-web.yourhost.us.

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save Record

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · HostGator

Namecheap

www

This route applies to BasicDNS, PremiumDNS or FreeDNS. Select TXT Record and CNAME Record, not URL Redirect Record. If you use Namecheap Web Hosting DNS, manage the zone in cPanel → Zone Editor. Do not switch to BasicDNS just to follow this guide without first migrating the records for your other services.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Domain Listexample.comManageAdvanced DNSHost Records
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add New RecordTXT

    TXTRecord fields
    Type
    TXT
    Host
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Save All Changes / ✓

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add New RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Host
    www
    Value
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Save All Changes / ✓

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Namecheap

DreamHost

www

If www is Fully Hosted and DreamHost will not let you replace its automatic records, review its DNS Only option before creating the CNAME. That change removes hosting configuration for the affected name: back up/import first and review the impact on example.com and email with support. If you want to keep root-domain hosting, confirm how to release only www; do not remove the entire domain blindly.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    DreamHost PanelManage Websitesexample.com⋮DNS Settings
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add RecordTXT

    TXTRecord fields
    Type
    TXT
    Host
    _yourhost-verify.www
    TXT Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add Record

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add RecordCNAME

    CNAMERecord fields
    Type
    CNAME
    Host
    www
    Points to
    mi-web.yourhost.us

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add Record

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · DreamHost

OVHcloud

www

Depending on your view, the zone may also appear under Domain names → example.com → DNS zone. The wizard appends .example.com to the subdomain; do not repeat it. For CNAME, enter the full destination with a trailing dot if required and review the summary before Confirm. Do not select Reset DNS zone or web forwarding.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    OVHcloud Control PanelWeb CloudDomain namesexample.comDNS zone
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Add an entryTXT

    TXTRecord fields
    Type
    TXT
    Sub-domain
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add / Confirm

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Add an entryCNAME

    CNAMERecord fields
    Type
    CNAME
    Sub-domain
    www
    Target
    mi-web.yourhost.us.

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add / Confirm

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · OVHcloud

Hetzner

www

Use console.hetzner.com → your project → DNS; select the primary zone managing example.com. Check names and destination in the final list. Having a server or registering a domain at Hetzner does not mean its DNS zone is there: confirm the active nameservers first.

  1. 1Open the DNS zone

    Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.

    Hetzner ConsoleProjectDNSexample.comRecords
  2. 2Add the verification TXT

    Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.

    Type → TXT / CNAMETXT

    TXTRecord fields
    Type
    TXT
    Name
    _yourhost-verify.www
    Value
    yourhost-verify=TOKEN_FROM_YOUR_PORTAL

    Resulting full name

    _yourhost-verify.www.example.com

    Copy your portal value without manually adding quotation marks unless the editor requires them.

    To save: Add

  3. 3Connect www using CNAME

    Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.

    Type → TXT / CNAMECNAME

    CNAMERecord fields
    Type
    CNAME
    Name
    www
    Value
    mi-web.yourhost.us.

    Resulting full name

    www.example.com

    TTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.

    To save: Add

  4. 4Save and verify in YourHost

    Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.

    In your YourHost portal

    www.example.com

    Verify DNS and HTTPS

    When the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.

View official instructions · Hetzner
What about example.com without www?

It is a separate name: add it separately in YourHost and use A + TXT with the current portal values. Its TXT name is _yourhost-verify.example.com (usually Host: _yourhost-verify). Do not create a standard CNAME at @. Configuring www does not automatically connect or redirect example.com.

If it still does not connect
TXT not found
Check the active DNS zone, current token and full name. Avoid _yourhost-verify.www.example.com.example.com: many editors append the domain for you. If the portal refreshes the token, update the TXT too.
DNS points to another destination
The CNAME must be your website’s exact subdomain, without https://, slashes or paths. Check old www A/AAAA records, proxy/CDN settings and provider forwarding. Do not add IPv6 unless the portal tells you to.
Ownership verified, HTTPS pending
Verify again after a few minutes. If you have restrictive CAA records, ask your DNS administrator to check letsencrypt.org authorization while keeping other authorizations. If it persists, contact support with the domain and portal error.

Choose how to deliver changes.

publish is the recommended workflow from your project with a terminal; ZIP in the dashboard is the alternative. These other tools are optional and have their own permissions and requirements per website.

Git

Publish by pushing to main.

  1. 1.Add your Ed25519 public key (.pub) under Git and SFTP upload.
  2. 2.Copy the portal URL and place files in public/ (HTML) or source/ (projects/WP).
  3. 3.Push to main and check the same website's status.
git clone <URL from your dashboard>
git push origin main
SFTP

Upload with FileZilla or WinSCP.

  1. 1.Configure your public key on the website and copy its SFTP username.
  2. 2.Connect over SFTP to portal.yourhost.us:7387 with your local private key.
  3. 3.Upload public/ or source/ under /upload and select Publish SFTP staging in the portal.
portal.yourhost.us · SFTP · 7387
/upload/public/  → HTML
/upload/source/  → Project / WordPress
CLI

publish connects your project; support sends reviewed requests; deploy and source keep their advanced contracts.

  1. 1.Install CLI 0.3.3 with Node.js 22 or later. Use check to review and publish from the project folder.
  2. 2.Approve the URL and code in the portal, without copying tokens. Keep the terminal open during authorization and transfer; follow the same submission to its result.
  3. 3.deploy/source use YOURHOST_SITE_TOKEN; support also accepts the connected project private credential, but an environment token takes priority. source depends on website eligibility returned by the server; the cloudpage-pocketbase-v1 persistent example requires Owner. Continue only with eligible: true and use the plan id.
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz
yourhost check .
yourhost publish .
yourhost publish-status .
yourhost deploy ./public
yourhost source plan . --files src/app/page.tsx
yourhost source apply <UUID> --wait
yourhost source status <UUID>
yourhost source resume <UUID> --wait
API

Automate a ZIP with a website key.

  1. 1.Open Manage your website and create a publishing key.
  2. 2.Send the ZIP with Bearer authorization and a UUID in Idempotency-Key.
  3. 3.If the response is lost, keep the same UUID and ZIP; check status before sending again.
POST https://portal.yourhost.us/api/v1/site/deploy
Content-Type: application/zip
Authorization: Bearer <website-key>
Idempotency-Key: <UUID>

Give your AI a clear instruction.

Open your workflow, copy the instruction and review the delivery before uploading.

HTML

Next.js / Node.js

Vite / React

WordPress

Short answers to keep going.

Does creating SMTP-INTEGRATION.md send my request?

No. Your AI with a terminal must review the file with you and run support submit with explicit authorization. Keep UUID, subject and file if the response is uncertain. See the three steps under Send a support request; received confirms a ticket, not resolution or a read email.

Why can't I create websites?

Check your authorized hosting access and any pending operation in the portal. Contact support if you need help. Buying another plan does not replace pending activation.

What if publishing fails?

Identify the submission and read its code. A historical failure is not a website block. If pending or uncertain, query the same UUID. For different sources after a confirmed terminal result, use normal publish in the same folder or upload the corrected ZIP to the same website; not --retry or --reconnect. Repeating identical content requires a confirmed transient failure; PUBLICATION_FAILED without a specific cause needs support review. Do not create a duplicate website.

What happens when Free ends?

There is no automatic charge. To continue, explicitly subscribe to a paid plan. Check your dashboard's expiry date and keep a local copy.

How do I change or cancel my plan?

Open View my subscription. Use Manage subscription for payments/cancellation and the portal's plan-change options. Downgrading requires your websites and storage to fit the new quota.

Can I have email without a website, or a website without email?

Website and email permissions are independent. If your email service is already authorized and associated, you can view its domains and mailboxes in the portal without creating a website. Automated standalone email purchasing and provisioning are still pending. Webmail requires its own sign-in. Keep your MX records until a migration is coordinated.

Does my app need a DB, secrets or an external API?

WordPress has its own database. The Node profile has no DB, persistence, configurable secrets or outgoing server network. General Python/PHP profiles and MCP are not available; ask about compatibility before uploading.

No email, or a forgotten password?

Check spam and request another confirmation if the link expired. For password recovery, use Forgot your password? and open the latest message. Resetting a password does not confirm the email.

Why does my charge say CLOUDPAGE LLC?

That is the company providing YourHost. Stripe processes payments for CLOUDPAGE LLC; also check the amount and date. Contact support if you do not recognize a charge.

Share the error message with support, never passwords, keys or full card details.

Stuck on a step?

Tell us your website type and the message you see.

Get help

YourHost is a service provided by CLOUDPAGE LLC.

A visual guide to publishing your website | yourhost.us