Nexus is built for PE portfolio-ops leads who lose time turning institutional memory into useful introductions. The source-available proof shows how a trusted network surfaces a non-obvious expert, collects consent, and keeps the introduction accountable.
No local installation is required for the investor walkthrough. The source-available project remains inspectable with synthetic, seeded data.
Every image comes from implemented Nexus UI using synthetic seeded records. Labels distinguish runnable proof from implemented behavior.
A PE portfolio-ops lead names the expertise or connection the network cannot surface efficiently.
Nexus surfaces a relevant seeded member from inside the trusted network and explains the capability overlap.
Both people review the proposal; either can approve, reject, or defer it.
Only an approved path becomes an introduction, recorded and visible inside the network.
Seeded local data. The dashboard surfaces a proposed match and its rationale alongside agent and reputation state.
nexus /dashboardSeeded local data. Visitors can inspect the full roster, including expertise a keyword search would not surface.
nexus /networkSeeded local data. A person reviews the match rationale, then approves, rejects, or defers before any introduction happens.
nexus /ratifySeeded local data. Approved introductions remain visible as network records, tracked through to their outcome.
nexus /introductionsA PE portfolio-ops lead needs a turnaround operator, a sector advisor, or a buyer for an asset. Across dozens of portfolio companies that expertise exists, but it lives in someone’s memory, scattered across deal teams and CRM notes. Manual introductions burn social capital and, when a person leaves, the map of who can help whom leaves with them. Nexus makes that latent expertise recoverable inside the network the firm already trusts.
The pieces needed for human-governed coordination matured at the same time Nexus shipped a runnable proof.
Unlike slide-only theses, the matching→ratification flow ships today as source-available code. The difficult governance work — consent, ratification, recorded introductions — is built, not promised.
Articles requiring meaningful human oversight of consequential automated decisions describe exactly the ratification gate Nexus already implements. Our architecture is pre-aligned with where EU enforcement is heading, not retrofit onto it.
When a portfolio operator leaves, their map of who can help whom leaves with them. Nexus records that map inside the network, so the asset compounds instead of evaporating every redeparture cycle.
Sized bottom-up — count of target organizations multiplied by a realistic annual contract value, never off our customers’ assets. Figures are an estimate with stated assumptions, not validated demand.
~50,000 European professional firms — PE, advisors, and portfolio operators — where an introduction carries capital and consequence, at an assumed €80k average ACV.
Estimate ≈ €4B/yr. Bottom-up: ~50,000 target organizations × €80k mean ACV. Source assumptions in the data room.
~3,000 European PE firms plus ~10,000 of their portfolio companies — the networks whose trusted-coordination is the bottleneck — at an assumed €100k ACV.
Estimate ≈ €1.3B/yr. Bottom-up: ~13,000 target deployments × €100k ACV, benchmarked against enterprise collaboration and CRM-adjacent software.
Private Nexus Enterprise deployments sold and operated alongside each customer. Near-term ramp: ~50 design-partner deployments at a €150k entry ACV.
Near-term estimate ≈ €7.5M/yr ARR, scaling with operator-led sales. Fewer, larger relationships rather than wide self-serve adoption.
Bottom-up estimate with stated assumptions, not validated demand.
The core combines member context, personal assistants, matching, ratification, reputation, introductions, circles, and messaging. Tenant packages can add domain tools without redefining the coordination model.
The included tenant package demonstrates order ingestion, fleet tools, channel integration, and alert monitoring. Credential-dependent services remain optional and inactive by default.
Public source-available evaluation on one developer machine with Docker Compose and synthetic seeded data.
Private Kubernetes deployment, operations, isolation, integrations, and support for organization-scale networks.
Nexus OS evaluates locally on seeded data. Nexus Enterprise targets private, operator-led deployments for organization-scale networks; validated capacity is design-partner scale, with large-network topology as an architecture target, not a benchmark.
Nexus OS is the free, source-available proof. Nexus Enterprise is the private, operator-led deployment we intend to sell. The streams below describe the intended model, not booked revenue.
Sold and operated alongside each customer for organization-scale networks, rather than self-serve sign-up.
Running trusted networks responsibly — hardening, isolation, integrations, and incident response — as an ongoing engagement.
Tenant packages that embed the tooling each vertical relies on, layered on the shared coordination core.
This thesis requires market validation.
We are raising to move Nexus from runnable proof to operated enterprise deployments with design partners. Full terms and a detailed use-of-funds breakdown are in the data room.
No design-partner deployments are signed yet. The market hypothesis — European PE and portfolio networks — is the wedge this round is built to validate.
Round figure and instrument stated on this page; full terms in the data room.
Inspect the member portal and core coordination services locally with Docker Compose and synthetic seeded data.
Run it nowPrivate Nexus Enterprise deployments with design-partner networks, operated alongside the customer.
Architecture targetProduction-grade deployment, multi-tenant isolation, integrations, and operational support.
Architecture targetTens of thousands of members coordinated per network at design-partner deployments, before scaling toward larger-network topology that remains an architecture target, not a validated benchmark.
Architecture targetA small, senior team operating the source-available proof and the private deployment path. Backgrounds, cap table, and advisors are in the data room; we will introduce the founders directly in the demo.
Founder & CEO
ConnectChief Operating Officer
ConnectChief Information Officer
ConnectNo. Nexus OS is source-available: you can inspect and run the proof locally, but the license is not an OSI-approved license. Nexus Enterprise is private and not source-available.
Through private Nexus Enterprise deployments, the operations and support around them, and domain-extension packages. Nexus OS remains a free, source-available evaluation. No revenue is presented as booked.
We have not announced customers. This page describes an initial go-to-market hypothesis in European private capital, not signed traction. Design-partner conversations are part of the demo.
Network adoption, permissioned context, reputation history, governance workflows, domain integrations, and operating expertise. Consumer address books and generic CRMs do not encode how a trusted network decides.
The local matching-to-ratification flow runs on seeded data. Enterprise scale, production hardening, and market traction are architecture targets or hypotheses, not validated results.
Inspect the public repository, run the Docker Compose proof, read the security guidance, and review the evidence register. The investor demo walks through each claim and its source.
The public project exposes the local topology, source, tests, security guidance, provenance, and limitations. External feedback begins with issues while contribution governance is finalized.
Nexus OS packages the member portal and core coordination services for local evaluation with Docker Compose.
Owner: Nexus engineering · Reviewed 2026-06-20Seeded members can review, approve, reject, or defer proposed introductions before an introduction proceeds.
Owner: Nexus engineering · Reviewed 2026-06-20The medical-logistics package demonstrates how a network can add domain-specific ingestion, fleet, channel, and alert tools.
Owner: Nexus engineering · Reviewed 2026-06-20Architecture target: support private-edition deployments serving up to 10 million users. This target is not yet validated by production-scale Nexus testing.
Owner: Nexus product · Reviewed 2026-06-20PE and portfolio networks are the initial go-to-market hypothesis; market demand is not presented as validated traction.
Owner: Nexus product · Reviewed 2026-06-20The "hidden expert" demo scenario (Elena ↔ Dmitri) and its match scores are authored seed data written to illustrate the ratification flow. The shipped matcher performs exact-tag matching only and does not compute these scores.
Owner: Nexus engineering · Reviewed 2026-07-07The investor demo runs on operator-managed server infrastructure. We will walk through the seeded matching-to-ratification story, discuss what the code proves, and separate current evidence from the private-edition opportunity.