Software engineering
We design and build software with maintainability, sensible permissions, and security considered from the start.
InnovaGuard is a small team of software engineers and security people building tools with privacy in mind. We like good software, careful security, and not collecting information we do not need.
Our focus is privacy and security software that is understandable, useful, and built with care. We pay attention to what software can access, what it sends, and what happens when something goes wrong.
We are not interested in making privacy sound mysterious. Good security should be something people can actually use.
We design and build software with maintainability, sensible permissions, and security considered from the start.
We work on tools that help people understand, restrict, and protect the software running on their systems.
Security claims deserve scrutiny. We look for weaknesses, questionable assumptions, and the stuff that is easy to overlook.
We are serious about security. We are less serious about agreeing on who gets the last word in a code review.
Computer science major with 8 years of experience in software engineering. Focused on turning ideas into software that works without creating a second problem somewhere else.
Builds the interfaces people see while staying heavily focused on the security tools and systems working behind the scenes. Basically, if it looks simple, someone probably worked very hard to make it that way.
Security expert with 5 years of experience auditing security tools. Specializes in looking closely at how tools actually behave instead of taking the word "secure" at face value.
Cybersecurity major with 7 years of experience across security and software engineering. Interested in how systems fail, how they can be abused, and how to make those failures harder to reach.
A security tool focused on giving applications clearer boundaries around what they can access.
QUARANTINE is being built around a simple idea: software should not automatically get access to everything on a system just because it asked nicely.
Clearer limits around what applications can access and interact with.
Designed with threat modeling, testing, and careful defaults in mind.
Keep unnecessary data collection and unnecessary access out of the picture.
Early development means testing, breaking things, fixing them, and repeating the process.
There is no magical security checklist. These are simply the standards we want our work to live up to.
If we do not need information, we should not need to collect it.
People should not need a security degree to understand what a tool is doing.
Threat models, audits, testing, and uncomfortable questions are part of the job.
We can care deeply about security and still make a dumb joke on the company website.
Take a look at the code, projects, and experiments on GitHub.