Encrypted Code Meta-Editor Build
Budget: $250 – $750 AUD
I’m putting together a lightweight yet secure meta-editing environment focused on code. The core need is a true code editor—nothing WYSIWYG or plain-text—able to read and write encrypted project files so that source remains protected end-to-end.
Here is the essence of what I’m after:
• A desktop or web-based editor purpose-built for coding tasks.
• Built-in encryption/decryption of files or project folders using modern, open algorithms (AES-256 or similarly strong).
• Smooth, familiar coding workflow: open an encrypted file, make edits, save, and the file is automatically re-encrypted without exposing plaintext on disk.
• Clean, well-documented codebase so I can extend the tool later.
Technology stack is open for discussion; feel free to recommend Electron, Tauri, a browser-only solution, or any framework you believe keeps the footprint small and security tight.
Deliverables
1. Working application (installer or runnable build) that meets the requirements above.
2. Source code with comments and a brief README describing build steps, crypto libraries used, and how to change keys or algorithms.
3. A short video or document showing the encryption flow in action.
If this sounds like a challenge you’d enjoy, tell me which language or framework you’d start with and why, along with a rough outline of your encryption approach.
Here is the essence of what I’m after:
• A desktop or web-based editor purpose-built for coding tasks.
• Built-in encryption/decryption of files or project folders using modern, open algorithms (AES-256 or similarly strong).
• Smooth, familiar coding workflow: open an encrypted file, make edits, save, and the file is automatically re-encrypted without exposing plaintext on disk.
• Clean, well-documented codebase so I can extend the tool later.
Technology stack is open for discussion; feel free to recommend Electron, Tauri, a browser-only solution, or any framework you believe keeps the footprint small and security tight.
Deliverables
1. Working application (installer or runnable build) that meets the requirements above.
2. Source code with comments and a brief README describing build steps, crypto libraries used, and how to change keys or algorithms.
3. A short video or document showing the encryption flow in action.
If this sounds like a challenge you’d enjoy, tell me which language or framework you’d start with and why, along with a rough outline of your encryption approach.