DryTrix is a small lab of practical, open-source tools: apps you can self-host, run locally, and ship fast.
Focus areas: productivity, maker tools, and data-driven utilities—built with developer ergonomics and real users in mind.

Want to collaborate, request a feature, or report a bug? Open an issue or start a discussion.

A self-hostable time tracking app for individuals and small teams.

• Website: https://timetracker.drytrix.com
• Source: https://github.com/DRYTRIX/TimeTracker
• Container: ghcr.io/drytrix/timetracker

Typical use cases

• Track work time per project/client
• Lightweight reporting and exports
• Simple self-hosting for privacy (no SaaS lock-in)

A digital pattern design tool focused on sewing pattern creation/editing.

• Website: https://patternsoft.drytrix.com

Goal

• Make pattern drafting and editing approachable and affordable
• Keep it open-source and feedback-driven (built together with real sewing workflows)

A bike road quality app with an approval flow for adding roads.

• Website: https://ridesafe.drytrix.com

Goal

• Help cyclists discover better routes based on road quality signals
• Community-driven contributions with moderation/approval

DryTrix projects aim to be:

• Open-source first (transparent, forkable, hackable)
• Self-host friendly (Docker where possible, minimal ops pain)
• Opinionated but pragmatic (defaults that make sense, configurable when needed)
• Built for usefulness (not demos—tools meant to be used)

This varies per repo, but you’ll commonly see:

• Docker / Docker Compose
• Modern web stacks (frontend + backend)
• CI/CD via GitHub Actions (in most repos)
• Sensible defaults + reproducible builds

Check each project’s README for the exact stack and setup instructions.

DryTrix is an org with multiple projects. To get started:

1. Pick a project from the list above.
2. Open the project repository (if public).
3. Follow the project’s README for installation and configuration.

Many DryTrix projects support a standard Docker workflow:

• Pull image (if available on GHCR)
• Configure environment variables
• Run with Docker Compose
• Access via local URL / reverse proxy

Tip: If you run multiple DryTrix apps, put them behind a reverse proxy (Caddy / Traefik / Nginx) and give each app its own subdomain.

• Projects typically follow SemVer (where applicable).
• Releases and containers (if provided) are published per-project.
• Changelogs live in each repository.

Contributions are welcome across all DryTrix projects.

1. Open an issue describing the bug/feature.
2. If it’s a feature: explain the use case and expected behavior.
3. Submit a PR:
   • Keep changes focused
   • Include screenshots for UI changes
   • Include tests where feasible

• Improve docs (setup steps, troubleshooting, screenshots)
• UI/UX polish (spacing, accessibility, mobile behavior)
• Export/import features
• Performance improvements and profiling notes

When reporting a bug, include:

• Project name (TimeTracker / PatternSoft / RideSafe)
• Steps to reproduce
• Expected vs actual result
• Screenshots / screen recordings (if UI)
• Logs (backend + browser console)
• Environment:
  • OS
  • Browser
  • Docker version (if used)
  • Commit hash / release version

Feature requests are best when they include:

• The problem you’re trying to solve
• The workflow (what you do today, what you want instead)
• Any references (screenshots, competing tools, examples)
• Priority (nice-to-have vs must-have)

If you discover a security issue:

• Please do not open a public issue immediately.
• Use the repository’s security policy if available, or open a private report if the platform supports it.

• Use GitHub Issues for bugs and actionable tasks
• Use GitHub Discussions (if enabled) for ideas, feedback, and questions

Each project defines its license in its own repository.
Check the LICENSE file in the relevant project for details.

• DryTrix websites:

  • TimeTracker: https://timetracker.drytrix.com
  • PatternSoft: https://patternsoft.drytrix.com
  • RideSafe: https://ridesafe.drytrix.com

• GitHub:

  • https://github.com/DRYTRIX

DryTrix evolves through real usage and community feedback. Typical roadmap themes:

• Better onboarding (demo data, guided setup, clearer docs)
• Export/reporting improvements
• UI/UX modernization (accessibility, responsiveness, keyboard workflows)
• Self-hosting improvements (compose templates, reverse-proxy examples)
• Performance and stability

If you want to help steer direction, open a discussion with:

• what you’re building,
• how you’d use the tool,
• and what’s currently missing.

Made with pragmatism. Built for real workflows.