About
Twenty years of keeping systems running
I'm George Morris, an IT operations and infrastructure professional in Las Vegas. My work sits where servers, networks, hosting, and support meet the people who depend on them.
Open to work Full-time, contract, or fractional
How I got here
I started the way a lot of people in this field do: taking computers apart, teaching myself whatever was needed to make something work, and finding that the interesting problems were usually the ones someone had already given up on. That turned into systems administration — Linux and Windows servers in data centers, including time spent tuning Linux kernels on bare metal — and then into the broader work around it: hosting, web development, networking, endpoints, and support.
The roles followed that arc. At Peoria Park District I deployed MDM and wrote the enrolment and device policies, and maintained UniFi, VoIP, and security systems, endpoint security, and the district's WiFi, switching, and firewalls. At Caterpillar I worked as a Field Services Operations Tech, putting ITIL incident, problem, and change practice in place and coordinating hardware rollouts and network provisioning across sites. From October 2024 to February 2026 I was at Kings Global Consulting as Support Lead → Server Manager, leading enterprise support operations for distributed client environments and managing the server infrastructure behind high-availability client platforms. I now run Red Rock Webscapes, a web design and managed-hosting business in Las Vegas.
Alongside the operations work I kept building software — usually small, specific tools that removed a repetitive task from someone's day. That habit produced the Innovation Suite at Kings Global (a VPN presence scanner, a SendGrid log checker, Bot Sharpener, and the Ricardo AI assistant) and later open-source projects like LVChat and JobPulse. It's also why automation and AI tooling show up in my work as things that have to run reliably and be maintainable after handoff, rather than as a strategy slide.
I've also worked in a fractional CTO capacity — technical direction, infrastructure and architecture decisions, vendor evaluation, and mentoring — for smaller organizations that needed senior technical judgement without a full-time executive. It's one part of my experience rather than the whole of it.
What I bring
The parts of the job I'm good at
Production infrastructure
Linux and Windows servers, virtualization, hosting control panels, backups, and monitoring. I've inherited messy environments and left them documented.
Networks and endpoints
UniFi wireless and switching, firewalls, VoIP, and endpoint security — supported and maintained across multi-site organizations, with MDM deployments and policy design.
Support that scales
Leading support across distributed client environments: triage, escalation paths, knowledge base, and tooling that stops the same ticket arriving twice.
Practical automation
Python, PHP, and n8n. The goal is a system someone else can maintain and debug, not a demo that only works on my machine.
Approach
How I work
Learn the system before changing it
Read the configs, find out what depends on what, and understand why the last person did it that way. Most outages are surprises you could have seen coming.
Automate the repeat, document the exception
Anything done more than twice becomes a script or a workflow with a runbook. The strange cases get written down instead of living in someone's memory.
Leave it maintainable
Naming, backups, and documentation are part of the build. If I'm the only person who can fix it, I haven't finished.
Keep data where it belongs
Self-hosted where it makes sense, local-first where it's possible. Client and personal data shouldn't move to a third party just because that's convenient.
Toolkit
Platforms I work with
Grouped by where they show up in practice. This is the working set, not an exhaustive list.
Systems
Hosting & edge
Networks & endpoints
Monitoring & automation
Software & web
AI tooling
Off the clock
Still building things
Most of what I do for fun looks a lot like work. LVChat started as a question about how far PHP and SQLite could be pushed. There's usually an electronics project on the bench, and a long-standing interest in science fiction that explains a few of the channel names.
The chronological version, with dates and scope, is on the experience page. If you'd like the fuller history, get in touch and I'll send a résumé.