Sign inSign up

hyukiody/secure-io-engine

By hyukiody

•Updated 9 months ago

Restricted Policy Services for safe Comms; Gateway Node with machine learning auto-weightable suit.

Image
Security
Integration & delivery
API management
0

358

hyukiody/secure-io-engine repository overview

Secure IO Engine (Microkernel)

Tags: latest, v2.0-microkernel-stream, 1.0.0-release

Docker Hub: hyukiody/secure-io-engine

A high-throughput, containerized security microservice designed for sidecar deployments. It provides stateless encryption/decryption for JSON payloads and continuous binary streams (video/audio) using a pure Java 17 Microkernel architecture. 🚀 Quick Start

  1. Run Container

To enable streaming features, use the PRO tier environment variables. Bash

docker run -d -p 8080:8080
--name secure-engine
-e LICENSE_TIER="PRO"
-e LICENSE_MASTER_HASH="5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8"
hyukiody/secure-io-engine:v2.0-microkernel-stream

  1. Usage Examples

Encrypt JSON (Standard) Bash

curl -X POST http://localhost:8080/api/encrypt⁠
-d '{"data": "SensitiveInfo", "key": "MyPass", "api_key": "1234567890123456"}'

Encrypt Stream (Video/Audio) Requires PRO Tier. Encrypts large files with constant memory usage (4MB chunks). Bash

curl -X POST http://localhost:8080/api/stream/encrypt⁠
-H "X-Encryption-Key: StreamPass123"
-H "X-License-Tier: pro"
--data-binary "@video.mp4" > encrypted.dat

✨ Key Features

Microkernel Architecture: Built on JDK native com.sun.net.httpserver. Zero external frameworks (No Spring/Jakarta) for <500ms startup and reduced attack surface.

Constant-Memory Streaming: Custom buffered IO pipeline allows processing multi-gigabyte files using only ~256MB Heap.

Enterprise Simulation: Integrated logic for Rate Limiting, Tiered Access (FREE vs PRO), and SHA-256 License Signature verification.

Security Primitives: AES-256-GCM (Authenticated Encryption) and PBKDF2 Key Derivation.

💼 Portfolio Highlight

Problem: Traditional security services suffer from "Memory Bloat" when processing large media streams, as frameworks often load entire payloads into RAM.

Solution: The Secure IO Engine uses a "Microkernel" approach. By stripping away frameworks and interacting directly with the JVM's native IO streams, this engine achieves:

Efficiency: Process 10GB+ files with constant memory footprint.

Security: 90% smaller container size and attack surface compared to standard Spring Boot images.

⚖️ License

MIT License | Copyright (c) 2026 yiStudio / hyukiody

Note: The LicenseVerifier module is a functional simulation of commercial enforcement logic for architectural demonstration purposes.

Tag summary

Content type

Image

Digest

sha256:a8ca3e2c3…

Size

90.6 MB

Last updated

9 months ago

docker pull hyukiody/secure-io-engine:2.2.0