Supabase Connected — Database Schema Setup Required
Project Reference: eggxwcinifyocmlcybae
Your Supabase cloud database is connected and authenticated with the Secret API Key. However, the database tables (clients, printers, printer_devices, printer_live_status, print_jobs) have not been created yet in PostgreSQL.
Registered businesses
Across all clients
Active print runs
Square feet completed today
All-time fleet volume (sq ft)
Fleet Command & Filter Directory
Select specific clients or filter by highest volume & run times to prevent overload
| Printer ID & Name | Client Company | Model & Bay | Machine Status | Active File / Job | Today (sq ft) | All-Time (sq ft) | Run / Idle Time | Telemetry |
|---|---|---|---|---|---|---|---|---|
| Loading fleet directory... | ||||||||
Client Companies (Tenants)
Manage flex printing businesses tracking their own printers
| Company Name | Client Code | Contact Email | Printers | Created Date | Actions |
|---|---|---|---|---|---|
| Loading clients... | |||||
Printer Fleet & Device Credentials
Manage machine activations, device key rotation, and assignments
| Printer ID | Printer Name & Model | Client Company | Live Status | Device Credentials | Last Seen | Actions |
|---|---|---|---|---|---|---|
| Loading printers... | ||||||
Print Jobs Historical Audit Log
Authoritative audit log across all client machines — filter by client, date range, runtime, and volume in square feet
| File Name | Printer | Client Company | Run Duration | Printed Area (sq ft) | Completion % | Status | Finished At |
|---|---|---|---|---|---|---|---|
| Loading print jobs... | |||||||
Zero-Vulnerability Security Architecture Audit
This console strictly separates human customer accounts from field machine tokens, mitigating common attack vectors:
No Exposed Service Keys
`SUPABASE_SERVICE_ROLE_KEY` is loaded strictly inside the Node.js backend environment. Client browsers only interact with authenticated API routes.
Per-Device SHA-256 Hashing
Printer Windows services authenticate using random device API keys. The database stores only the cryptographic SHA-256 hash.
Row Level Security (RLS)
Supabase RLS guarantees customers can only view printers assigned to their own `client_id`. Cross-tenant data leaks are physically blocked at the database engine level.
Server-Side Ingestion RPC
Telemetry updates every 3s are validated via `ingest_printer_telemetry` PostgreSQL function running with `SECURITY DEFINER`. Spoofing is blocked.
Database Infrastructure Managers & RBAC
Assign granular administrative permissions, API authority, and operational roles
| Manager Name & Email | Administrative Role | Assigned Permissions | Created Date | Actions |
|---|---|---|---|---|
| Loading database managers... | ||||