EF-004 — Digital Estate
Document ID: EFType: ReferenceStatus: DraftOwner: Cloudberrie StudioVersion: 1.0Updated: 2026-07-17
Domain Estate
| Domain/property | Purpose | Status | Risk |
|---|---|---|---|
| cloudberrie.com | Company website and Workspace email domain | Active | High: email and public brand |
| manual.cloudberrie.com | Business & Operations Manual | Planned deployment | Depends on root DNS |
| board.cloudberrie.com | Studio Board | Planned production subdomain | Depends on root DNS |
| aifa.team | AIFA | Active/planned product domain | Moderate |
| needleneeds.com | Needle Needs | Live mature property | Highest migration sensitivity |
| khushimarriagebureau.com | Khushi Marriage Bureau | Early stage | Low current traffic risk |
Core Platforms
| Platform | Estate component | Business identity |
|---|---|---|
| Google Workspace | Identity, Gmail, Drive, Calendar | admin@ + aliases |
| GitHub | Organization and repositories | accounts@ |
| Cloudflare | DNS, Pages, security, Access | accounts@ |
| Firebase | Auth, Firestore, Storage | accounts@ |
| Meta Business | Facebook/Instagram business and client access | social@ |
| LinkedIn / YouTube | Company and content channels | social@ |
Planned, Not Automatically Enabled
Workers, R2, KV, D1, Images, and other Cloudflare services should be enabled when a documented product requirement exists. Enabling every service in advance creates unnecessary cost, access surface, and operational confusion.