Live demos: wonmor.io/demo/: every demo runs the real interface on sample or open data, in the browser, with nothing to install.
Wonmor is a self-funded brand from Uzbekistan that builds and supports the dtwin ecosystem: a personal planner anchored to the five daily prayers, an open-source Uzbek keyboard, and the tools and infrastructure around them. It is not a company: there is no legal entity, no board and no investors. One founder builds the products, working with AI agents, and every change goes through a pull request, continuous integration and a human merge.
The product code lives in github.com/dtwinuz. This organization holds the Wonmor site and the shared, open material around it.
| Repository | What it holds | Licence |
|---|---|---|
| wonmor.io | Source of wonmor.io in English, Uzbek and Russian: Astro, deployed by GitHub Actions on every merge | — |
| research | Reproducible material behind the posts on wonmor.io/research | MIT |
| uz-open-data | Open data for Uzbekistan: 2,289 mosques from OpenStreetMap, the Uzbek Cyrillic to Latin table. Explorer at wonmor.io/demo/uz-open-data | MIT (data: ODbL) |
| deploy-kit | Zero-downtime static site deploys: releases, symlink swap, Caddy reload, rollback | MIT |
| design-system | Wonmor design tokens (@wonmor/tokens): colour, type, spacing, motion. Playground at wonmor.io/demo/design-system |
MIT |
| brand | The Wonmor mark, lockups, colours, brand film and the rules for using them | See repo |
| open-source-fund | The planned Wonmor Open Source Fund. Not accepting applications yet. | See repo |
| muhr | Planned: timestamp proofs for files, anchored to Bitcoin through OpenTimestamps and an open log. No tokens. Demo at muhr.wonmor.io | Apache-2.0 |
| sanad | Planned: verifiable certificates and badges (W3C Verifiable Credentials 2.0), checked offline. No tokens. Demo at sanad.wonmor.io | Apache-2.0 |
| shaffof | Planned: charity reports sealed with Merkle roots, and a sourced zakat calculator after scholar review. Never handles money. Demo at shaffof.wonmor.io | Apache-2.0 |
| .github | This profile, contributing guide, code of conduct and security policy | — |
Products with a public address. Release levels are explained on wonmor.io/responsible-release-policy.
| Product | What it is | Status | Links |
|---|---|---|---|
| dtwin | A personal life planner whose day is anchored to the five daily prayers | Beta | dtwin.uz |
| bitg | An open-source Uzbek keyboard that converts text to the 2026 Latin alphabet as you type, on Windows, Linux and macOS | Beta | bitg.uz · source |
| TeleTwin | A company layer for Telegram: work chats and channels kept apart from personal ones | MVP | tele.dtwin.uz · source |
| Gateway | One control point between AI agents and the systems they are allowed to use | MVP | gateway.dtwin.uz |
| Tunnel | Publishes a service running on your own machine at a public address, on infrastructure we run ourselves | MVP | tunnel.dtwin.uz |
| Fam | A self-hosted bug-capture tool: one link carries the video, logs and context of a problem | Preview | fam.dtwin.uz |
| operobot | An outbound calling assistant designed around Uzbekistan's rules for advertising calls | Prototype | operobot2.dtwin.uz · source |
| shop | An experiment: a catalogue for small clothing stores | Experiment | shop.dtwin.uz |
| gym | An experiment: an open-source workout diary | Experiment | gym.dtwin.uz · source |
| med | An experiment: a study platform for medicine | Experiment | med.dtwin.uz |
Every product has its own page at wonmor.io/products.
- Every change is a pull request. CI builds and checks it; merges are squash-only, into a protected
main. - Security by default. Secret scanning with push protection, Dependabot, CodeQL and private vulnerability reporting are on for every repository.
- Facts with sources. Every number and claim on wonmor.io links to where it comes from. Planned work is labelled as planned.
- Charter: seven principles that decide how we build, release and look after the products
- Research and Engineering: what we are working on and how to reproduce it
- Changelog: every release across the ecosystem, also as RSS
- Open source: which repositories are public, under which licences, and how to contribute
- Security: how to report a vulnerability privately
Telegram: t.me/xnosir. Bugs and ideas go to an issue in the repository they belong to; questions go to Discussions. Please do not report vulnerabilities in public issues; see the security policy.