Schema-per-tenant isolation, multi-realm Keycloak auth,
and a plugin system powered by Module Federation.
Enterprise-grade multi-tenancy without the complexity tax.
Each tenant gets an isolated PostgreSQL schema. DROP SCHEMA for GDPR right to erasure. No shared data, no leaks.
Every tenant gets its own Keycloak realm. SAML, OIDC, social login, MFA — configured per-tenant.
UI plugins via Module Federation, backend via HTTP proxy, event subscription via Kafka. Plugin in half a day.
Role-based access control with attribute-based condition tree for workspace-level data isolation.
Kafka/Redpanda event bus for async plugin communication. CRUD events emitted automatically on core entities.
E2E tests run against real Keycloak, real PostgreSQL, real Kafka. What you test is what runs in production.
Up and running in 5 minutes.
# Clone
git clone https://github.com/plexica/plexica.git && cd plexica
# Configure
cp .env.example .env
# Start infrastructure
docker compose up -d
# Install dependencies
pnpm install
# Run migrations
pnpm --filter core-api db:migrate
# Create a demo tenant
pnpm --filter core-api tenant:create -- --slug demo
# Start the API (Terminal A)
pnpm --filter core-api dev
# Start the Web UI (Terminal B)
pnpm --filter web dev
Detailed specifications, architecture decisions, and project plan.
Functional and non-functional requirements, personas, security, GDPR, and UX design.
Read → 02System architecture, multi-tenancy, frontend/backend design, plugin system, data model.
Read → 03Rewrite strategy, phased project plan, risk management, success criteria, 5-7 month timeline.
Read → 04Technology comparison and evaluation of key infrastructure decisions.
Read → 05Evaluation of Better Auth vs Keycloak for the authentication layer.
Read → READMEFull README with quick start, testing guide, service ports, and contribution guidelines.
Read →Modern, battle-tested technologies.
Star the repo, read the docs, or contribute to the v2 rewrite.