Engineered on the Google Cloud Platform ecosystem
We run Syzyra on Google Cloud Platform to isolate attendee data, prevent plaintext secret leaks, and eliminate cold starts.
Serverless Compute & Execution
2 servicesIntelligence & State Store
2 servicesEphemeral Storage & Secrets
2 servicesIdentity, Automation & DevOps
6 servicesFour stages from terminal stall to room recovery
Syzyra replaces informal chat screenshots and stalled lab sessions with structured error intake, grounded Gemini citations, room cluster triage, and verified health checks.
Private capture and local redaction
Zero remote transmission without explicit consent
Attendees capture terminal output, stack traces, and command errors directly in browser memory. Evidence stays on-device until the attendee grants consent.
- Browser IndexedDB holds diagnostic logs on-device
- Canvas pixel redaction masks tokens, passwords, and file paths locally
- The browser blocks all outbound network requests until Consent A is granted
14:02:11 [client:buffer] Storing 4,120 bytes in browser IndexedDB
14:02:11 [redactor] Scanned 12 lines for high-entropy tokens
14:02:11 [redactor] Masked: JWT_SECRET=[REDACTED ON-DEVICE]
14:02:12 [state] Status: LOCAL_STAGED (0 bytes sent to network)Built for the human realities of live developer workshops
Technical workshops break in predictable ways: attendees stay silent when stuck, instructors spend the lab debugging identical laptops, and generic chatbots hallucinate outdated flags.
Eliminating the Hand-Raising Friction
When developers hit errors, they often stay silent rather than exposing confusion to the entire room. Private on-device capture lets attendees troubleshoot errors without broadcasting them to peers.
Breaking the Mentor Bottleneck
Two instructors cannot debug 40 laptops individually. When a setup script fails, 8 attendees hit the exact same error. Cosine vector clustering groups them into one incident card for a single broadcast fix.
Preventing Hallucination Damage
Generic AI chatbots invent deprecated flags that break student environments. Syzyra enforces exact line citations from logs and requires deterministic health check receipts before closing tickets.
"We cut 40 minutes of environment triage per session. Instructors spend their workshop energy teaching distributed systems instead of debugging Node versions on individual machines."
Calculate your workshop time savings
Calculate how on-device redaction, grounded Gemini citations, and cluster broadcasts save instructor hours in your workshops.
Session Parameters
Instructor time saved by avoiding repetitive desk-to-desk debugging for identical setup errors.
Individual student stalls collapsed into single broadcast resolutions via cosine vector similarity.
Projected lab completion rate, eliminating early dropouts caused by local dependency mismatches.
Trusted by developer educators and platform architects
How platform engineers, foundation instructors, and enterprise workshop leads run unblocked labs with Syzyra.
"Instead of walking desk to desk debugging Docker sockets for 45 minutes, Syzyra grouped 11 identical failures and let us broadcast the verified fix to the room in seconds."
"On-device redaction convinced our corporate security team to approve live workshops on employee laptops. No API key or authentication token ever leaves browser memory."
"Attendees who previously froze in silence when their environment broke now recover in under a minute without raising their hands in front of 50 colleagues."
Strict isolation and three-tier consent governance
Participants choose what data processes and what stays local. Raw terminal logs never reach other attendees or unverified screens.
3-Tier Consent Controls
Consent A enables private on-device analysis. Consent B allows matching against similar room issues. Consent C enables peer assistance pairings. Attendees grant or revoke each level independently.
Automated Ephemeral TTL
Raw uploaded evidence expires 1 hour after submission. All workshop records purge 24 hours after an event ends. Cloud Scheduler cron sweeps delete orphaned data every 60 seconds.
Air-Gapped Raw Diagnostics & Secret Isolation
Participants and facilitators never see raw terminal logs or screenshots from other desks. Only anonymized problem signatures reach the facilitator triage queue.
API keys, OAuth tokens, and local paths are masked on-device before leaving browser memory.
Google Cloud Enterprise terms guarantee that Gemini never trains on customer diagnostic logs or code snippets.
The application retrieves all runtime credentials from Google Cloud Secret Manager using IAM service accounts.
Explore both workshop roles without signing in
Test the real interfaces with simulated workshop data. Zero network calls, zero data persistence, and instant role toggling.
Facilitator Command Center
Test the triage command center: inspect grouped participant requests, review line-cited fixes, broadcast guidance to the room, and monitor recovery receipts.
Participant Workshop Workspace
Walk through the attendee workflow: capture terminal logs, redact sensitive tokens on-device, inspect grounded Gemini diagnoses, adjust consent levels, and run health check verifications.
Engineered on Google Cloud Run 2nd Generation
Consolidates serverless compute into a single warm container. Eliminates cold-start cascades, binds secrets to hardware HSMs, and purges ephemeral diagnostic data automatically.
Client Edge & Local Ingest
Client TierRuns inside attendee browser memory. Masks auth tokens, file paths, and environment variables on-device with canvas pixel redaction before any byte touches TLS.
Serverless Compute Core
Compute TierUnifies the Next.js 15.5 application and callable API into a single warm container. Eliminates cold-start cascades across separate microservices during 50-person workshops.
Grounded AI & Secret Boundary
AI & SecurityExtracts root causes using direct line-level evidence citations. Suppresses unverified proposals instead of generating hallucinations. Secret Manager isolates API keys from source code.
Ephemeral State & Sweeper
Data & StorageTracks attendee presence and cosine vector clusters in Firestore. Cloud Scheduler runs 1-minute cron jobs to delete raw evidence blobs after 60 minutes.
Serverless Compute Core
roles/run.invokerWarm Containergcloud run deploy syzyra --region asia-southeast1 --execution-environment gen2"Why we deleted 15 microservices: Running separate serverless functions for triage, vector embeddings, redaction, and notifications caused cold-start spikes during 50-person workshops. Consolidating the Next.js application and API into a single warm Cloud Run container dropped cold starts to zero, removed inter-service network hops, and reduced infrastructure costs by 68%."
Technical clarity for organizers and engineers
Answers to common architecture, privacy, operational, and data governance questions.
Are participant API keys or local passwords ever sent to the server?
No. Attendees redact tokens, passwords, and paths directly in browser memory using canvas redaction before sending any data. On the backend, server filters strip remaining credentials before storing diagnostics.
Does the AI model train on code or workshop errors?
No. Syzyra queries Gemini through the Google Cloud enterprise API, which excludes customer data from model training. Diagnostic logs serve only to extract immediate root causes and purge according to the 1-hour retention schedule.
How does attention clustering prevent repetitive questions?
When participants enable Consent B, Syzyra converts approved error summaries into vector embeddings. When multiple attendees hit the same failure (such as a missing environment variable or port bind error), Syzyra groups them into a single incident card on the facilitator dashboard. One broadcast unblocks the entire group.
How do instructors receive facilitator permissions?
Participants join using the shared event code. Facilitator access requires an explicit operator grant or the platform operator claim (`syzyraOperator: true`) set via Firebase Admin Auth. Attendees cannot escalate their own permissions.
What happens when a workshop concludes?
When the operator closes an event, workshop membership locks. Cloud Storage immediately purges raw evidence files, and the system deletes remaining event metadata after 24 hours. Attendees can export their diagnostic logs as JSON before the event ends.
Can Syzyra run in an offline classroom or private network?
Yes. The Facilitator and Participant demos run completely offline in the browser without network dependencies. For enterprise air-gapped classrooms, the backend connects to local Firebase emulators and mock inference adapters.