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
Registered client accounts
Active billing status
Enrolled workshop printers
Awaiting machine onboarding
| Company Name | Client Code | Plan & Status | Fleet Usage | Created Date | Actions |
|---|---|---|---|---|---|
| Loading clients... | |||||
Printer Fleet & Device Credentials
Manage machine activations, device key rotation, and assignments
Across all organizations
Active telemetry beacons
Workshop accounts enrolled
Cumulative production volume
| 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
Production Totals for Selected Client & Range
All Historical Time| 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.
Machine Statistics & Health Diagnostics
Lifetime powered-on hours, idle ratios, power-on cycles, and critical error incidents across all workshop printers
Telemetry Page Totals for Selected Date Range
Last 30 DaysDaily Power-On to Power-Off Events & Print Run Times
Chronological timeline for selected date rangeHardware Lifetime Baseline Totals
Total Active + Standby duration
0% of powered on time
Hardware power cycle events
100% Completion Reliability
Hardware Telemetry & Power Cycle Breakdown
Since Last Powered On vs Lifetime TotalsCritical Errors & Aborted Print Jobs Incident Log
Hardware aborts, midway job terminations, and error halts across fleets
| Incident Time | Printer (Client) | Aborted File | Progress | Run Duration | Lost Area (sq ft) | Status |
|---|---|---|---|---|---|---|
| Loading incidents... | ||||||
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... | ||||
Subscription Plan Update Timings & Sync Intervals
Configure update timings, powered-off sync rates, and unauthorized backoff intervals pushed dynamically to Windows monitoring agents.
How Agent Interval Synchronization Works
When machine is powered on and actively printing, telemetry syncs at this set interval (not event flooding).
When machine powers on via USB, it monitors for log activity and pings cloud at this idle rate until a print job starts.
When USB disconnect is detected, the agent sends "Power off" state and pings at this low-frequency sync interval.
If credentials are unauthorized or subscription expired, the agent enters backoff mode and will NOT ping until this set time elapses.
Basic Plan STARTER
1 Printer Quota / Entry Level
Recommended: 10 - 15s. Batches telemetry during active printing.
Recommended: 60s. Periodic heartbeat while waiting for jobs.
Recommended: 120s. Sync interval when USB is disconnected.
Recommended: 300s (5 min). Wait time before pinging if rejected.
Pro Plan PROFESSIONAL
Up to 2 Printers / Commercial Fleet
Recommended: 5s. Responsive real-time tracking.
Recommended: 30s. Keeps cloud status warm and ready.
Recommended: 60s. Fleet presence check when machine is off.
Recommended: 180s (3 min). Wait time before pinging if rejected.
Ultra Plan ENTERPRISE
High-Density Industrial / Multi-Printer
Recommended: 2s. High-frequency industrial telemetry rate.
Recommended: 15s. Ultra-responsive standby keepalive.
Recommended: 30s. Rapid power-state awareness.
Recommended: 60s (1 min). Wait time before pinging if rejected.