Skip to main content

Strategic Partnerships

We offer a focused, sponsor-aligned path to a demonstrable Apache-2.0 system stack for dedicated RISC-V display devices.

Why this matters

Many dedicated device platforms become harder to control the moment a real deployment starts: one custom driver, one special workflow, one tighter security requirement, one longer lifecycle. Complexity spreads, costs rise, and the system becomes harder to trust over time.

  • Higher long-term maintenance cost
  • Slower customization for specialized deployments
  • More integration risk when hardware or workflows change
  • Less control in regulated or sovereignty-sensitive environments
Industrial control panel for dedicated device environments

Why Open Nexus is different

Open Nexus is not built as one large, tightly coupled stack. It is built around a Rust-based microkernel, capability-governed isolation, explicit service boundaries, and a development process designed to stay testable and documented as the system grows.

  • Easier to adapt for kiosk, HMI, and other dedicated device profiles
  • Easier to keep maintainable over long lifecycle deployments
  • Stronger isolation for security-sensitive environments
  • Clearer integration paths for specialized hardware and driver work
  • Built with distributed device workflows in mind, not just isolated single endpoints
  • Better fit for audit, review, and controlled rollouts

Why this is credible

These are not generic platform claims. The core architecture is already described in public papers and tied to a published software artifact. The goal is not to hide complexity behind slogans, but to make system boundaries, trade-offs, and implementation choices inspectable.

  • Published architecture papers with DOI references
  • Public software artifact linked to the implementation work
  • Deterministic build-and-test workflow instead of ad hoc integration
  • Documented design decisions, interfaces, and boundaries
  • Current work backed by running kernel and service foundations

What we can deliver by year-end

  • Demonstrable system stack — Apache-2.0 licensed and built for dedicated RISC-V display devices
  • Runnable prototype — on defined target hardware or QEMU plus a reference board path
  • Boot to simple UI — a working path from boot to a basic interface or application surface
  • Microkernel-based isolation — process and service separation on top of the NEURON architecture
  • Documented build and test flow — so the result is inspectable, repeatable, and reviewable
  • Defined kiosk/HMI demos — concrete use-cases instead of abstract platform claims
  • Distributed workflow path — room for managed multi-device or cross-session scenarios where they fit the agreed scope
  • Architecture and integration docs — enough to understand boundaries, interfaces, and next steps
  • Regular milestone demos — visible progress throughout the engagement
  • Requirement exchange — close discussion within the agreed scope

Partner benefits

  • Early access to results as they land
  • Insight into the roadmap and delivery path
  • Influence on priorities within the agreed scope
  • Regular reviews and milestone demos
  • Founding Sponsor recognition, if desired
  • A reference setup relevant to the partner's use-case
  • Optional limited support or consulting time

Evidence and references

If you want to validate the technical claims internally, start with the references below. They explain the system model in plain terms and link architectural claims back to code and published artifacts.

What this does not mean

A strategic partnership accelerates an open-source reference stack. It does not transfer the project itself.

  • No transfer of the entire IP
  • No exclusive usage rights to the open-source stack
  • No market exclusivity
  • No full control over the long-term roadmap
  • No permanent custom support entitlement
  • No promise of "everything you want by year-end"

A typical scoped package

  • Target device — kiosk or HMI-class system
  • Target platform — RISC-V on defined hardware or emulator plus reference board
  • Target outcome — a demonstrable system, not a slide deck
  • Scope — defined core functions and agreed demo use-cases
  • Out of scope — no full consumer OS, no app store, no broad hardware support

The trust lever is Apache 2.0. The commercial offer is a faster, better-scoped, partner-informed prototype.

Contact: jenning@open-nexus-os.io

Send a short intro, your device/use-case, preferred target platform, and the level of involvement you have in mind.

Hardware and systems foundation for dedicated RISC-V devices

Three ways to engage

We structure collaboration so the open-source model stays clear while the sponsor still gets tangible value.

  • Sponsor — fund delivery through year-end; everything stays open source, with visibility and prioritized alignment
  • Development partner — fund a reference build shaped around a concrete kiosk/HMI use-case
  • Angel — back the company or pre-company structure; the Apache-2.0 stack is part of the story, not the whole consideration