ECHO is a digital platform built to address the fragmentation of the cultural market. Before ECHO, artists had no unified way to reach buyers, service requesters had no reliable directory of creative talent, and venue managers had no centralized tool to find performers or fill event slots. ECHO solves this by bringing all three parties into a single, structured marketplace.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/HelenaLM32/ECHO/llms.txt
Use this file to discover all available pages before exploring further.
The problem ECHO solves
The cultural and arts sector has historically been fragmented: talent discovery happens through word of mouth, contracting is informal, and event logistics are managed across disconnected tools. ECHO centralizes these workflows — from first discovery to final review — on a single platform built specifically for the sector.Who uses ECHO
ECHO is built around three actor types, each with a distinct role on the platform:Content Creator
Artists and creative professionals who publish services, build portfolio projects, and apply to events at venues.
Service Requester
Individuals and organizations that browse listings, place orders, and hire creative talent for their needs.
Venue Manager
Owners and operators of cultural spaces who list venues, organize events, and connect with content creators.
Core platform capabilities
ECHO provides a set of interconnected features that support the full lifecycle of a creative engagement:- Marketplace listings — Creators publish service offerings with descriptions, pricing, and media. Requesters browse and filter by category.
- Portfolio projects — Creators showcase past work through project entries that serve as a public portfolio.
- Service listings — Structured service offers with defined scope, price, and delivery terms.
- Events and venues — Venue managers register physical spaces and organize events. Creators can apply to participate.
- Orders with messaging — Requesters place orders against service listings. Both parties communicate in-platform throughout the engagement.
- Reviews — After an order completes, both the creator and the requester can leave a review. Venue reviews are also supported.
- Disputes — A structured dispute system allows either party to flag issues with an order and escalate for resolution.
How the three parties interact
The core interaction loop on ECHO follows a simple pattern:- A Content Creator publishes a service listing or portfolio project.
- A Service Requester discovers the listing, browses the creator’s profile, and places an order.
- Both parties communicate via in-platform messaging to align on scope and delivery.
- Once the work is delivered, both parties leave reviews that build their public reputation on the platform.
- If issues arise, either party can open a dispute to seek resolution.
Technology stack
ECHO is built on a modern, containerized stack:| Layer | Technology |
|---|---|
| Frontend | React (Vite) |
| Backend | Spring Boot (Java) |
| Database | MariaDB |
| Authentication | JWT + Google OAuth2 |
| Deployment | Docker Compose |
Explore key features
Marketplace
Browse and publish service listings and portfolio projects.
Orders and payments
Place orders, exchange messages, and manage the delivery lifecycle.
Events and venues
Register spaces, organize events, and connect with creators.