ALIISMAIL
Back to projects
Investerna (استثمارنا)

Investerna (استثمارنا)

Live site

Gallery

Select a screen to enlarge

Summary

People who want to invest, but do not run the deals, meet in one place: a catalog of projects, a request to join, and a private community chat after an admin approves them.

Overview

Investerna is a backend for an investment community platform. It gathers people who want to invest but do not manage deals themselves into one place: a catalog of projects, a request to join, and a private community chat for each project once an admin approves them. The stack is NestJS, TypeScript, PostgreSQL, and Prisma. Clients talk to REST under /api/v1. Chat also uses WebSockets. Arabic and English are stored side by side; public responses follow the Accept-Language header and default to Arabic. The domain is a simple chain: a category holds projects, each published project has one community, and people become members of that community.

Technologies

NestJSTypeScriptPostgreSQLPrismaWebSockets

Features

  • Investors and admins

    Investors sign in with Google. They browse projects, apply to invest, chat inside communities they belong to, and open a private support chat with the team. Admins sign in with email and password. What they can do depends on a role. Permissions are by area: ACCOUNT, COMMUNITY, INVESTMENT, CHAT, and CONTENT. Admins can also manage other admins, roles, and user status (ACTIVE, SUSPENDED, BANNED).

  • Catalog

    Categories group investment types. Projects sit under a category and carry the offer: titles, location, description, minimum investment, expected revenue, risk level, investment period, and how revenue is paid out. Each project can have images and documents, and a status of DRAFT, PUBLISHED, CLOSED, or ARCHIVED. Public visitors only see published projects. Admins create and edit categories and projects, upload files, and change status.

  • Investment requests

    A user applies to a specific project with a reason and phone number. The request moves through PENDING, APPROVED, REJECTED, or CANCELLED. The user can cancel while it is still pending. When an admin approves, the user is added to that project's community. A reject does not add them. After approval, the user can see the projects they were accepted into.

  • Communities

    A community is the group tied to one project. Members can list their communities, open details, and leave. Admins can list communities, add or remove people, ban a member, archive a community, or delete it. Membership is not open. Someone is in a community only after an approved investment request, or because an admin added them.

  • Chat

    Community chat is only for active members. They can send text, images, and files, mention someone, reply in a thread, edit or delete their own messages, see who is online, and report a message. Support chat is one private thread per user with the admin team. Admins with chat permission can delete any message, pin a message, ban someone from the community, and work a report queue (PENDING, RESOLVED, DISMISSED). They also reply in support chats. New messages can trigger in-app and push notifications.

  • Content and settings

    Public pages are managed as content, not code. Admins edit the hero, statistics, about, features, work steps, client reviews, FAQ, contact, terms, and privacy. The public API only reads those sections. A single settings row holds platform values that are not page copy. Today that is the WhatsApp number. Anyone can read it. An admin with CONTENT permission can update or clear it.

  • Accounts, files, and notifications

    Users update their own profile (email, username, full name, avatar) and can view another user's public profile. Admins list and edit users and can suspend or ban them. Notifications cover chat messages, mentions, support replies, system events such as an investment decision, and optional revenue updates. Each person can turn types on or off per channel. In-app is the main channel. Push works when Firebase is configured. Email is reserved. Uploaded files (avatars, project media, chat attachments) are stored on the server disk and served through the files API.

  • Analyser

    Portfolio views for investors, and admin reports on users and projects, are in the requirements. There is no analyser module in the codebase yet.