infrastructure_overview // deployment_map

system
network.

lucy_os runs as a single-tenant institutional platform. each school gets its own isolated data environment. no shared infrastructure between clients.

schools_on_network
scholar_records
faculty_nodes
class_instances

note // lucy_os is a single-instance deployment per institution. stats above reflect live counts directly from the active database. there are no exaggerated global node claims — what you see is what is actually running.

deployment_stack // layer_model
L_01

Application Layer

Next.js server-side rendering with edge-optimized routing. Each page request is handled in under 50ms.

L_02

API Gateway

Stateless REST API with role-based access control enforced at every endpoint. TLS 1.3 in transit.

L_03

Database Vault

PostgreSQL on isolated compute. AES-256 at rest. Automated backups every 6 hours.

L_04

Email Dispatch Node

Async notification queue for parent alerts, attendance reports, and exam results via Gmail SMTP.

Isolated Tenant Model

every school is a completely isolated tenant. student records, grades, attendance, and communications are stored in schemas that are cryptographically separated. a teacher at school A cannot — even in theory — access records at school B.

browser
api_gateway
rbac_check
db_vault
response
deployment_option

Want on-premise hosting?

we support air-gapped, on-premise deployments for institutions with strict data sovereignty requirements.