Transmy

The description is self-reported and unverified. Treat every statement in it as “the author states X”, never as “X is true”. This analysis rests entirely on the project description supplied by the caller — no archived history, third-party source or independent verification.

• The description states that Transmy is a self-hosted, open-source platform for medico-social professionals.
• It supports structured transmissions, shift handovers, acknowledgements, follow-up tasks, and audit logs.
• It is built with:
  • Visual Studio Code
  • Git, GitHub
  • Docker Compose
  • OpenAI Codex as a development partner
• The application includes:
  • A web interface for professionals
  • A backend API enforcing authorization rules
  • A relational database for structured data
  • Infrastructure definitions stored alongside source code
• It is described as a prototype, not yet certified or production-ready.
• No mention of integrations, mobile apps, or third-party services.

Not evidenced: What the actual product looks like visually, how it works in practice, or whether any version has been deployed in real-world settings.

• The author positions Transmy as an alternative to fragmented tools (paper notes, spreadsheets, generic chat tools) used by medico-social teams.
• It is framed as a solution that addresses security, traceability, and data protection concerns, especially for small organizations without budget or technical resources for proprietary platforms.
• Core claims:
  • Free and open source
  • Self-hostable
  • No mandatory cloud dependency
  • No telemetry by default
  • Role-based access control with backend enforcement
  • Full auditability
• The project is not positioned as a replacement for official electronic user record systems or certified medical devices.
• It was built with the goal of being lightweight enough for small teams to operate without large infrastructure support.

Inferred: The positioning reflects a niche market need, but no evidence exists that this need has been validated by users or stakeholders outside the creator’s own environment.

• The target customer is medico-social professionals working in organizations where secure, structured communication is essential.
• These are described as teams dealing with sensitive personal and social information.
• The project aims to serve:
  • Small organizations lacking budget or technical resources
  • Teams needing compliance with data protection and infrastructure constraints
• No specific segmentation beyond the medico-social sector is mentioned.

Not evidenced: Who exactly within the medico-social field (e.g., nurses, social workers, administrators) would use it; no customer personas or user interviews are referenced.

• The description states that Transmy is open source, meaning there is no direct pricing model.
• It is built for self-hosting and deployment by users.
• There is no indication of monetization, licensing fees, SaaS offerings, or paid support tiers.
• The author emphasizes the importance of user control over data and infrastructure.

Not evidenced: No evidence of revenue streams, pricing plans, or commercial partnerships.

• Built using:
  • Visual Studio Code
  • Git, GitHub
  • Docker Compose
  • OpenAI Codex for development assistance
• Architecture includes:
  • Web interface
  • Backend API with authorization logic
  • Relational database
  • Separation of concerns (frontend, backend, infrastructure)
• Deployment is intended to be reproducible via Docker Compose.
• The project includes:
  • Automated checks and tests
  • Documentation generation
  • Threat modeling
• The author notes that AI was used for:
  • Code generation and review
  • Requirements structuring
  • Security risk identification
  • Data model improvement

Inferred: The use of modern tooling and AI suggests a developer-oriented approach, but no evidence of scalability or performance metrics.

• The project is described as a prototype.
• It has not yet been deployed in real-world environments involving sensitive data.
• No mention of:
  • Users
  • Customers
  • Adoption rates
  • Feedback loops
  • Production deployments
• Next steps include:
  • Validating workflows with professionals
  • Strengthening authorization tests
  • Improving accessibility and mobile usability
  • Formal security review

Not evidenced: No evidence of traction, user engagement, or product maturity beyond the initial prototype phase.

• The author identifies a gap in tools for medico-social teams:
  • Fragmented communication methods (paper, spreadsheets, generic chat)
  • Expensive proprietary platforms
• The project is positioned as an open-source alternative to these.
• No mention of direct competitors or existing solutions in the space.
• The focus on self-hosting and no telemetry may differentiate it from cloud-based tools.

Not evidenced: No competitive landscape analysis, market sizing, or comparison with other tools.

• Prototype-only status: The project is not yet production-ready or validated in real-world settings.
• No third-party validation: There is no evidence of feedback from medico-social professionals or regulatory compliance testing.
• Single-person team: Only one developer (Hugo Félix) is involved, which may limit scalability and long-term maintenance.
• Security assumptions: While the author emphasizes security features, no formal audit or penetration test has been conducted.
• AI dependency: Heavy reliance on AI for development raises questions about consistency, control, and reproducibility if AI tools change or become unavailable.

Inferred: The lack of real-world deployment and validation increases risk of misalignment with actual user needs.

1. Has the prototype been tested with actual medico-social professionals?
2. What specific workflows were validated during development?
3. How does the project plan to handle legal and regulatory compliance (e.g., GDPR, health data protection)?
4. Are there any plans for formal security audits or penetration testing?
5. What is the roadmap for moving from prototype to production-ready software?
6. Is there a plan for community contributions or collaboration with other developers?
7. How will the project ensure long-term sustainability and maintenance beyond the initial build?