Founder - Software Defined Corporation

Rashid Amin

Founder, Software Defined Corporation. Twenty-plus years as the engineer, and then the director, who had to make the vendor’s number true.

In short

Rashid spent two decades in Southern California IT — as a systems engineer at managed service providers, and as Director of IT and Privacy Officer inside a publicly traded healthcare organization — on the side of the table where spec sheets become tickets and vendor claims become compliance exposure. MFid is what he built after watching the same gap between promise and delivery recur across every employer, every vendor, and every renewal: a way to measure it instead of arguing about it.

Career

Managed services, Los Angeles

Systems and escalation engineering at Cal Net, then seven years as Senior Systems Engineer at LANAIR (2010–2017), with a later stretch at 1PATH. The work was the MSP’s work: backup and recovery, server and storage infrastructure, and the escalations that land when a vendor’s product does not do what the datasheet said. At Cal Net he automated the firm’s Backup Exec environment end to end; at LANAIR he wrote the engineer-to-engineer knowledge base the rest of the team ran on.

Healthcare IT

Director of IT and Privacy Officer at ApolloMed, a publicly traded healthcare organization — accountable both for the infrastructure and for the organization’s privacy obligations under HIPAA. Earlier roles at Network Medical Management and Healthsource. These are environments where uptime, data retention, and vendor SLAs carry regulatory weight, where a vendor’s security and availability claims have to be verified rather than taken on faith, and where the cost of a broken promise is counted in patient-facing minutes.

Education

B.A. in Computer Science, Knox College, Galesburg, Illinois.

Why he built MFid

An MSP engineer sits between two sets of promises: the ones the vendor made to the MSP, and the ones the MSP made to its clients. When the first set fails, the second set fails too, and the engineer is the one in the room explaining why. A Privacy Officer sees the same problem from the other chair: vendor security and availability claims become the organization’s own compliance posture the moment the agreement is signed, and “the vendor said so” is not a defense an auditor accepts. After enough of those rooms, the question stops being who is at fault and becomes why did nobody measure this before we signed.

MFid is the answer to that question, built by someone who needed it rather than someone who studied it. The design choices on this site — the weakest promise dominating the score, the refusal to score from the vendor’s own dashboard, the insistence that the measurement window include the client’s worst day — are each a lesson from a specific ticket.

The firm holds itself to the same instrument. Its own uptime, latency, and reachability are scored and published live, alongside the promises it has not yet instrumented.

Reach him

Through the contact form, or via the company on LinkedIn. Engagements begin with the ten intake questions; question 7 alone is worth the call.

Bring us a promise. We will tell you if it was kept.

A renewal, a vendor you suspect, a purchase you are about to make — the paperwork is all we need to start.

Request an Investigation