MCP Gateway & Registry
Every team wiring its own MCP servers by hand ends up with credentials scattered across dotfiles and no list of what exists; MCP Gateway and Registry replaces that with one governed front door. Register an MCP server, an A2A agent, a reusable skill, or a custom entity type once, and the Discover page lists it with tags, ratings, and search by natural language. Coding assistants and agents connect to a single authenticated gateway backed by Keycloak, Entra ID, Okta, Auth0, or Cognito, with scopes that decide who may call which tool. Virtual servers bundle tools from several backends behind one endpoint. Connected Accounts brokers third-party logins for Slack, Atlassian, and GitHub so tokens stay off laptops. Every registration is security scanned, and an admission gate holds unsafe items for review. The settings area offers audit log filtering with JSONL and CSV export, federation with outside registries, per-group rate limits, and a searchable configuration viewer. OpenTelemetry metrics and health checks are built in. 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.
Apache SeaTunnel
Apache SeaTunnel is a distributed integration platform that runs batch, streaming, and change-data-capture pipelines between databases, message queues, data lakes, lakehouses, and SaaS applications without hand-rolled scripts. Pipelines are declared once in a configuration file and executed on your choice of the native Zeta engine, Apache Flink, or Apache Spark, so the same job definition travels across engines without connector rewrites. Real-time CDC captures row changes from major databases with a snapshot-first handoff that never locks the source, while checkpoint-backed recovery restarts jobs from the last completed checkpoint with exactly-once semantics. When an upstream table gains a column, schema evolution propagates the change downstream automatically instead of pausing the pipeline for manual surgery. Roughly two hundred connectors cover relational databases, Kafka, object storage, search indexes, vector stores, and business apps, and the multi-table routing keeps every record on the right destination path. Engineers can dry-run configurations against sampled data before a full launch, isolate failures per table, and route bad records to dead-letter queues. Release 3.0.0 adds AI-assisted configuration generation from natural language, Python sources and transforms, and document parsing with text chunking for RAG preparation. 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.
KiCAD Prism
KiCAD Prism gives hardware teams the review and release layer that KiCad and Git leave out, hosted on your own hardware with no proprietary ECAD cloud. Import projects from SSH or HTTPS Git remotes, monorepos included, and every revision opens in the browser across schematic, PCB, 3D, BOM, and stackup views. Cross-probing links the views together, insets open a live view of the other document from any pin or pad, and selecting a net highlights it across schematic, PCB, and 3D with its routed length, layers, tracks, and vias. Reviewers comment on any sheet, part, or area with rich text, pasted snips, and attachments anchored to the exact revision, optionally publishing the discussion to GitHub or GitLab issues. Design Comparison lines two revisions up and lists what changed across schematic, PCB, BOM, stackup, and fabrication outputs, highlighted on the sheet beside the review thread. Release Studio then walks a committed revision through source, identity, manufacturing, build, outputs, and publish, building fabrication and assembly files, showing Gerbers in the browser, recording DRC and ERC evidence and designer and QA sign-off, and publishing the approved package to GitHub or GitLab Releases. Library Manager governs components as a catalog of immutable revisions with symbol, footprint, 3D, and SPICE assets and a QA release flow, delivered into desktop KiCad through the Remote Symbol Provider. 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.
Apache DolphinScheduler
When nightly SQL, Spark, and Python jobs outgrow cron, Apache DolphinScheduler replaces the tangle with a visual workflow orchestrator where every dependency is a line on a drag-and-drop canvas. More than 30 built-in task types cover Shell, SQL, Python, HTTP, Spark, Flink, Kubernetes, SeaTunnel, and Jupyter, while logic nodes add sub-workflows, conditions, switches, and dependencies across projects. Workflows can also be written as code through a Python SDK, YAML, or the Open API and run on timezone-aware cron schedules. Backfill reruns a workflow across a date range or a hand-picked list of dates, in serial or parallel, and any instance can be modified, rolled back, and rerun without touching the saved template. Kill, pause, and resume running tasks, and choose whether a failure ends the run or lets parallel branches continue. Alert groups route results to Email, Slack, Telegram, PagerDuty, Feishu, DingTalk, webhooks, or custom scripts. Tenants, worker groups, and environments isolate teams on shared infrastructure, with project and data source permissions. A Resource Center stores scripts and task files locally or on HDFS, MinIO, and cloud object storage, and the monitor page shows master, worker, and database health at a glance. Standalone, Cluster, Docker, and Kubernetes deployments scale from one node to many masters and workers that can join or leave a running cluster. 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.
Topolograph
Before the maintenance window, know exactly where the traffic will go: Topolograph rebuilds your network the way its routing protocols see it and lets you break it safely on screen. Upload one router's LSDB output, from Cisco, Juniper, Arista, FRRouting, MikroTik, and a dozen other vendors, and the whole area's topology appears as an interactive graph, because the protocol already flooded it everywhere. Compute the shortest path between any two routers and see every equal-cost alternative with per-link loads, then fail a link or a node and watch SPF recalculate: which pairs moved to backup, which are left with none, and how the load shifted on every surviving link. Search the graph for prefixes, MAC addresses, or any network element, plan an MPLS TE path against real bandwidth attributes, and compare snapshots from different moments to answer what changed before the incident. Collectors can stream live OSPF, IS-IS, and BGP events over GRE, BGP-LS, or BMP so the timeline replays the network at the moment things broke, and a REST API, Python SDK, and MCP server let your own tooling and AI agents ask the same questions. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Statewave
Statewave is the memory runtime that compiles what your AI agents experience into typed, provenance-tagged memories, so the same subject asked the same question receives the same context every time. Recording is append-only: your application writes events as episodes (chat, ticket, commit), and a compiler distills them into structured memories with confidence scores, each traceable to its source episodes. When an agent needs context, Statewave assembles a ranked bundle inside the token budget you set; the same request at the same moment returns identical bytes, so retrieval sampling noise never leaks into an answer. Every bundle leaves an HMAC-signed receipt that a replay endpoint can re-evaluate under the same rules. Memories carry sensitivity labels for personal data, financial details, and secrets, and YAML policies deny or redact them per tenant. One instance serves many products: tenants are isolated by header, pinned to a region for residency with cross-region requests refused, and erasable by subject on request. The default compiler runs fully local on regex heuristics with no API key, or point extraction at any of 100+ LiteLLM providers. Reach it over REST from any language, through typed Python and TypeScript SDKs, LangChain, CrewAI, and AutoGen integrations, or the built-in MCP server that lets Copilot, Claude, and Cursor share one memory. Support agents recognize returning customers across sessions, and coding agents keep project decisions between conversations. 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.
Massing
A building project usually scatters across a dozen disconnected tools, and Massing pulls the whole lifecycle into one browser workspace organized as seven rooms: Deal, Design, Planning, Schedule, Cost, Work, and Operate. Generate massing options from a zoning envelope, author the model, and produce permit-ready drawing sets with plans, sections, elevations, and schedules exported as SVG, PDF, or DXF on ARCH-D sheets, plus a MasterFormat specification manual. An IBC code pre-check flags problems before submission. The general contractor portal spans 139 modules for RFIs, submittals, change orders, G702 and G703 pay applications, a critical path schedule, safety tracking with TRIR, and COBie closeout. A development proforma handles sources and uses, XIRR, NPV, and joint venture waterfalls. A vitals strip keeps float, health, and cost per square foot in view, and a next best action banner points to the most urgent item for whichever role you pick, for example general contractor. A CAD command line speeds drafting, and an AI command bar and an MCP server connect assistants to the project. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
ChainForge
Comparing prompts and models by eye stops working fast, so ChainForge lays every experiment out on one visual canvas. Drop a table of inputs into a Prompt Node, add a handful of models, and the app sends every combination of template variable and model, then collects the answers in an Inspect Node that groups responses by any variable. Evaluator nodes score outputs with a few lines of code, and visualization nodes plot pass rates and numeric scores as histograms or box plots. Chat Turn nodes test follow-up questions, to see if a model caves when a user pushes back. Sparkle buttons draft synthetic table rows, test questions, and starter evaluator code with a model of your choice, and an LLM scorer can judge answers against a rubric you write. Example Flows open ready-made experiments, from a no-key starter with tiny in-browser models to prompt template comparisons, sycophancy checks, gender bias audits, red-teaming runs, and 188 flows converted from OpenAI Evals. Documents, Chunking, Retrieval, and Rerank nodes cover retrieval experiments. Finished flows export as cforge files, and results export to spreadsheets or JSON for the rest of the team. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Multiwoven
When warehouse data never reaches the CRM, ad platform, or help desk that needs it, Multiwoven is the open-source reverse ETL platform that syncs it there on a schedule. Sources include Snowflake, BigQuery, Redshift, Databricks, PostgreSQL, ClickHouse, MariaDB, Oracle, Amazon S3, and SFTP. Models define what to move: write SQL with a 100-row preview, pick tables in a visual selector, or reuse existing dbt models. Destinations span Salesforce, HubSpot, Klaviyo, Mailchimp, Zendesk, Slack, Airtable, Google Sheets, Stripe, Facebook Custom Audiences, HTTP endpoints, and vector stores such as Pinecone, Qdrant, and Weaviate. Each sync maps model columns onto destination objects like Salesforce Account, Contact, or Opportunity, then runs as a full refresh or as an incremental sync that moves only new or changed rows, optionally tracked by a cursor field. Schedules can be manual, an interval from minutes to weeks, or a cron expression. A dashboard reports sync activity, each run records its status with successful and failed row counts, and failed runs can trigger status emails. Workspaces keep sources, models, syncs, and destinations separate for each team, while Admin, Member, and Viewer roles and email invitations control access. A connector framework lets teams add sources or destinations that are not yet supported. 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.
Middleware
Middleware turns the pull request history your team already has into live DORA metrics, so engineering leads can see deployment frequency, lead time, recovery time, and change failure rate without building a reporting pipeline. Connect GitHub with a personal access token, group repositories into teams, and the dashboard starts charting how often you ship and how long changes take to reach production. Lead time is not one opaque number; it breaks into first commit to pull request, first response time, rework time, merge time, and merge to deploy, so the actual bottleneck is visible instead of guessed at. Merged pull requests count as deployments and revert pull requests count as incidents, which means recovery time and change failure rate appear even if your team has no separate incident tool wired up. You can exclude bot and dependency pull requests, define which branches count as production, and filter incidents in settings, so the metrics match how your team actually ships rather than how a generic template assumes. Bring it to a weekly engineering review to catch a review queue quietly doubling merge times, or open it after an incident to see if failure rate is trending the wrong way across a team. 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.