Ovumcy App
The mobile app is the no-server local-first path. Core use works without an account, sync, or managed hosting, and health data stays on-device by default.
About Ovumcy
Private cycle tracking across app, self-hosted web, sync, and managed continuity
Ovumcy is a privacy-first cycle tracking product family with four clear operating modes: a local-first mobile app, a full self-hosted web deployment, a self-hosted sync backend for the app, and managed hosting for people who want sync plus managed convenience.
The point is not to collapse those paths into one vague promise. Each route has a different trust, storage, and operations story, and the site should make that explicit instead of forcing everyone into a single self-host-only narrative.
What Ovumcy is
One brand, clear product shapes
The Ovumcy ecosystem is organized around distinct product models instead of hiding everything behind one ambiguous marketing layer.
Ovumcy self-hosted web
The full self-hosted web product runs as a single Go service with a server-rendered browser UI, optional phone home-screen install, SQLite as the baseline, and PostgreSQL as an advanced operator path.
Ovumcy self-hosted sync
The self-hosted sync backend exists for app users who want encrypted backup, restore, and multi-device sync on their own server without turning that server into the full browser-based web product.
Managed hosting
Managed hosting is the separate path for people who want sync plus managed-only convenience. It should be evaluated as its own surface, not confused with app-only use or ordinary self-hosting.
Why Ovumcy exists
Useful cycle tracking without vendor lock-in
Many cycle trackers center cloud accounts, opaque telemetry, or product decisions that make portability feel secondary. Ovumcy exists to keep day-to-day usefulness and long-term control visible at the same time.
Readable daily product
Cycle tracking still needs to feel calm enough for everyday use, not like an operator console wearing health-product colors.
Inspectable deployment model
Storage, secrets, reverse proxy expectations, backups, and release tags should all be visible before the first deployment starts.
Portable records
Export and backup workflows should stay ordinary parts of the product story instead of awkward emergency exits.
Who it serves
Designed for people who verify before they trust
Ovumcy fits people who care about product usability and infrastructure truth in the same decision.
Privacy-conscious individuals
People who want cycle tracking without ad-tech, forced vendor accounts, or invisible telemetry assumptions.
Self-hosters and developers
Operators who want a reviewable stack, public releases, a narrow deployment baseline, and an honest ops story.
App users who still want their own sync infrastructure
People who prefer the mobile app experience but still want encrypted backup, restore, and multi-device continuity on a server they control.
People who want continuity without self-hosting ops
Users who would rather choose managed hosting than operate servers, while still caring about a privacy-first product story.
Ovumcy ecosystem
Useful links
These links point to the live Ovumcy surfaces that already exist today.