Architecture Overview

Remok uses a client-server architecture with centralized management and distributed gateways.

Components

Remok consists of four core components that work together to provide secure remote access:

Management Console — web-based admin interface for configuring applications, managing users, and viewing logs
Access Gateway — handles VPN connections and traffic forwarding; can be deployed in multiple locations
Client Application — installed on user devices; establishes encrypted tunnels to the gateway
Authentication Service — handles user identity verification and policy enforcement

User opens the Remok client and enters their Enterprise Code + credentials
The authentication service verifies identity (with optional MFA step)
An access token and network policy are issued to the client
The client establishes an encrypted DTLS tunnel to the nearest gateway
All internal network traffic is routed through the tunnel according to the split-routing policy
Every session is logged for audit purposes

Remok clients intelligently detect the current network environment:

On corporate LAN — direct access to internal resources; VPN tunnel is bypassed to reduce latency
On external network — VPN tunnel is automatically established; all internal traffic is encrypted

💡 Automatic network detection significantly reduces unnecessary VPN traffic and improves user experience.

Team Size	CPU	RAM	Disk
Up to 10 users	2 cores	4 GB	40 GB
10 – 100 users	4 cores	8 GB	100 GB
100+ users	8 cores	16 GB	200 GB

Zero Trust — no user or device is trusted by default; every connection is verified
Least Privilege — users can only access explicitly authorized resources
End-to-End Encryption — all traffic is encrypted using DTLS 1.2 with AES-256-GCM
Complete Audit Trail — every connection, access event, and admin action is logged