Independently designing services, from backend logic and automation to distributed infrastructure. Explore the project descriptions and interactive architecture maps below.
A production secure-access platform serving 200+ paying users. Not just a VPN server but a dedicated control plane: backend, PostgreSQL / Redis, node orchestrator, Telegram self-service, centralized configuration and telemetry management, custom client applications.
An AI platform with chats, files and workspaces, custom backend logic, a provider gateway, memory, document workflows and background jobs for long-running operations.
An independent platform for LLM tools and roles: capabilities, skill packages, external-source access and policies. The AI skills overlay is separate from tool calls through the MCP transport.
A fresh VPS becomes a working node automatically: SSH setup, Docker, health checks, registration in the system. Monitoring shows node health, traffic and network degradation from a real client’s perspective, not just the server’s.
Centralized control. Distributed secure access.
VPN traffic: client → nodes → internet. DNS name resolution is a separate request. Arrows show the caller; responses return over the same connection. Internal-module connections represent calls within a service.
Models, memory, background jobs and billing through Core.
Chat: AI Backend → Gateway → providers. Background jobs: AI Backend → Redis queue; workers consume jobs. SOLIDUS MCP skills attach through a separate, optional connection — see map 03. Arrows show the caller; responses return over the same connection. Internal-module connections represent calls within a service.
Versioned roles, skills and tools for LLMs with two entry points: internal and OAuth.
Two entry points: an internal API for AI Backend (service key, Nginx allowlist) and an external MCP transport with OAuth 2.1 / PKCE. All tools are read-only. Arrows show who initiates a call; responses return over the same connection. Links to internal modules denote in-process calls.