Quick start

1. Sign in. Open the console address and enter your email and password. The top bar shows projects and tokens (admins also see users, metrics and platform). The language selector in the top bar — and on the login page — switches the console between English and Ukrainian; your choice is remembered, and until you make one the browser's language is used.

   hosting.example.com/login

   

2. Create a project. On Projects click + new project. Give it a slug (hello), a display name and the base domain — the hint under the field says it: sites become slug.alias.domain.
3. Pack your source. Zip or tar the folder (not the folder's parent): tar czf site.tgz index.html or zip -r site.zip .
4. Deploy. Open the project, stay on the Deploy tab, choose archive upload, pick the file and press deploy. The new deployment appears in the list — open its build log to follow the pipeline live.
5. Open the site. When the deployment turns running the app is up. Check Domains: the pre-check should be passed, then the certificate issued.

hosting.example.com/projects/7

BASE=https://hosting.example.com        # your console address

# 1 · log in — the response contains a JWT valid for 8 hours
TOKEN=$(curl -fsS -X POST "$BASE/api/v1/auth/login" \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","password":"…"}' | python3 -c 'import json,sys;print(json.load(sys.stdin)["token"])')

# 2 · create the project (returns its numeric id)
PID=$(curl -fsS -X POST "$BASE/api/v1/projects" \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \
  -d '{"slug":"hello","display_name":"Hello","base_domain":"example.com"}' \
  | python3 -c 'import json,sys;print(json.load(sys.stdin)["id"])')

# 3 · upload the archive (multipart field name: file)
UPLOAD=$(curl -fsS -X POST "$BASE/api/v1/projects/$PID/uploads" \
  -H "Authorization: Bearer $TOKEN" -F file=@site.tgz \
  | python3 -c 'import json,sys;print(json.load(sys.stdin)["upload_id"])')

# 4 · start the deployment (202 Accepted) and follow its log
curl -fsS -X POST "$BASE/api/v1/projects/$PID/deployments" \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \
  -d "{\"source\":{\"type\":\"archive\",\"upload_id\":\"$UPLOAD\"}}"

Deployments run in the background. Poll GET /api/v1/projects/$PID/deployments until the newest one is running, or stream the log from GET /api/v1/deployments/{id}/logs?stream=1.

Create a token on the tokens page, then connect your agent once:

claude mcp add --transport http dind-platform https://hosting.example.com/mcp/ \
  --header "Authorization: Bearer dt_…"

Now describe the outcome and let the agent call the tools:

The tools involved are create_project, upload_archive (or create_upload_url for big archives), deploy_app, list_deployments and get_logs. See API tokens, REST & MCP.