Real Work From Real Students
What happens when you give students access to proper cloud infrastructure and guidance from industry professionals? They build things that matter. Our students tackle actual deployment challenges, manage live servers, and solve problems that'll show up in their future careers.
Featured Student Work
These projects represent months of learning, debugging, and occasionally wanting to throw a laptop out the window. But that's how you actually learn this stuff.
Multi-Region Deployment Dashboard
Lachlan Fitzgibbons built a monitoring system that tracks server health across three AWS regions. Started as a simple status checker, ended up handling automated failover between Sydney and Melbourne endpoints. The kind of project that looks straightforward until you hit the reality of network latency.
What Students Actually Learn
This table shows what students know before starting versus after completing our capstone projects. Based on tracking data from our 2025 cohort.
| Technical Skill | Before Program | After Capstone | Practical Application |
|---|---|---|---|
| Server Provisioning | Theory only | Hands-on deployment | Spun up 4+ live servers |
| Database Management | Basic SQL queries | Full CRUD operations | Managed production databases |
| Load Balancing | Conceptual understanding | Implemented solutions | Configured nginx for traffic distribution |
| Container Orchestration | Never used Docker | Multi-container setups | Built Docker Compose environments |
| Security Protocols | Aware of best practices | Applied in production | Implemented SSL, firewalls, key management |
| Monitoring Systems | Used built-in dashboards | Custom monitoring | Set up alerting and logging pipelines |
| Backup Strategies | Manual backups | Automated systems | Scheduled backups with rotation policies |
The Capstone Journey
Most students spend 14-16 weeks on their final project. Here's what that actually looks like, week by week.
Planning and Architecture
Students pick their project scope and design the infrastructure. This phase involves a lot of whiteboard sessions and rethinking initial assumptions about what's actually possible.
- Define project requirements and success criteria
- Design system architecture with mentor feedback
- Choose appropriate cloud services and estimate costs
- Create deployment timeline with realistic milestones
Development and Testing
The bulk of coding happens here. Students build their applications while simultaneously learning that local development environments behave very differently from cloud servers.
- Set up development and staging environments
- Build core functionality with continuous testing
- Implement security measures and access controls
- Debug issues that only appear in cloud environment
Deployment and Optimization
Moving to production reveals all sorts of interesting problems. Students learn about database migrations, zero-downtime deployments, and why monitoring matters.
- Deploy to production environment with proper procedures
- Configure monitoring and alerting systems
- Optimize performance based on real usage data
- Implement backup and disaster recovery protocols
Documentation and Presentation
The final stretch involves documenting everything and presenting to industry professionals. Students explain their technical decisions and demonstrate what they built actually works.
- Write comprehensive technical documentation
- Create deployment guides for future maintenance
- Prepare presentation covering architecture and decisions
- Present to panel of industry professionals for feedback