File Structure
Xio is organized as a full-stack application with a backend and frontend running in separate directories. Here's a breakdown of the structure:
bashCopyEditxio/
├── backend/ # Core logic, file processing, embeddings, vector storage
│ ├── services/ # LLM, embeddings, and integrations
│ ├── routes/ # Logic for handling chat, file parsing, and workspace actions
│ └── utils/ # Helpers for chunking, cleaning, formatting
├── frontend/ # React-based UI for chat, workspace management, uploads
│ ├── components/ # Reusable UI elements
│ ├── pages/ # Page-level views (chat, workspace, settings)
│ └── styles/ # Tailwind and global styles
├── docker-compose.yml
├── .env
└── README.md
Each service is modular, so you can easily swap out parts like the embedding logic or vector database without changing the rest of the app.
Last updated