WebApp is a schema-driven application template for building internal tools, operational dashboards, and reporting systems. Models, fields, views, and insights are declared as data, allowing the same frontend and backend to adapt to different business domains with minimal custom code.
- Highlights
- Architecture
- Prerequisites
- Quick start
- Database backup and restore
- Development commands
- Documentation
- Security note
- License
Declarative core
- Declarative Kanban, list, form, and calendar views
- Reusable field components, relationships, avatars, and localized labels
- Insights dashboards: KPIs, gauges, and charts from declarative definitions
Search
- Natural-language global search: an AI interpreter turns questions into validated, typed search plans, with automatic fallback to plain text when no provider is configured
- PostgreSQL full-text search (
tsvector/ts_rank) and trigram (pg_trgm) indexes, tuned to stay fast at 100,000+ records per model - Contextual, in-app help for the search bar
Security and accounts
- Access/refresh token session renewal with rotation and reuse detection
- CSRF-protected refresh cookies with absolute session expiration
- Session activity tracking and read-only user log reporting
Platform
- In-app and browser push notifications
- Read-only MCP reports for authorized users
- Attachment storage with authenticated previews
- FastAPI, GraphQL, SQLModel, PostgreSQL, and Alembic
- Preact, Signals, Tailwind CSS, Vite, and CJ Router
Browser
└─ Preact dashboard
├─ GraphQL API ── FastAPI services ── PostgreSQL
├─ Attachment API ── local filestore
└─ MCP endpoint ── read-only reports
The canonical model definitions live in:
backend/app/domains/system/data/system_models.json— models and fieldsbackend/app/domains/system/data/system_model_schemas.json— view layouts
- Python 3.11 or newer
- PostgreSQL 15 or newer, including the
pg_dumpandpg_restoreclient tools - Node.js 20.19+ or 22.12+ and npm
- Docker with Docker Compose, if you prefer containerized PostgreSQL
cd backend
cp .env.example .env
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
# Start the bundled PostgreSQL service; skip this if you use another server.
docker compose up -d db
python scripts/setup_database.py
uvicorn main:app --reloadThe API is available at http://localhost:8000, with GraphQL at
http://localhost:8000/graphql.
scripts/setup_database.pyrecreates the configured database. ReviewDATABASE_URLbefore confirming the operation. A successful run creates the current schema and seed data, installs the required search indexes, and stamps the database at the current Alembic revision.
cd frontend
npm ci
npm run devThe development server is available at http://localhost:3000 and proxies API
requests to the backend.
cd backend
docker compose up -d db
docker compose build web
docker compose run --rm web python scripts/setup_database.py
docker compose upThe setup command asks before replacing the database created by PostgreSQL. Run the frontend separately with Vite for the best development experience.
Both commands read DATABASE_URL from backend/.env. From backend:
# Creates backups/<database>_<timestamp>.dump
python scripts/backup_database.py
# Optional custom destination
python scripts/backup_database.py --output /path/to/backup.dump
# Replaces the existing database objects after confirmation
python scripts/restore_database.py backups/<backup-file>.dump
# Non-interactive restore
python scripts/restore_database.py backups/<backup-file>.dump --yesBackup files can contain sensitive application data. The default backups/
directory is ignored by Git; store exported files securely.
| Task | Command |
|---|---|
| Backend tests | cd backend && .venv/bin/pytest -q |
| Backend migrations | cd backend && .venv/bin/alembic upgrade head |
| Frontend tests | cd frontend && npm test -- --run |
| Frontend lint | cd frontend && npm run lint |
| Production build | cd frontend && npm run build |
Start with the documentation index, or jump directly to:
- Database setup
- Declarative views
- Data format
- Frontend guide
- Backend guide
- GraphQL reference
- Insights format
- Global search design
- MCP reports
- Error handling guide
- Quality and testing guide
The seed credentials are intended for local development only. Replace default passwords and secrets before exposing any environment outside your workstation.
See the backend license file.