Developer,
Student,
Junior Entrepreneur,

Duplicate requests and incomplete state sync could cause real VM outages or data loss.

1. Designed the backend architecture and domain model
2. Built VM lifecycle workflows on the Proxmox API
3. Centered validation, state handling, and recovery around consistency

Unified repetitive VM operations into one consistent workflow and established a Docker-based delivery environment.

A server or database breach could not be allowed to expose secrets alongside their decryption keys. Key sharing for long-lived secrets also needed to account for the risk that quantum computers could weaken conventional public-key cryptography.

1. Derived each user encryption key with Argon2id and stored the ML-KEM-1024 private key only after wrapping it with AES-256-GCM
2. Encrypted secrets with a client-generated 256-bit Environment Set key, separating AES-256-GCM data encryption from key delivery
3. Designed collaborator onboarding to deliver the Environment Set key through the recipient’s quantum-resistant ML-KEM-1024 public key, with Workspace and Environment Set ACLs plus key-reroll state governing its lifecycle

Implemented crypto-credential registration, retrieval, and strict key-size validation, then modeled per-collaborator PQC key delivery and key rerolling in a ciphertext-oriented database schema.

Persistent bidirectional connections had to stay responsive, reject unauthorized clients, and scale horizontally.

1. Designed an RFB web client and WebSocket relay
2. Validated access through short-lived connection tokens
3. Kept the server stateless for horizontal scaling

Separated streaming and authorization concerns into a secure, scalable remote-access architecture.