ServerStack
ServerStack
Self-hosted orchestration platform
Parallel infra • AI • mail • routing

One server platform for proxies, mail, APIs, deployment, and AI access.

We analyzed nine repositories spanning proxying, email infrastructure, deployment, API generation, LLM routing, documentation, and MCP tool orchestration. The result is a unified self-hosted control plane that turns disconnected tools into one operational system.

Review the stackSee architecture
9
Repos
5
Domains
1
Control plane
OrchestratorOnline
Control Plane
Unified orchestration for infra, AI, and app workflows.
Execution Layer
Deploy, proxy, and route workloads across private infrastructure.
Data & Contracts
OpenAPI and documentation-first contracts across services.
AI Router
Normalize model access, failover, and tool routing across providers.
Repository analysis

What each project contributes

unblock-proxy.sh

Network

Turns a home or enterprise network into a self-hosted SmartDNS / SmartGateway proxy layer.

Value
Edge proxying and censorship circumvention
Ideal as the network ingress layer for a private infrastructure stack.

BillionMail

Mail

Open-source mail server and email marketing system with high-traffic self-hosted capabilities.

Value
Self-hosted inbox + outbound campaign automation
Best for multi-domain mail workflows and internal communication.

QuickStack

Deployment

Open-source platform for hosting apps on private infrastructure like Vercel or Heroku alternatives.

Value
Portable app runtime layer
Acts as the deployment substrate for internal services and workers.

OmniMail

Cloud

Self-hosted multi-domain webmail backed by Cloudflare Workers, D1, R2, and email routing.

Value
Webmail and user mail portal
Good fit for email endpoints and domain-managed user experiences.

OmniKey AI

AI

LLM proxy and failover gateway for OpenAI and Gemini-compatible providers with load balancing and key rotation.

Value
Unified AI routing and credential control
This is the AI traffic control plane for internal services.

primesieve

Compute

High-speed prime generator and mathematical compute primitive optimized for throughput.

Value
Compute-intensive utility engine
Useful for cryptographic, scientific, and performance-heavy workloads.

openapi-generator

API

Generates API clients, server stubs, SDKs, and docs from OpenAPI definitions.

Value
API contract translation and generation
Creates a consistent interface layer across all services.

jsdoc

Docs

Generates API documentation from JavaScript comments and code structure.

Value
Documentation, onboarding, and developer clarity
Makes the platform explainable and maintainable for teams.

OneMCP

AI Tooling

Compresses OpenAPI specs into task-routed MCP tools to reduce context bloat and tool explosion.

Value
AI tool orchestration and progressive disclosure
The brain layer for agentic interfaces and tool selection.
Architecture

A unified server stack

Core runtime model
1
Edge proxy / firewall / DNS
2
Mail infrastructure & webmail
3
Self-hosted app runtime
4
OpenAPI and SDK generation
5
LLM gateway and key failover
6
Documentation + MCP tool mapping
Recommended composition

Proxy / DNS: use the SmartDNS or SmartGateway flow to shape ingress and outbound routing.

Email: combine a private mail server with mult-domain webmail to operate communication and marketing channels.

AI: layer OmniKey AI in front of OpenAI/Gemini-compatible providers with failover, telemetry, and key management.

API + docs: standardize contracts using OpenAPI, generate clients, and unify tools through OpenAPI-to-MCP conversion.

Execution plan

How to build the unified server

1

Map the stack into a shared control plane with edge connectivity, proxy, and security rules.

2

Provision mail + email routing as a service, with routing and domain controls built in.

3

Use a deployment runtime to host internal apps, worker jobs, and API gateways.

4

Add an LLM routing layer that consolidates multiple providers behind one failover interface.

5

Generate and version API contracts using OpenAPI and expose them through MCP-friendly tools.

6

Publish documentation and operational dashboards for maintainers and developers.

Operating method

From repository research to a reliable platform

Every service moves through the same accountable loop so progress stays visible, testable, and repeatable.

01

Plan

Define boundaries, ownership, rollout order, and measurable outcomes.

02

Research

Map repositories, runtime assumptions, interfaces, dependencies, and value.

03

Strategize

Choose composition, contracts, security model, data flows, and failure boundaries.

04

Execute

Provision runtime, connect services, generate contracts, and ship increments.

05

Debug

Trace failures across ingress, workers, providers, mail, credentials, and tools.

06

Verify

Check builds, health probes, route behavior, contracts, and browser output.

07

Audit

Review access, secrets, logs, dependencies, delivery posture, and readiness.

08

Optimize

Tune latency, cost, reliability, context usage, docs, and operator ergonomics.