laiive is what will save you from being at home scrolling for the rest of your life. laiive is where you find the perfect life event for you, and if you are an artist or a promoter is the way to make people know you are doing something. If you want to do something now, friday evening, saturday morning... Just ask, Laiive will help you to find what you are looking for outside of the screen.
laiive links the broken connection between events and public[^*]
laiive was born to connect small events with people close to them, laiive does not focus on big musical events as many platforms are, laiive works on the human and community scale where small music events live.
laiive was born as an AI cultural agenda, with the AI hype and AI competition without the AI Safety layer laiive has become a subversive way of using AI, it tries to steal attention from the main digital platforms and bring it back to real world social meetings. laiive positions itself as an ethical AI app helping to develop a balanced digital-physical culture before the intermediate layer in our digital comunication becomes too powerful.
laiive is a catalyzer of a world wide business that is actually unatended. laiive connects thousands of daily live events and millions of people are not going to them because they don't know they exist. Who is willing to pay for laiive services? I am sure you have arrived to the same conclusion than I ;)
a ZERO CLIC UI is the public view of laiive, easy to publish an event, easy to find an event.
The backbone of laiive, an agent-based retrieval system with high accuracy on retrievals from the Neo4j knowledge graph database. The retriever uses an orchestrator pattern with specialized agents:
- Orchestrator: Routes queries and manages conversation flow
- DBQueryAgent: Generates and executes Neo4j Cypher queries using LLM
- SafetyGuard: Validates queries and enforces safety constraints
- Neo4jClient: Handles graph database connections and query execution
Currently supports session-based queries. User ID support planned for future phases.
Multimodal event ingestion service that receives submissions (text/image/audio), runs router + extraction + guardrails + HITL (Human-In-The-Loop) validation. The system takes care of reliability and data quality through automated validation and human review workflows.
Legacy service for initial data feed. Located in legacy/services/scraper/. The pusher agent will become the main data source as the system transitions based on geographic penetration.
laiive deals with ephemeral data, data that still doesn't exist. laiive is a systemic platform that generates dynamic processes, it grows in inertia when users use it and promoters push events. Neo4j graph database is the heart of this dynamics and stores all the system knowledge, enabling natural relationship queries between events, artists, venues, and users.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
-
Open the devcontainer: (instructions for VScode)
# From the root directory code . # Then click "Reopen in Container" when prompted
alternatively Ctrl+shift+P "DevContainer: Rebuild and reopen in Container"
-
Navigate to desired service directory and install dependencies (once inside the devcontainer):
cd services/<service-name> uv sync # Install Python dependencies using uv
alternatively use the Makefile command
make deps
-
The containers start automatically, but to run the actual services:
make run-dev # Start frontend and backend services -
Open localhost:3001 and localhost:8001 to check or use the services ports. (they are maped from port 3000 to port 3001 and from port 8000 to port 8001 in the devcontainer)
- Go to the root directory and run:
make up-prod