The Naming Landscape
Multiple names have emerged organically across the project. This doc captures all of them, their origins, and the decision on what to use going forward.
Name Inventory
| Name | Origin | Domain | Status |
|---|
| Starlight Practice | Erik — chosen for the .com | starlightpractice.com | Primary brand name |
| Starlight Pediatrics | Deepak — the actual medical practice name | starlight-pediatrics.netlify.app (prototype) | Practice name (Dr. P's clinic) |
| Starlight.MD | Deepak — business plan branding | starlight-md-plan.netlify.app (biz plan) | Business plan / pitch deck name |
| Starlight Pediatrics EMR | Claude — initial doc site title | — | Deprecated — too narrow |
| Starlight EMR | Redirect domain | starlightemr.com | Redirect → starlightpractice.com |
| Starlight PMS | Redirect domain | starlightpms.com | Redirect → starlightpractice.com |
Why "Starlight Practice"
| Reason | Detail |
|---|
| .com availability | starlightpractice.com is owned and live. The .com matters for credibility with physicians. |
| Broader scope | "Practice" covers the full product vision — the single pane of glass for an entire DPC practice. Not just EMR, not just billing, not just pediatrics. Dashboard, CRM, billing, comms, analytics, clinical workflows — everything. |
| Specialty-agnostic | "Pediatrics" limits to one specialty. "Practice" works for the expansion path: pediatric DPC → family medicine → adult DPC → concierge/employer. |
| Not "EMR" | EMR implies clinical charting only. The product is practice management + CRM + communications + analytics + billing. EMR charting is Phase 3 roadmap. |
| Not ".MD" | The .md TLD (Moldova) is not supported by AWS Route 53 — can't use it for DNS/hosting. Also creates brand collision with Atlas**.md**, the very competitor we're displacing. We want to be bigger than "another .md" — we're the single pane of glass for an entire practice. |
| Clean and professional | "Starlight Practice" sounds like a real company name, not a side project. |
Domain Strategy
| Domain | Purpose | Cost |
|---|
| starlightpractice.com | Primary — marketing site, app, docs, everything | $15/yr |
| starlightpms.com | 301 redirect → starlightpractice.com | $15/yr |
| starlightemr.com | 301 redirect → starlightpractice.com | $15/yr |
Usage Guidelines
| Context | Use |
|---|
| Product name | Starlight Practice |
| Company/legal entity | TBD at incorporation (likely Starlight Practice, Inc. or Starlight.MD, Inc.) |
| Dr. P's clinic | Starlight Pediatrics (unchanged — this is her medical practice) |
| Deepak's prototype | starlight-pediatrics.netlify.app (his domain, unchanged) |
| Business plan / pitch | Starlight.MD is fine for pitch decks (the .MD is catchy for investors) |
| GitHub repo | MillionOnMars/Starlight |
| Documentation site | Starlight Practice Docs |
| API subdomain | api.starlightpractice.com |
| Staging | dev.starlightpractice.com |
Why Not "Starlight.MD"
Deepak's business plan uses "Starlight.MD" — and while the MD/Medical Doctor double-meaning is clever, there are three hard blockers:
- AWS doesn't support .md — Route 53 cannot register or manage .md (Moldova) domains. Our entire infrastructure is AWS/SST. Non-starter.
- Brand collision with Atlas.md — We're positioning against Atlas.md as "bigger than an EMR." Sharing their TLD puts us in their shadow instead of above it. We're not another ".md" tool — we're the single pane of glass for the entire practice.
- Scope limitation — ".MD" signals "medical doctor tool." We want to signal "practice operating system." Starlight Practice says exactly what it is.
The business plan can reference "Starlight.MD" as historical branding, but the product ships as Starlight Practice at starlightpractice.com.