About us

Healthcare IT since 2012. Products we build ourselves.

Rubix Technology LLC keeps healthcare organizations running — and turns what that work teaches us into software anyone can use. 30+ years of hands-on IT behind our engineers, 5 service practices under one roof, 4 products of our own in production.

Who we are

We support what we build

We began in 2012 as an IT support company for healthcare, and we still are one. That is an unusually demanding place to learn the trade: an outage interrupts care, every access to a record is auditable, and “we restored most of it” is not an acceptable sentence. Meeting that standard for over a decade — on top of a team carrying 30+ years of hands-on IT — is where everything else here comes from.

We are in Grand Rapids, Michigan, and we are a United States based company only — the engineers who build, the technicians who answer and the people who own the roadmap are all in the same company, in the same country. For a managed-services customer that is not a slogan: it decides who picks up when something is wrong at 6am.

Most technology firms pick a side. Consultancies build something and hand it over. Managed-service providers keep the lights on but don’t write software. Product companies ship a product and leave the integration to you. We do all three, and that combination is the whole point: the people who designed a system are the ones paged when it misbehaves, which changes how it gets designed.

What AI actually changed for us

For years the gap between “we know exactly what this industry needs” and “we can afford to build it” was too wide to cross. AI closed it. We built our own suite of AI-assisted engineering, support and delivery tooling, and it does that work faster and cheaper than doing it by hand — which is why we can maintain a growing product line, add features in weeks, and still compete on price for services work.

The judgement is the part AI didn’t give us. Knowing which failure modes matter, which shortcuts bite three years later, and what a technician actually needs at 2am comes from 30+ years of doing the work. The tooling just made acting on it affordable.

Built for healthcare, useful to everyone

It shows in our own software. Secure Message encrypts and filters mail on the customer’s own network. SecureGuard turns a firewall’s entire configuration into one reviewable, revertible document. Secure Desk is web VDI and isolated AI-agent desktops on a relay you run — the relay forwards ciphertext it cannot read. Support is one use case. All three are self-hosted, and supporting them on hardware we don’t host taught us things about encryption, isolation and deployment that no architecture diagram would have.

None of those are healthcare-only products. They were built for a clinical environment — a strict version of what any organization wants. We keep adding to the range, and every new one is held to the same standard.

We would rather tell you an honest “that won’t help” than sell a project that demos well and dies in production.

That applies most to AI. There is real, measurable value in retrieval over a company’s own documents, in classification that clears a manual review queue, and in agents that can act with proper permission boundaries. There is very little in a chatbot bolted onto a website. We spend our first conversations working out which one you’re describing.

How we work

Senior engineers, working in short increments with something running at the end of each one. Documentation and access are handed over as we go, so you are never hostage to us — and if you would rather own the result outright, we will train your people and step back.

And then we support it. Support is the oldest thing we do, not an afterthought bolted onto a product launch: the same agreements that keep clinics running back the software we sell, so a customer with a problem reaches people who can read the source.

What we stand for

What we will stand behind

Built in healthcare IT since 2012

Our habits come from an industry where an outage is a clinical problem, every access is auditable and patient data has rules. That standard is the baseline we apply everywhere else — most organizations benefit from it, few are asked to meet it.

Thirty years of IT, used on new tools

The team has 30+ years of hands-on IT behind it. AI didn’t give us the judgement about what to build; it removed the cost of building it, which is why our product line keeps growing instead of standing still.

One US company, in Grand Rapids

Rubix is United States based only. Engineering, delivery, and support sit in one company in Grand Rapids, Michigan — no offshore tier, no follow-the-sun handoff. The people on your systems work with the people who built them.

We use AI on our own work first

The suite of internal AI tooling we built does our engineering, support, and delivery work faster and cheaper than doing it by hand. That is how we keep rates competitive and ship product features in weeks.

We ship software, not just advice

Four products are ours end to end — a mail gateway, a firewall and web VDI / isolated agent desktops, all self-hosted, plus Secure Assess as multi-tenant SaaS for defensive PCI 11.3 scans. The engineers on your project are the ones who wrote them.

Support is the product we’ve practised longest

Before we sold software we spent years supporting other people’s, under agreements that didn’t forgive a slow answer. Our products inherit that: you reach the team that wrote the code, not a queue that only escalates.

Security is requirement #1

We build to HIPAA and PCI DSS standards as a baseline, not as a retrofit: least privilege, encryption in transit and at rest, audit trails and tested restores. Healthcare and payment data taught us to design that way; every client gets it, whether their industry demands it or not.

Your data stays yours

Private and on-premise deployments are a default option, not an enterprise upsell. Our own products hold to it: the gateway’s inbound BEC/phishing score runs on-box, and the Desk relay forwards traffic it cannot decrypt.

Get in touch

Talk to the people who’d do the work

No account manager relaying questions to an engineer in another timezone. You get the engineer.

Or email ussales@rubixtechnology.com

Prefer to talk? The number is in the header, on every page.