Enterprise IT training built for the real world.
Students don't just study IT — they practice working like IT employees.
🌐 Website · Vision · Career Ops Mode · Shift Mode · Training Domains · Access
ARIA is a career-long IT training and practice platform for aspiring, transitioning, and working technology professionals.
It is not a course library. It is not a chatbot. It is not a collection of isolated labs.
ARIA is a guided workplace simulation where students practice how to read tickets, prioritize work, investigate systems, collect evidence, document findings, and grow through progressive responsibility — before they ever touch a real production environment.
The differentiator is enterprise realism. Students don't click through lessons — they enter a simulated IT workplace and receive work.
ARIA runs entirely in the browser — nothing to install, no VPN, no client. A student can start a shift from a laptop, a Chromebook, a library computer, or a phone.
Signing in is simple on the surface and strict underneath:
1. Open ARIA in any web browser.
2. Enter your email — a one-time code is sent to it.
3. Type the code. You're verified — no shared password to leak, nothing to memorize.
4. You land on a personal workspace showing only the lab systems assigned to you.
Each student gets a Linux terminal and a Windows desktop streamed straight to the browser tab — plus network simulation and identity tooling when a lab calls for them. The device never joins the private network and never needs special software. The Linux workspace comes preloaded with the everyday toolset — git, tmux, vim, curl, and standard networking tools — so students can start working immediately, and each one is a persistent container they return to, not a throwaway sandbox.
Underneath is a zero-trust, least-privilege model: an identity-aware access gateway verifies every student at the edge, a browser-based access broker connects them to only their own resources, and the student path is completely separate from the instructor's private management path. Nothing lab-facing is exposed directly to the internet.
The result is enterprise-grade access that a first-week student can use without a setup call. See Access Model for the full description.
When a student opens Shift Mode, they don't see a lesson list. They see a standing queue of at least four labs their instructor has assigned at their level:
Your Assigned Labs — Junior IT Operations
• Login triage on a training workstation Identity / Endpoint
• Name resolution is failing for a user Networking
• Endpoint health check requested Linux / SysAdmin
• New training asset needs inventory review Asset Management
Work them in any order. Each is reviewed by your instructor.
The student chooses a lab, investigates within their permitted level, collects evidence, consults the ARIA Mentor when stuck, and submits the work for instructor review. When a lab is approved and leaves the queue, the next level-appropriate lab takes its place — the queue stays full, and the instructor stays in control of what's eligible.
That moment — choosing which lab to tackle first — changes the learning experience. The student is no longer consuming information. They are practicing responsibility.
| # | Pillar | What It Means |
|---|---|---|
| 01 | Hands-On Enterprise Simulation | Students work tickets, follow procedures, gather evidence, and document outcomes inside workflows modeled after real IT operations |
| 02 | AI-Guided Mentorship | The ARIA Mentor acts like a senior teammate — not an answer machine. It asks questions, not just gives answers |
| 03 | Progressive Career Practice | Students move through levels of responsibility. No one gets assigned senior infrastructure work without preparation |
| 04 | Evidence-Based Learning | Students learn to document proof, not assumptions. "I fixed it" is not an answer. Evidence is |
| 05 | Instructor-Governed Safety | The instructor controls progression, high-risk work, and outside labs — mirroring how real IT teams operate |
ARIA organizes practice into six training domains that mirror the live lab catalog — 100 hands-on labs in total (95 production-ready). A single ticket may touch several domains at once.
| Domain | Focus | Labs |
|---|---|---|
| 01 · Help Desk & Ticketing | Triage, documentation, escalation, professional communication, asset/operations awareness | 24 |
| 02 · Identity & Access Management | Account review, login triage, group membership, lockouts, MFA, Windows endpoint & policy validation | 21 |
| 03 · Networking & Cisco | IP/DNS/DHCP, VLANs, routing, switch/router troubleshooting, network automation | 17 |
| 04 · Linux & Systems Administration | Service status, log review, health checks, safe scripting, automation & documentation | 16 |
| 05 · Security Operations Center | SIEM alert triage, investigation, incident notes, instructor-authorized offensive track | 12 |
| 06 · Data Analysis | Data profiling & cleaning, relational (star-schema) modeling, SQL and pandas analysis, dashboards in Power BI & Tableau, and sensor time-series | 10 |
Asset management/operations and outside-lab support run across these domains rather than as separate tracks, and a graduation Cross-Domain Incident Response capstone connects them end to end. See the Training Domains Overview.
Students cannot skip levels by default. Promotion requires completed tickets, evidence quality, documentation quality, safe behavior, and instructor approval.
| Level | Tier | What Students Practice |
|---|---|---|
| L1 / L2 | Junior IT Operations | Safe triage and evidence collection. Prove what you observed before recommending action |
| L3 / L4 | Intermediate Infrastructure Ops | Controlled remediation. Stronger pre-check, post-check, and rollback awareness |
| L5+ | Senior Operations / Engineering | Root cause analysis, change planning, runbooks, post-incident review, mentoring others |
The same topic appears at every level — with different expectations.
Junior: Can the endpoint resolve names?
Intermediate: Why is the endpoint receiving the wrong network settings?
Senior: Is this a design or architecture issue that affects multiple teams?
The AI Mentor inside ARIA is designed to act like a senior teammate, not an answer machine.
Instead of handing students the solution, it asks:
What system is affected?
What did the user report?
Can you prove the endpoint is online?
What evidence do you have?
What does the evidence show?
What does it not yet prove?
What would you check next?
The goal is to build judgment, not dependency.
Students don't just finish labs — they graduate with a portfolio of real, instructor-approved work they can hand to an employer.
Every completed lab that reaches a student's portfolio has passed a layered review: automated evidence checks, AI rubric grading as a second opinion, and — the deciding step — human instructor approval. Only approved work is included.
Each portfolio is cryptographically signed, so its authenticity can be confirmed independently:
- An employer can verify a portfolio through a public verification page — no account, no login, no need to contact ARIA.
- The signature confirms the portfolio was genuinely produced through ARIA and that every lab in it was instructor-approved.
- Any edit to the work after signing breaks the signature, so a portfolio can't be quietly altered.
The result is a credential backed by evidence, not just a claim. Secrets and any private lab details are removed before a portfolio is exported — what remains is the student's own work, safe to share.
- Aspiring IT professionals entering the field
- Career transitioners preparing for help desk or support roles
- Learners moving from certification study into practice
- Working professionals refreshing or expanding skills
- Instructors who want realistic, structured practice environments
This repository is the public documentation home for ARIA. It contains the learning model, training philosophy, and sanitized examples. It does not contain application code, private infrastructure, credentials, or real student data.
| Document | Description |
|---|---|
| ARIA Vision | Mission, core idea, five pillars, and long-term direction |
| Career Operations Mode | The progressive workplace simulation and student experience |
| Career Operations Features | Assignment Bridge, Employee Onboarding, Student Dashboard, and Outside Lab Support |
| Shift Mode | The daily ticket queue — how students choose, investigate, and submit work |
| Access Model | Any device, anywhere — browser-only access, one-time-code sign-in, and the zero-trust security model |
| Evidence-Based Learning | Proof vs. claim, scope enforcement, teardown requirements, and the final note format |
| ARIA Mentor | The AI coaching model — template validation, evidence standards, and instructor loop |
| Training Domains Overview | All six domains, the capstone, and how they connect |
| Security and SOC Domain | Six defensive SOC labs, the offensive track, evidence standards, and the dedicated security node |
| Public / Private Boundaries | What belongs here and what stays in the private codebase |
|
Julius Moore Founder & Platform Architect — ARIA Training Labs ARIA was built from a single observation: the gap between certification study and actual IT work is too wide. The best way to close it is to make students practice like they're already on the job. ariatraininglabs.com |
No private infrastructure details, credentials, internal addresses, source code, or real student records are published here.
See docs/governance/public-private-boundaries.md for the full governance standard.