OWNOMI

About Ownomi

Ownomi started with a simple question: once you have your genomic data, what can you actually do with it?

Sequencing and consumer genetic testing are making personal genomic data increasingly accessible. But receiving the data is only the beginning. Files such as VCF can be difficult to work with, useful tools are scattered across different projects, and exploring the data often means uploading it to another service.

Ownomi is an attempt to make another approach practical: give people a private workspace where they can explore their own genomic data with open-source tools while keeping control of the environment in which those data live.

Built from an infrastructure perspective

Founder of Ownomi

Ownomi is founded by a technology professional with a background spanning DevOps, application support, systems administration, cloud infrastructure, AWS, automation, databases and SQL, and the operation of production systems.

That background shapes the project. Ownomi approaches personal genomics first as an infrastructure and data-ownership problem: how to assemble useful tools into a working environment, make the workflow understandable, and avoid unnecessary movement of sensitive genomic data.

The goal is not to replace geneticists, physicians, or genetic counselors. Ownomi does not provide medical diagnosis or clinical interpretation.

Instead, the goal is to help people who already have genomic data build an environment they can understand, control, and continue using as their questions and the available evidence evolve.

Why Ownomi

Genomic data are unusually personal, but they are also something you may want to return to for years.

New questions appear. Tools improve. Public databases change. Research develops. The underlying genome remains largely the same.

That makes continued control over your data important.

Ownomi is being built around a simple principle:

Your genomic data should be something you can explore without giving up control of them.

Today Ownomi is an early-stage, founder-led project. The current service is intentionally hands-on: understand what data a person has, agree on an appropriate workflow, configure the environment, and help the owner learn how to use it.

As the project develops, that principle—user control over the data and the environment—should remain at its core.