- Move infrastructure into businesses/00-infrastructure; add 01-06 numbered dirs ordered by importance (secure, support, systems, cloud, web, software) - Add per-business branding.html (accent color scheme + ChatGPT logo prompt) - Add NN-name.md scaffold/research/todo docs for the six planned divisions - Make divisions/ the formal-docs library: parent + infrastructure briefs, legal-structure, investment-research - Add root README map and businesses/ index; empty READMEs per dir - Fix all relative links broken by the moves
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# SNS Cloud
|
|
|
|
**Parent:** SnS Network Solutions · **Tagline:** *Infrastructure Without Limits*
|
|
|
|
## Scope
|
|
Anything hosted off-premises: public cloud, hybrid, and cloud-native
|
|
infrastructure. The scalable extension of SNS Systems.
|
|
|
|
## Services
|
|
- AWS and Azure architecture and deployment
|
|
- Hybrid infrastructure (on-prem ↔ cloud) and migration
|
|
- Infrastructure-as-code, automation, and CI/CD
|
|
- Cloud networking, security, and cost optimization
|
|
- Backup, DR, and business-continuity in the cloud
|
|
|
|
## Positioning
|
|
The scale layer. Line vs. neighbors: **Infrastructure** = the LAN/wire,
|
|
**Systems** = on-prem compute, **Cloud** = off-prem compute. Naming note: "SNS"
|
|
also = AWS Simple Notification Service — keep internal docs unambiguous.
|
|
|
|
## Liability & Ops Notes
|
|
- **Medium** — professional liability; client cloud spend and data handling
|
|
create fiduciary/contractual responsibility. Define who owns the cloud account.
|
|
- **Entity:** operating subsidiary **SNS Cloud LLC** under SnS Network Solutions
|
|
Holdings LLC. **Liability tier: Medium** — form its own LLC when this becomes an
|
|
active business.
|