Skip to main content
PARTNERS

The relationships the roadmap depends on

Named collaborations where disclosable, plus seven open-to categories of relationship — each stated as what Nelix brings and what it is looking for.

Pre-silicon Named collaborations Open to categories
FPGA development board

FPGA development board

DISCLOSED

Named collaborations

Relationships Nelix can name with written agreement. Capacity-building collaborations appear here; open-to categories below are not claimed partnerships.

  • Collaboration

    Pan African Semiconductor Institution

    Collaboration with Nelix for capacity building in Africa — strengthening semiconductor skills and institutional readiness through joint programme work.

    Named collaboration
While running Runtime verification
Continuous runtime verification A conceptual die floorplan for continuous measurement. An always-on measurement engine occupies the left of the die, with a four-phase cycle beneath it: sample, hash, extend, compare. To its right a recessive band shows workload activity in three lanes of uneven task footprints. A sample bus runs under the band and a comb of taps drops from it into a digest chain of linked cells, one per epoch, which the light extends from left to right. One epoch is flagged and re-measured. Beneath the chain the measured history stacks downward in rows that fade as they age, and the chain has no entry from its left end, so the record can only be extended and never rewound. Fresh evidence leaves through a port on the right edge. Operating die · power on Measure engine Always on Sampler Hash macro Every epoch not only at boot Sample Hash Extend Compare Workload activity L0 L1 L2 Sample bus Rolling digest E0 E1 E2 E3 E4 E5 E6 No rewind Re-measure Measured history E6 E5 E4 E3 Fresh quote Measurement continues for as long as the device runs
  • Measured epoch
  • Flagged for re-measure
  • Light = the digest being extended
Boot-time proof goes stale, so measurement continues while the device works and the evidence an operator asks for is always current.
Where partners meet the programme · design intent
NAMING POLICY

Nelix does not display partner names or marks without written agreement. Where a relationship is active and disclosable it will be described explicitly, with the partner named.

Open-to categories are not claimed relationships. Named collaborations appear only when disclosable with written agreement. No third-party logo graphics appear without that agreement. Pre-silicon: architecture defined, RTL in progress, FPGA validation next.

DETAIL

What each category needs and offers

Open-to framing only. Nothing here claims a current commercial relationship.

01 · UNIVERSITIES

Universities

Curriculum collaboration, supervised placements and joint research.

What we need

  • Engineering faculties with digital design teaching
  • Final-year and postgraduate project supervision capacity
  • Departments able to host practical FPGA work

What Nelix brings

  • Curriculum input from an active design team
  • Project supervision and code review
  • Research topics with an industrial counterpart
02 · EDA VENDORS

EDA Vendors

Tooling for design, verification and physical implementation.

What we need

  • Simulation, synthesis and verification tooling
  • Academic and startup licensing routes
  • Training and application engineering support

What Nelix brings

  • An active design programme with a defined tool need
  • A university programme that trains new users on the flow
  • Structured feedback from a constrained-resource design team
03 · FOUNDRIES

Foundries

Process technology, PDK access and the route to a tape-out.

What we need

  • Process design kit access and technology guidance
  • Multi-project wafer participation
  • Packaging and test partner introductions

What Nelix brings

  • An architecture specified for mature, cost-effective nodes
  • A design targeting long-lifetime infrastructure volumes
  • A programme structured around multi-project wafer validation first
04 · GOVERNMENTS

Governments

Sovereign capability, standards input and public infrastructure deployment.

What we need

  • Public infrastructure pilot opportunities
  • Standards and procurement engagement
  • Support for capability development programmes

What Nelix brings

  • Domestic semiconductor design capability
  • Technical input on device security and attestation requirements
  • Engineering training delivered locally
05 · UTILITIES

Utilities

Field conditions, pilot sites and requirements that come from operations.

What we need

  • Operational requirements from real deployments
  • Pilot sites for field validation
  • Feedback on measurement integrity and tamper priorities

What Nelix brings

  • Architecture designed for unreliable supply and narrow bandwidth
  • Metering and grid-edge security expertise
  • Willingness to trial on an FPGA platform before silicon exists
06 · INDUSTRY

Industry

OEMs and integrators building the equipment the silicon goes into.

What we need

  • Product requirements from equipment makers
  • Integration partners for pilot hardware
  • Channel relationships into infrastructure markets

What Nelix brings

  • Silicon and system architecture for constrained deployments
  • Design services capacity for your own programmes
  • Reference designs as the platform matures
07 · INVESTORS

Investors

Capital for a hardware programme with a services business alongside it.

What we need

  • Investors comfortable with semiconductor development timelines
  • Support through FPGA validation and pilot deployment
  • Introductions to strategic and industrial partners

What Nelix brings

  • A defined architecture with a published technical basis
  • Revenue from design services and training today
  • A staged plan that validates on FPGA before committing to silicon

Start with a technical discussion

Partners are named only with written agreement, so the first step is a conversation rather than an announcement.