INFRASTRUCTURE_AUDIT

Hardened
Infrastructure

OMEGA is built on a "Zero-Trust, Zero-Knowledge" architecture. We assume the network is hostile and design accordingly.

ZERO_KNOWLEDGE_ARCHITECTURE

The OMEGA Engine (omega-core) runs entirely on your local hardware. Your API secrets (Binance, Groq, OpenAI) are stored in a local .env file that never leaves your machine.

NO_CLOUD_KEY_STORAGELOCAL_EXECUTION

POSTGRESQL_RLS

Row Level Security ensures data isolation at the database engine level. Even if a query is injected, it cannot return rows that do not match the auth.uid() of the requester.

POLICY: "Users can only select their own rows"

DOCKER_ISOLATION

The Core engine runs in a sandboxed container. It has no access to your host filesystem beyond the specific bind mounts you explicitly configure.

CONTAINER: "omega-core:latest"

JWT_AUTHENTICATION

Communication between the UI and the Cloud is secured via short-lived JSON Web Tokens. Tokens are rotated automatically and signed by Supabase's Auth service.

STANDARD: "RFC 7519"

FULL_AUDITABILITY

OMEGA is open source. You don't have to trust us. You can verify every line of code that handles your wealth data before you deploy it.

LICENSE: "MIT"

ENCRYPTION_STANDARDS

LAYERTECHNOLOGYSTATUS
Data at RestAES-256 (Supabase)ACTIVE
Data in TransitTLS 1.3ACTIVE
API SecretsLocal Environment VariablesISOLATED