Our Story — Teaching Technology That Serves People

Marvin Gage

Marvin has been building for the web since WordPress ruled everything. He saw firsthand what happened when small business owners and nonprofits tried to manage their own sites — the bloat, the security headaches, the endless plugin updates, the bills that kept climbing. He knew technology was supposed to make this easier, not harder. So he built a modular, card-based website framework that stripped away the complexity while keeping the power. Fast. Secure. Actually easy to manage. No training required.

Then came the phishing crisis. Fake emails pretending to be from clients. Spoofed domains. Credential theft. The people who needed protection the most — small businesses, nonprofits, elderly operators — were the least equipped to defend themselves. Marvin built Email AI, an AI-powered classification system that catches phishing, spam, and scams before they reach a human. It's the kind of protection that big enterprises pay thousands for, now accessible to anyone. For Marvin, it's not just about building tools — it's about building tools people can actually understand, trust, and afford.

Nick Hiteshew

Nick has worn a lot of hats. He owned a taxi company, then a limousine company — businesses where dispatch, billing, scheduling, and communication all had to work together in real time. That experience taught him how hard it is to make different systems talk to each other when it actually matters. He also worked with overseas developers building apps and platforms, which gave him a front-row seat to both the promise and the pitfalls of outsourced technology — you can get something built fast, but if you don't control the code and don't understand the architecture, you're at someone else's mercy.

Later, in the pilot car industry — guiding oversized loads on highways — he hit the same wall from a different direction. Different radios, different apps, different log sheets. Nothing talked to anything. He started building a tool to fix it and ran straight into the same problem: APIs don't connect, data doesn't flow, every system is an island.

But the mission that changed everything was Wilmington Response, the disaster relief nonprofit he runs. When a hurricane hits, volunteers pour in from everywhere. Food, water, supplies, shelter assignments — it's chaos. And the hardest part isn't the disaster — it's the coordination. Volunteers scattered across group chats and spreadsheets. Admins burning out trying to keep up. The same problem repeats in every nonprofit he's seen: animal rescue, food banks, homeless outreach. There are never enough volunteers, never enough admins, never enough time.

That experience shaped two core goals. First: an affordable, secure way to use AI so that people could actually benefit from it without accidentally leaking API keys or breaking their code. Second: a platform that could help small businesses, nonprofits, and special needs organizations automate the processes they'd otherwise struggle to afford or find the staff to manage. Not a stripped-down version of enterprise software — something built from the ground up for the people who need it most.

Technology needed to serve people — not the other way around.

Jeremy Jankovsky

Jeremy is the Director of Information Technology at Skidmore-Tynan ISD, a K-12 school district in rural Texas, where he keeps the district's infrastructure running — networks, servers, security, and the systems that teachers and students rely on every day. Before that, he served in the United States Navy, where he learned the discipline of building systems that have to work right the first time, every time. He also spent time as an Install Technician at Safelite, which gave him a grounded perspective on what it means to solve real problems for real people.

Jeremy has spent years building the kind of infrastructure that most people never see but everyone depends on. His creation — Hermes — is an agentic framework that connects AI models, tools, APIs, and data into a single operating layer. Think of it as the operating system for AI agents: the engine that lets them actually do things, not just talk. Read files. Send messages. Search the web. Run code. Coordinate across servers.

Jeremy's background is in building systems that are secure by default. He saw too many AI projects fail because security was bolted on at the end — API keys hardcoded into front-end code, data piped through unencrypted channels, models trained on customer data without permission. He built Hermes to solve that from the ground up — secure tool access, credential isolation, audit trails. Working in a school district, he knows what it means to do more with less — there's no enterprise budget, no dedicated security team, no room for expensive mistakes. That constraint shaped everything about how he builds.

While Marvin was fixing websites and Nick was connecting tools, Jeremy was building the nervous system that could tie it all together safely. He didn't know he was building Onveros. He was just building something that worked the way it should.