Keep decisions visible
People should be able to understand what software is doing and choose when it acts.
01 / 06Swipe or use arrows to explore
Independent company · Winnipeg, Manitoba
Useful products. Clear foundations.
We build focused apps and open tools that give people more control over their data and technology.
Projects
Our projects
6 current projects across products, public foundations, and research.
Commercial product
Your memories, yours to keep.
Mochilada is the current product.
Preparing for release
Mochilada
Browse the social media archives you already have.
Local processingNo direct account connection
Public foundations
Foundations
Open-source tools for human-led AI work and modular TypeScript services.
Research & development
What comes next
Prototypes and research in progress. Each project page explains its current scope.
Public engineering source: Sentzunhat on GitHub.
Company
An independent software company in Winnipeg.
Sentzunhat builds focused apps and open-source engineering tools.
The work grew from projects in local-first software, service architecture, and infrastructure.
Our vision
Focused products. Shared foundations.
Each product starts with a specific problem. Shared tools and engineering practices help us carry useful lessons into the next one.
The aim is a family of focused products, not one platform built to do everything.
Principles
How we build
The choices behind our work.
Keep data portable
Privacy and ownership should be supported by the product’s design, not only its policy.
Be clear about status
We label what is released, what is a prototype, and what is still being researched.
Behind Sentzunhat
Why I started Sentzunhat
I started Sentzunhat to build software that gives people more control over their data and technology. I like untangling systems that have become hard to use or maintain.
I look for the simplest design that solves the real problem and lasts over time.
Start with the problem
Before choosing a tool or adding a feature, I want to understand what someone is trying to do and where the friction comes from.
Build for the next change
I work across product software and engineering foundations. I prefer focused tools, visible boundaries, and decisions that are easy to revisit.
Solve the real problem. Leave the system easier to understand.