Terrapod gives you the Terraform Enterprise control plane on your own Kubernetes cluster, with remote state, run approvals, and policy checks, and no per-resource bill at the end of the month. Point your existing cloud block at it and terraform or tofu keep working unchanged, because Terrapod answers the same backend protocol the CLI already speaks. Workspaces isolate state, variables, and runs per team or environment, with versioned state you can lock, inspect, and roll back. Server-side agent pools execute plans and applies on ephemeral Kubernetes jobs, while CLI-driven runs stay available for local workflows. Approvals gate every apply, and conditional auto-apply only proceeds when a plan adds or updates resources without destroying anything. Label-based RBAC decides who may read, plan, write, or administer each workspace, with OIDC and SAML single sign-on on top. A private registry hosts your own modules and providers with GPG signing, and OPA Rego policy sets enforce rules as mandatory or advisory checks before apply. Drift detection flags infrastructure that wandered from its state, run triggers chain dependent workspaces, and an interactive impact graph shows a plan's blast radius before you approve it. Optional AI review summarizes each plan's changes and risks, and an MCP server lets AI assistants inspect workspaces and runs under the same permissions. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MPL-2.0 licensed.

WebCodex gives ChatGPT, Claude, and other MCP clients a real development environment on machines you own, so an AI assistant can edit your actual repositories instead of a pasted snapshot. A self-hosted Server authenticates every request and routes it to a Runner sitting next to your code, where file edits, Git operations, test runs, shell commands, and long jobs execute with your real toolchain. Your projects never move into a hosted workspace; only the tool results you authorize travel back to the model. The browser Runtime Console shows project readiness, the work queue, session activity, and connected Runners, and it is where you decide pending approvals or accept and reject finished work, because the model cannot approve its own changes. Runners join with a short-lived pairing code and stay connected over QUIC, WebSocket, or polling, so machines behind NAT still work. One-command sharing opens a temporary session for a single repository, while durable setups run the Server and Runner as system services behind your own HTTPS domain. Workflow Sessions keep evidence and context across conversations, so long tasks survive closed browser tabs and threads you pick up days later. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One endpoint, every model you run, and a government-grade paper trail for each request. OpenGateLLM sits in front of your AI infrastructure as the single door: applications call one OpenAI-compatible API, and the gateway decides which backend answers, a self-hosted vLLM cluster, an Ollama box in the corner, a Hugging Face TEI embeddings service, or a hosted provider when you allow one. You publish friendly model names as routers and attach real provider APIs behind them, then load-balance across those backends by shuffle or least-busy so a second GPU node starts earning its keep the moment you register it. Chat completions, embeddings, reranking, OCR, and audio transcription each get their standard endpoint, so existing OpenAI SDK code, LangChain, and LlamaIndex projects point at a new base URL and keep working. Governance is built in rather than bolted on: organizations, users, and roles control who may call which model, API keys authenticate every request, and rate limiting keeps one enthusiastic team from eating the whole cluster. Usage monitoring follows every inference, and carbon footprint estimates attach to models through their hosting zone and parameter counts. Retrieval-augmented generation against Elasticsearch or Qdrant plugs into the same surface. No chat history is stored, which is rather the point when the data is yours. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Agent code needs somewhere disposable to run, and Sandstorm turns one modest VPS into a fleet of thousands of isolated sandboxes that wake the moment work arrives. You create sandboxes through a plain HTTP API, starting from a registered template or forking a tagged snapshot, with per-sandbox memory ceilings, attached volumes, and egress rules set on each call. Every sandbox is a gVisor container with its own network namespace, so untrusted agent code runs away from your host and away from its neighbors. Idle sandboxes cool down through four tiers, from running hot, to frozen in place with a wake time near ten milliseconds, to checkpointed on disk and back in about a fifth of a second, so a small machine can hold far more sandboxes than it could ever keep running at once. A single binary acts as master, node, and web console: the master tracks desired state and places work across nodes, nodes behind NAT dial out to join the fleet, and a gateway on each node wakes a sleeping sandbox and forwards its traffic automatically. The built-in Hub pulls ready-made snapshot packs for warmed runtimes like Python with numpy or a pre-warmed Playwright browser, skipping cold starts entirely. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

ServerBee delivers complete fleet monitoring from a single Rust binary that embeds both the server and web UI, requiring no external database or heavy runtime. Lightweight agents installed on each node stream CPU, memory, disk, network, load, temperature, GPU, and disk I/O metrics over persistent WebSocket connections to a central server backed by embedded SQLite. The real-time React dashboard presents 17 drag-and-drop widget types across custom layouts, with historical charts spanning one hour to 30 days and monthly traffic statistics with billing-cycle prediction and cost insights including burn rate and per-resource unit cost scoring. Network monitoring covers ICMP, TCP, and HTTP ping probes, service monitors for SSL certificates, DNS records, HTTP keyword matching, TCP ports, and WHOIS expiration, plus network-quality probing across 96 China 3-ISP and international presets with IP-quality and streaming-unlock detection. Remote management features include a web terminal with sandboxed file manager, Docker container stats with logs and events, firewall configuration, and agent auto-update capabilities. Public status pages display 90-day uptime timelines, while alerting supports email and webhook notifications with flexible trigger expressions. A native iOS companion app provides mobile monitoring access. Deploy via Docker or download the single binary for Linux, macOS, or Windows, running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Born at Brazilian media giant Globo.com, Thumbor answers imaging CDNs like Imgix and Cloudinary with an HTTP service where every image variant is just a URL. Ask for /300x200/smart/your-image.jpg and Thumbor fetches the original, crops and resizes on demand, and caches the result - one source file, unlimited renditions, no batch pre-generation pipeline. The "smart" in the URL is the signature feature: OpenCV-based face detection finds people in the frame and crops around them (no more thumbnails with severed heads), and when no faces exist, feature detection finds visually important corners and computes a weighted center of mass as the focal point. Beyond cropping, a chainable filter pipeline handles brightness, contrast, grayscale, blur, red-eye removal, rounded corners, rotation, watermarks, and format conversion with quality control - applied in order via URL segments. All common image formats work out of the box, and every layer is pluggable: loaders (HTTP, local, S3), storages and result storages (local, S3, Ceph, and community backends), engines, optimizers, filters, and even custom detectors, with the awesome-thumbor list cataloging the ecosystem. URL signing prevents abuse of your processing capacity. Integrations exist for Django, Rails, Node, WordPress, and most frameworks. MIT-licensed, battle- tested for over a decade.

Securing a SaaS product, running B2B onboarding, or replacing Auth0 and Keycloak with a stack they own - teams needing more than basic auth reach for ZITADEL, an open-source identity and access management platform built in Go. Its multi-tenancy model is the differentiator: a strict Instance, Organization, Project hierarchy isolates data and scopes policy at each level, with identity brokering (pre-built templates for Google, GitHub, Microsoft, Apple, plus generic OIDC, OAuth, SAML, and LDAP), domain discovery that routes users to the right organization by email domain, and delegated management so customers administer their own users and roles. Authentication covers OpenID Connect (certified, including device authorization and token exchange), SAML 2.0 as both IdP and SP, SCIM, FIDO2 passkeys for phishing-resistant passwordless login, and MFA via OTP, email, SMS, and U2F; machine-to-machine flows support JWT profile, PATs, and client credentials. The architecture is event-sourced - every mutation is an immutable event, yielding a complete audit trail - with relational projections for queries and no external session store, so it scales horizontally. API-first with gRPC and REST, extensible via Actions webhooks, and the same codebase self-hosted (Docker Compose or Helm on PostgreSQL) as in the cloud.

With over 43,000 GitHub stars and adoption by companies including Nasdaq, Samsung, and Expedia, Kong Gateway is the world's most deployed open-source API gateway, processing billions of API requests daily across hybrid-cloud and multi-cloud architectures. Built on the battle-tested NGINX engine with OpenResty's LuaJIT runtime, Kong delivers sub-millisecond proxy latency while supporting REST, gRPC, GraphQL, WebSocket, SOAP, and Kafka protocols. The plugin architecture includes authentication via JWT, Basic Auth, HMAC, key authentication, OAuth 2.0, and LDAP, alongside rate limiting with configurable windows per consumer, IP address, or API key. The AI Proxy plugin provides a universal LLM API that routes across OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure AI, Databricks, Mistral, and Hugging Face through a single standardized interface, while MCP proxy capabilities convert REST APIs into MCP tools and provide traffic governance for AI agents. Kong supports declarative configuration via YAML for GitOps workflows, a RESTful Admin API for dynamic configuration, and decK CLI for version-controlled infrastructure-as-code management. Upstream health checking with active and passive probes enables automatic failover, and the ring balancer distributes traffic across upstream targets with consistent hashing, round-robin, or least-connections algorithms. The Kong Plugin Hub hosts over 100 community and official plugins covering logging, monitoring, transformation, security, and traffic control. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Compose Craft is an open-source visual diagramming and management platform that transforms raw Docker Compose configuration files into an interactive canvas of interconnected service nodes. Developers can drag and drop container services to map complex microservice architectures, automatically wiring port mappings, internal bridge networks, volume mounts, and dependency relationships. The real-time synchronization engine reflects every node repositioning, environment variable adjustment, and resource constraint directly into standard docker-compose syntax alongside a live editable code preview pane. Teams can import existing configuration files to diagnose routing conflicts, auto-format tangled service trees, and generate clean architectural documentation for operational handoffs. Engineers can generate shareable read-only public links to demonstrate infrastructure topologies to teammates and external reviewers without forcing them to register accounts. The built-in playground lets administrators experiment with container restart policies, healthcheck definitions, build contexts, and secret keys before deploying to production hosts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 1,200+ GitHub stars since its April 2026 launch, Arkon provides an enterprise-grade knowledge management layer that turns scattered organizational documentation into AI-accessible structured context. The platform runs as a centralized MCP server, compiling your SOPs, policies, technical docs, and institutional knowledge into a versioned wiki with draft-approval workflows, then serving that wiki to Claude Desktop, Claude.ai, Cursor, and any MCP-compatible client through a single permission-scoped endpoint. OAuth 2.1 with PKCE authentication eliminates manual token management — employees authenticate through a browser login while the system discovers endpoints automatically via RFC 8414. The RBAC v2 system supports custom roles with granular permissions, department-scoped AI Skills, workspace isolation, and comprehensive audit logging so every query and access event is traceable. RAG retrieval powered by pgvector embeddings enables AI clients to search across all organizational documents with source attribution, while the AI Skills system lets teams define reusable instruction sets scoped to specific departments or roles. The architecture runs seven Docker containers coordinated by Compose: PostgreSQL with pgvector for embeddings and metadata, Redis for caching, MinIO for document storage, a FastAPI backend, two ARQ async workers for embedding generation and document processing, and a Next.js frontend portal accessible on port 3119. API keys are encrypted at rest with Fernet, and no telemetry leaves the deployment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. PolyForm Internal Use licensed.

With 2,600+ GitHub stars, MetaMCP solves the MCP server sprawl problem by aggregating any number of upstream servers into a single authenticated endpoint that any MCP client connects to once. Group servers into namespaces — development tools in one, data sources in another — then publish each namespace as its own SSE, Streamable HTTP, or OpenAPI endpoint with API-key authentication in headers or query parameters, or full OAuth per the MCP Spec 2025-06-18 standard. The aggregation engine discovers tools, resources, and prompts from all active servers in parallel, prefixes tool names with server identifiers to prevent collisions, and applies configurable middleware including tool filtering to reduce context-window bloat and description overrides to improve LLM comprehension. The web management UI lets you configure MCP servers with stdio, SSE, or Streamable HTTP transports, toggle servers active or inactive per namespace, create and revoke API keys per endpoint, and inspect discovered tools with their schemas. Nested MetaMCP support enables hierarchical architectures where one MetaMCP instance consumes another, creating multi-level tool organization with automatic name resolution. Compatible with Claude Desktop, Claude Code, Cursor, Open WebUI, and any MCP-compatible client through a single connection URL. The Docker container packages the TypeScript backend with PostgreSQL for configuration persistence, exposing the management UI on port 12005 and MCP endpoints on configurable ports. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Foreman is the control room for a server fleet, taking machines from blank hardware or an empty VM to configured, monitored hosts through one web interface. Create a host entry and it network-boots by PXE or UEFI HTTP, or starts from a discovery image that phones home its hardware inventory so unknown machines can be claimed and built by rule. Installation runs from templates for Kickstart, Preseed, AutoYaST, Agama, and cloud-init, while host groups bundle the operating system, partition layout, and parameters that make every build of a role identical. The same console provisions onto bare metal, libvirt, VMware, oVirt, Amazon EC2, Google Compute Engine, and OpenStack, because each provider plugs in as a compute resource with its own images and networks. After installation, Puppet classes and parameters, Ansible roles with recurring runs, or Salt states keep configuration enforced, and the reports and facts those tools send back fill dashboards showing which hosts are current, which drifted, and which are erroring. Smart Proxy services carry DHCP, DNS, TFTP, and configuration enforcement into each subnet or datacenter segment, remote execution runs jobs across the fleet, and the Katello plugin adds content and patch management on top. Hammer gives the whole API a command-line face, and role-based access with LDAP or FreeIPA sign-in keeps large teams in their lanes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

OpenLLM serves any large language model as an OpenAI-compatible API endpoint from a single CLI command, handling model download, backend selection, quantization, and port binding automatically. It supports the full spectrum of popular models including Llama 3.3, Qwen2.5, DeepSeek, Mistral, and Phi3, choosing between vLLM and PyTorch inference backends based on hardware capabilities. When vLLM is available, continuous batching with PagedAttention achieves up to 23x throughput improvement over naive serving, while GPTQ and bitsandbytes quantization reduces memory requirements for GPU-constrained deployments. The server exposes a RESTful API on port 3000 with full OpenAI client library compatibility, enabling drop-in replacement for commercial providers in any application using the standard chat completions format. A built-in web chat UI at the /chat endpoint provides immediate interactive testing without external clients. Custom model repositories allow teams to maintain private catalogs of fine-tuned models alongside the default repository that tracks the latest releases. Deployment workflows generate production-ready Docker images automatically, with Kubernetes manifest support for orchestrated scaling. Native integration with LangChain and LlamaIndex supports RAG pipelines, Transformers Agents enables tool-calling workflows, and HuggingFace Hub handles model discovery. Server-Sent Events enable real-time token streaming across all API endpoints. Backed by BentoML's production ML infrastructure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Flowctl turns repetitive ops work, such as granting SSH access, restarting a service, or provisioning a server, into self-service forms that anyone on the team can run without holding credentials. Each workflow is a YAML or HUML file with typed inputs, validation rules, and a list of actions. Actions run in order or as a dependency graph, so independent branches execute in parallel. Every action runs in a Docker container, as a shell script, or as another flow, and scripts can target remote servers over SSH, several at once. Sensitive steps pause until a reviewer approves or rejects them. Output from one action feeds the next, files pass along as artifacts, and failed actions can be retried. Cron schedules with time zones and labels run flows unattended, while logs stream live in the browser. Email, Slack, Mattermost, and webhook notifications announce success, failure, waiting, or cancellation. Teams get isolated namespaces with user, operator, reviewer, and admin roles, OIDC single sign-on, and encrypted storage for SSH keys and secrets. A built-in flow editor means nobody has to hand-write files, and custom executors can be added as Go plugins. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Sixty-thousand-plus GitHub stars make Uptime Kuma the most popular self-hosted monitoring tool - MIT-licensed, Node.js, and the standard replacement for UptimeRobot, Pingdom, and Freshping. It watches a dozen monitor types: HTTP(S) endpoints with keyword and JSON-query content validation, TCP ports, ICMP ping, DNS records, WebSockets, Docker containers via the socket, Steam game servers, MQTT brokers, gRPC services, and push-based heartbeats for cron jobs and internal workers. Checks run at intervals as tight as 20 seconds - versus UptimeRobot's 5-minute free tier - with unlimited monitors and unlimited data retention. When something fails, alerts fan out through 90+ notification channels: Slack, Discord, Telegram, email with LiquidJS templating, PagerDuty, OpsGenie, ntfy, Gotify, Matrix, and dozens more via native providers plus the Apprise library. Unlimited public or password-protected status pages - mappable to specific domains and organized into monitor groups - communicate health to customers, with maintenance windows that suppress alerts during planned work. The reactive dashboard graphs response times, tracks SSL certificate expiry with advance warnings, supports proxies and 2FA, and ships in dozens of languages. One Docker container with a SQLite volume covers an entire infrastructure.

Stop hunting for a public mirror that still works this week: MirrorProxy puts every software source your builds depend on behind one domain you control, so GitHub releases, container images, npm and PyPI packages, and operating-system repositories all come from the same stable gateway. Point it at a source and it fetches and caches on demand, with no full mirror to store or sync, and when an upstream times out or starts rate-limiting, it fails over to the next endpoint and keeps your builds moving. Around thirty adapter types cover the everyday sprawl: Docker Hub and nine other registries, Cargo and Go modules, Maven and NuGet, Homebrew and WinGet, and more than thirty Linux and BSD distributions, plus custom static repositories you define yourself. Sharing the gateway is safe: invite users, set monthly quotas per person or team, restrict which sources each team may use, and gate access with rate limits and IP rules, while the console shows traffic trends, visitor regions, cache behavior, and the health of every source. Email and webhook alerts warn you before a quota runs out or an upstream outage drags on, and the cross-platform client switches a workstation's sources to your gateway and back. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Sensors watch your infrastructure so your engineers do not have to watch it at 3 a.m. StackStorm is event-driven automation: Python sensors poll or listen to external systems (monitoring alerts, ticket updates, chat messages, webhooks, timers) and inject each event as a trigger. Rules match triggers against criteria you define and fire the response automatically, mapping the event payload straight into action parameters. Actions do the work: SSH commands, REST calls, and integrations for AWS, Docker, OpenStack, Puppet, Jira, Slack, and hundreds more from community packs, or your own scripts wrapped with a few lines of metadata. Multi-step responses become workflows that sequence actions with conditions, branching, and data passed between tasks, handling everything from disk-full remediation to full deployment pipelines. Everything bundles into packs, the shareable units that group sensors, rules, actions, and workflows per product or per automation, installable from the StackStorm Exchange or your own Git repositories. The web UI runs actions, explores workflow executions down to individual task results in real time, manages rules, and installs packs, while every execution, manual or automated, lands in an audit trail with its triggering context. ChatOps aliases even let the team trigger approved automations from chat. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With over 330 GitHub stars and described as "OpenRouter, but for agent tools instead of models," Treg is the unified tool registry that gives your AI agent one base URL, one token, and instant access to approximately 2,800 cataloged endpoints across 56 providers — SEO and backlink analysis via Semrush and Moz, social media intelligence from TikTok and Instagram, people and company enrichment through Crunchbase and Hunter, media buying, scraping, and SERP data — all priced per call from fractions of a cent with no provider signup required. The FastAPI backend with PostgreSQL stores credential bindings and injects them server-side into every proxied request, ensuring API keys and OAuth tokens never touch the agent or local machine while every call is audit-logged. Teams register their own paid API accounts, OAuth connections, vendor CLIs like Stripe, GitHub CLI, Vercel, and gcloud, plus custom SKILL.md definitions — all callable by every teammate's agent through a single treg token with automatic credential injection. The evidence-based tool selector shows success rate, response speed, and last-seen timestamp for each provider, so agents pick tools on measured performance rather than guesswork. Bring-your-own-key routes bypass metering entirely, and the one-dollar free credit on every new team lets agents start calling immediately. The Vue.js web dashboard provides team management, audit logs, catalog browsing, and guided onboarding. Self-host with pip install tools-registry[server] on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.