Skip to main content

Project Master Plan

Organic Sharing and Management Platform​

Status:Living Document (Updated May 2026)
Project:Elo Orgânico
Main Scope:Digitalization and Optimization of the Organic Product Sharing Chain.

Phase 1: Functional Proposal and Scope​

This document details the development of a robust digital platform for the optimized management of sharing organic products. Our strategic goal is to migrate manual processes based on spreadsheets and messages to a centralized, high-performance, and scalable system.

1.1. Scope and Operational Flow​

The solution is architected as an integrated environment pair within the Instance Scope:

  • @elo-instance/api (Backend): Fastify REST API handling business logic, data persistence, and bank integrations.
  • @elo-instance/web (Frontend): React SPA containing both the Administrative Panel (for cycle management) and the Customer Shop (for order execution).

End-to-End Cycle Flow:

  • Cycle Configuration: The administrator defines and schedules purchase windows (cycles) through the @elo-instance/web admin interface. [STABLE]
  • Product Ingestion: A plain text list of products is processed by an Intelligent Parser in the frontend. [WIP - Refining Logic]
  • Opening of Purchases: The structured catalog is automatically enabled for members in the @elo-instance/web shop. [STABLE]
  • Order Execution: Members assemble custom baskets and submit their orders. [STABLE]
  • Payment Processing: Direct integration with EFI Bank API for Pix payments. [WIP - Technical Specification Stage]
  • Confirmation: The system performs bank reconciliation and confirms the order automatically. [WIP]

1.2. Architecture & Technical Guidance​

All architectural decisions, project structure, and technology stack details are centralized in the Architecture Overview.

Phase 2: Operational Guidelines & Standards​

All development workflows, coding standards, and quality requirements are defined in the Style Guide.

Phase 3: Cost Estimation​

3.1. Cost Breakdown​

The "Self-Hosted" strategy on Hetzner Cloud provides a highly favorable and predictable cost-benefit ratio.

Cost CategoryDetailsEstimated Monthly Cost
Hosting (Hetzner Cloud VPS)High-Performance Server (Linux VPS) covering current and future containers.€5.00 to €7.00 (Fixed)
Database & CacheUtilization of the VPS's own resources (MongoDB/Redis).Zero Additional Cost
Payment Gateway (EFI Bank)Fixed fee per received Pix transaction.Variable
Domain and DNSAnnual registration and maintenance.Standard Annual Cost

3.2. Financial Conclusion​

The selected architecture ensures total predictability of infrastructure costs. The fixed monthly cost is extremely low, ensuring the project's long-term financial sustainability.

Phase 4: Brand Identity & Design System​

The strategic development of the Elo Orgânico brand identity is consolidated in the specialized design documentation.

Phase 5: Operational Flowchart​

1. Preparation Stage (Administrator)​

  • Access: The Administrator accesses the management features within @elo-instance/web.
  • Data Ingestion: The Admin pastes raw product data. The frontend structures it and saves it via @elo-instance/api.
  • Cycle Opening: Admin sets dates and activates the cycle.

2. Shopping Stage (Customer)​

  • Navigation: The Customer accesses the shop features within @elo-instance/web.
  • Cart & Checkout: Assembly of baskets and order submission.
  • Payment: Unique Pix QR Code generated by @elo-instance/api via EFI Bank integration.

3. Closing Stage (Admin/System)​

  • Closing: Automatic blocking of new orders at the deadline.
  • Consolidation: Admin accesses consolidated reports in @elo-instance/web to finalize logistics with suppliers.

Phase 6: Long-Term Scaling to SaaS (Post-v1.0)​

6.1. Strategic Vision​

IMPORTANT: The current focus is strictly on Phase 1-5 to deliver a polished single-instance product (@elo-instance/*). SaaS development will only commence after the core application is fully operational.

The long-term goal is to evolve into a Multi-tenant SaaS Platform:

  • Portal Scope (@elo-portal/web & @elo-portal/api): A singleton global entry point for onboarding and discovery.
  • Multiple Instance Pairs (@elo-instance/api & @elo-instance/web): Each community receives its own isolated environment pair.
  • Core Libraries (@elo-instance/core & @elo-portal/core): Domain-specific source of truth (SSOT) for each scope.

6.2. Key SaaS Features​

  • Tenant Isolation: Independent data and configuration for each community instance.
  • Producer Self-management: Direct inventory and pricing management for producers.
  • Subscription Management: Tiered service levels managed via @elo-portal/api.

6.3. Architectural Evolution​

  • Multi-Instance Deployment: Automated spinning up of @elo-instance/* containers per tenant.
  • Dynamic Routing: Global load balancer routing users to their specific community instance.