Hardware & inventory
Document the compute devices, Raspberry Pis, managed networking equipment, and available storage before assigning roles.
Explore this area →Roadmaps / Infrastructure
Reliability first.
Capacity when justified.
The public direction for a dependable development environment. These are proposed readiness stages—not completed installations, approved purchases or promised dates.
Explore the foundation
Six focused areas.
Capabilities and verification steps, not a public device inventory or spending approval.
Networking
Design an independent lab network without changing the household Xfinity service or everyday devices.
Explore this area →Compute & virtualization
Evaluate workload roles, hypervisors, containers, local AI processing, and future Proxmox options.
Explore this area →Storage & backups
Plan durable project storage, recovery copies, a future NAS, and restore testing.
Explore this area →Security & access
Keep household services independent while improving access control, segmentation, and recovery practices.
Explore this area →Budget & expansion
Organize existing assets, optional purchases, recurring services, and power protection by dependency.
Explore this area →Detailed readiness ledger
Dependencies stay explicit.
These retained planning records are not automatically marked complete when a purchase, preview or code change occurs.
01 · Inventory & foundation
Verified equipment inventory
Confirm owned computers, Raspberry Pi boards, network gear and storage without publishing sensitive identifiers.
Depends on: Access to private inventory records
Cost status: Existing equipment
Backup and restore baseline
Verify recoverable backups before any operating system, disk or network migration.
Depends on: Inventory and backup destination review
Cost status: To be scoped
02 · Networking & security
Lab segmentation design
Design the lab separately from household Xfinity routing, with an approved rollback plan.
Depends on: Current topology and switch capability verification
Cost status: Existing gear first
Firewall and remote access plan
Specify least-privilege policy, access approval and fail-safe testing.
Depends on: Approved segmentation plan
Cost status: To be scoped
03 · Compute & virtualization
Server workload map
Assign proposed workloads across the Ubuntu system, workstations, Pis and future hosts.
Depends on: Verified CPU, memory and storage inventory
Cost status: Existing equipment first
Virtualization pilot
Evaluate Proxmox and alternatives on suitable hardware without modifying daily-use machines.
Depends on: Backups, compatibility and maintenance window
Cost status: To be scoped
04 · Storage & backup
NAS and shared-storage design
Compare dedicated NAS, existing server and Pi-based approaches for workload fit.
Depends on: Storage inventory and recovery requirements
Cost status: Quotes pending
Recovery test and retention
Define versioned backups, retention and a repeatable restore exercise.
Depends on: Selected backup destination and safety approval
Cost status: To be scoped
05 · AI & automation
Local AI service architecture
Document model-hosting capacity and safe separation between experiments and reliable services.
Depends on: Workload map and capacity verification
Cost status: Existing equipment first
Automation service organization
Plan service ownership, observability, deployment and credential handling.
Depends on: Compute and security baseline
Cost status: To be scoped
06 · Reliability & expansion
Monitoring and alerts
Plan health checks, logs, capacity reporting and operator response procedures.
Depends on: Stable workloads and private inventory
Cost status: To be scoped
UPS and expansion decisions
Size power protection and future capacity only after measuring current loads.
Depends on: Hardware inventory and measured power use
Cost status: Quotes pending
Public progress.
Private operating details.
Network configurations, machine inventories, costs, investor terms and financial records are not published in this roadmap.