Architecture

This section explains how Airfree Cloud integrates with Hostiva for the Domain Module.

1. High-level components

• Airfree Cloud UI: domain search + checkout UX
• Airfree Cloud Backend: server-to-server calls to Hostiva (never expose keys in browser)
• Hostiva Core API: tenant-aware, permissioned sandbox + live endpoints
• Sandbox Engine: deterministic behaviors for testing
• DNS Cloud: default nameservers + future zone automation
• Webhook Delivery: event callbacks + retry and signing

2. Integration boundary (recommended)

flowchart LR
  U[User] --> UI[Airfree Cloud UI]
  UI --> AFAPI[Airfree Backend API]
  AFAPI -->|Bearer Key + X-Tenant| HAPI[Hostiva Core API]
  HAPI --> SANDBOX[Sandbox Engine]
  HAPI -->|events| WH[Webhook Delivery]
  WH --> AFAPI
  HAPI --> DNS[DNS Cloud]

3. Security notes

• Hostiva developer keys must be stored in Airfree backend .env and never sent to the browser.
• Use X-Idempotency-Key on order creation to prevent accidental duplicate orders.
• Webhooks must be verified using HMAC signature and replay protection.

4. Observability (recommended)

• Correlation ID header (optional): X-Request-Id: <uuid>
• Log at Airfree and Hostiva using order_id and request_id.