Selia is a technology-driven company focused on improving mental health and well-being. We develop innovative tools and platforms to connect users with specialists and provide personalized support.
A platform designed for users to manage their mental health journey. It allows users to schedule appointments, access personalized mental health content, interact with specialists via chat and video calls, and track their progress.
A comprehensive tool for mental health specialists to manage their practice. It provides features for scheduling appointments, conducting video sessions, chatting with patients, and tracking patient progress over time.
The core backend service that powers all Selia applications. It handles data management, user authentication, appointment scheduling, communication tools, and integration with external services.
A dedicated service for managing secure and seamless payment transactions within the Selia platform. It supports payment processing, subscription management, invoicing, and integration with third-party payment gateways.
To make mental health care accessible, efficient, and effective through cutting-edge technology.
- Selia Users App: A platform for users to connect with specialists, access personalized content, and manage their mental health journey.
- Selia Specialists App: A tool for specialists to manage appointments, communicate with users, and conduct sessions via video calls.
- Frontend: JavaScript, Vue.js 2/3, Capacitor.js (iOS & Android), Lit 2
- Backend: Node (NestJS), Python (Django)
- Databases: PostgreSQL, MongoDB, Supabase
- DevOps: AWS (Elastic Beanstalk, EC2, RDS, SES), GCP (Bigquery, Firebase), GitHub Actions...
Selia is a private organization, and contributions are limited to authorized team members. If you are part of the Selia team, please follow the guidelines below when working on any repository.
Branches must follow the naming convention: / Examples:
- feature/add-login
- fix/resolve-bug-123
- chore/update-dependencies
We use Conventional Commits to maintain consistency and clarity in our commit history. The format is:
<type>(scope): <description>
[optional body]
[optional footer(s)]
Common Commit Types
- feat: A new feature
- fix: A bug fix
- docs: Documentation changes
- style: Changes that do not affect code logic (e.g., formatting)
- refactor: Code changes that neither fix a bug nor add a feature
- test: Adding or updating tests
- chore: Maintenance tasks (e.g., dependencies)
Examples:
- feat(auth): add user login feature
- fix(video-call): resolve connection issue
- docs(README): update contribution guidelines
For more information about Conventional Commit please visit the following link.
- Create a branch following the naming convention: git checkout -b /
- Make your changes and commit them following the Conventional Commits format.
- Push the changes to the repository: git push origin /
- Open a pull request and notify your team lead for review.
You can find all our repositories here
For internal inquiries or support, please reach out through the organization’s official communication channels.
