Bighorn Byte, and who builds it.
Custom business websites, dealer inventory platforms and the admin portals behind them. Built and supported directly, out of Sheridan, Wyoming.
Where this came from
Gillette, then the Air Force, then Sheridan.
Hometown Roots
I grew up in Gillette, Wyoming. Around there, folks work hard, keep their word, and help each other out. That's how I was raised, and it's how I still approach my work today.
The Pivot to Cyber
I joined the Air Force to work in radio communications. While I was there, I learned about a new cybersecurity team called the Mission Defense Team. I studied for my Security+ certification, got accepted, and worked with a small crew to build new cyber defense methods from the ground up. Those methods were later adopted across most Air Force bases.
From Student to Mentor
That job introduced me to servers and enterprise networking. I put in the time to learn everything I could, and before long I was writing Linux guides that other team members used in training. I found out I enjoyed both solving tough problems and teaching others how to solve them too.
Barracks Connectivity
While I was deployed in Africa, the barracks didn't have any internet. I ran a cable to my container, set up a router I had flashed with DD-WRT to bypass certain network restrictions, and got Wi-Fi working in our little connex box. It gave everyone a way to stay connected during downtime.
Sharing the Know-How
When I got back, I started a YouTube channel (now unlisted) with tutorials on setting up home servers. I liked finding ways to explain complicated steps so that anyone could follow along.
Starting Bighorn Byte
Bighorn Byte started in Sheridan doing the hands-on work: networks, servers, backups, and the calls that begin with nothing working. That work is still here, and it is where the habit of picking up the phone yourself came from.
What it builds now
Most of the work is software. Custom business websites with a real admin portal behind each one, dealer inventory platforms, manufacturer feed integrations, staff accounts, off-site backups and the monitoring underneath all of it. Every build that ships is run day to day by the client's own staff rather than by a developer.
The work is the better argument.
Six builds are live and run by the people who own them. The demo is the same admin, seeded with a sample lot, open with no signup.