Beta 0.2.0-beta.2, not yet for critical processes. See the roadmap
PNeX

Open source · Self-hosted · MIT license

Connect all your data. Decide. Act, all the way to the physical world.

The open, sovereign data platform: APIs, documents, public registries, media, cameras and sensors joined in one living ontology, to investigate, follow your business, automate and operate. On your own servers, from a Raspberry Pi to a cluster.

Public beta · 0.2.0-beta.2 · Open source MIT

01Vision

Data you own. Decisions you can explain.

A contract, an email, a public registry, a measurement, an image: each tells part of what happens. Scattered across different tools and clouds, they tell nothing.

PNeX brings them onto one platform and ties them to the real objects they describe. Every fact, image and decision keeps its provenance and its context over time.

AI finds its proper place there: it reads, summarizes, proposes. Actions on hardware stay the ones a human chose to deploy.

03Who it is for

The same building blocks, for very different jobs

Operations & maintenance

Keep the memory of every asset, see failures coming and run your installations.

  • Predictive and planned maintenance
  • Synoptics and controls
  • Documented incident analysis

Investigations, audit & public sector

Build a case on sovereign infrastructure: open, auditable code, and data that never leaves your servers.

  • Investigation cases: timeline, map, graph
  • Sourced, traceable evidence
  • Money flows and actor timelines

Sales, monitoring & investment

Link accounts, public signals and sourced events, instead of scattering them across ten tools.

  • Sales follow-up and prospecting
  • Partner and certification watch
  • Issuer watch and investment theses

Data teams & developers

Build on a versioned ontology rather than gluing tools together: everything goes through a documented API.

  • REST API, CLI and MCP server
  • Installable domain packs
  • Applications on the ontology

04Capabilities

Twelve capabilities, one data foundation

01

Ontology & domain packsNext beta

Your objects, their dated links and provenance; ready-to-install packs: investigation, maintenance, CRM, prospecting, monitoring, investment research.

02

Investigation & incident analysisNext beta

Cases that bring people, places, evidence and hypotheses together on a timeline, frozen and exported on demand.

03

Document intelligenceNext beta

Search across your PDF, Office and spreadsheet files, real-time collaborative pages, assistant answers with citations.

04

AI assistant

On your organization’s own LLM: queries the ontology, diagnoses, drafts — never acts on hardware.

05

API, CLI & MCP

A REST API described by an OpenAPI contract, a generated CLI and an MCP server, with the caller’s own rights.

06

Automation

Visual flows, sandboxed JS / Starlark functions, live debugging, versioned deployments.

07

Geospatial analysisNext beta

A map of your sites and objects, geocoding, routing and basemaps from your provider, through a server proxy.

08

Computer visionNext beta

Detection, tracking and zones on camera streams; Vision Lab to annotate, version and train your own detectors, without Python.

09

Audio & speech

Stream capture, local transcription, speech and speaker detection, voice profiles with consent.

10

Predictive maintenance

Anomaly detection and forecasting as flow nodes, recurring maintenance plans on a calendar.

11

Industrial supervision

Synoptics with animated process symbols, control loops, built-in CoolProp thermodynamics.

12

Devices & field

From firmware to signed updates: boards built and flashed from the browser, edge agent, a certificate per device.

05Why PNeX

Built to last and to be audited

Sovereign

Self-hosted end to end, your own LLM, offline builds: nothing depends on a third-party cloud.

Open

MIT license, permissively licensed dependencies, standard formats on export.

Secure by design

A certificate per device, Noise encryption, signed OTA, strict isolation per organization.

Explainable

Every fact has its provenance, every version is kept, every AI-written text waits for human approval.

One stack

Rust end to end on PostgreSQL, OpenObserve, Valkey and S3 storage: from a Raspberry Pi to a cluster.

06In numbers

560
documented API operations
12
domain packs
2 000+
automated tests
450+
documented design decisions
0
third-party cloud dependencies

07Sectors

Where PNeX helps

  • Public sector & investigations

    Investigation cases, sourced evidence, sovereign hosting.

  • Business services

    Sales follow-up, prospecting, partner and certification watch.

  • Finance & investment

    Issuer watch, sourced events, documented theses. Research only, no order is ever placed.

  • Manufacturing & energy

    Lines, utilities and equipment: supervision, control, maintenance.

  • Buildings & facilities

    Comfort, energy, access and virtual tours of the premises.

  • Inspection & quality

    Field findings, photo and audio evidence, traceable audit cases.

  • Research, education & environment

    Annotated datasets, test benches, measuring stations, reproducible lab work.

Makers and home: the dedicated space, with its tutorials

08Architecture

The stack

An ontology, a flow engine, media workers and an IoT platform in a single product: Rust end to end, three data bricks plus S3 storage, and nothing more.

CLIENTSEDGE · TLSCOREDATAHTTPS · WSSHTTPSWSS · mTLS :4443WSScerts/auth/v1/ · /wsOIDCsuperviseSQL · jobsingest · querylast valuesliveartifacts · mediaWeb appDioxus · WASMNative appsDioxus · same codeDevicesESP32 · ESP8266Your codePublic APITLS edgenginx:443 web · :4443 mTLSCertificatesCA · Let’s EncryptIdentityRauthyPNeX serverRust · Loco + SeaORMFlow engineEdgeLink · RustDatabasePostgreSQLTelemetryOpenObserveLive cacheValkeyObject storageS3-compatible
TLS-encrypted on the wire Private internal networkDocker Compose · Helm 0.3.0 (dedicated device edge) · Wolfi (Chainguard) images · Raspberry Pi → cloud

09Security

Security is part of PNeX’s DNA

Not a box ticked afterwards: every layer was designed encrypted, isolated and verifiable from day one — including on a Raspberry Pi in a workshop.

Encrypted by default, even on a LAN

TLS everywhere with an automatic local CA; a certificate per device (mutual TLS), and inside it a Noise layer with a pre-shared key that holds up against quantum attacks; signed OTA updates.

Least privilege

The server never writes a pin on its own, one write source per output; the AI drafts flows, dashboards, functions and templates, but never touches a device or a control, never deploys, stops or deletes, and cannot change a deployed flow.

Defense in depth

Eight independent layers, from transport to sandboxed user code, down to minimal container images.

Transparent

Every layer shows its real state: shipped, partial or planned. No imaginary security.

Explore the security layers

10Where we are heading

From linked data to running operations

The goal: a complete operational platform, open and sovereign, for civilian uses only. What follows is not built yet; the roadmap says where each block stands.

Versioned data

Transactions, history and lineage, on open formats.

Connectors

Databases, ERP and SaaS, cloud storage, controlled write-back.

Fine-grained governance

Per-object and per-row rights, markings, purpose of access, SAML.

No-code analysis

Aggregates, read-only SQL, rules tested on history.

Governed agents

Autonomous or validated, operation by operation, with a journal and a budget.

Bounded autonomy

On the physical world: limits enforced by the device, shadow mode, manual override.

See the roadmap

Where PNeX stands, honestly

PNeX is in beta — very much so. A lot works, tested by the maintainer on a real bench; none of it has been validated by the community yet. The numbers below come straight from the roadmap.

56
features shipped
45
bench-tested
78
in beta or in progress
0
community-validated

Works today

  • ✓ Flows, JS / Starlark functions
  • ✓ Self-hosting on a Raspberry Pi, TLS everywhere
  • ✓ SCADA and mobile dashboards, ntfy alerts
  • ✓ Build, browser flashing and OTA on ESP8266 / ESP32
  • ✓ In beta: cameras, object detection, anomalies & forecasts, audio streams and transcription
  • ✓ On main, for the next beta: ontology, investigation cases, collaborative pages, document search, Vision Lab, maintenance calendar, call recorder, investment research

Coming next · 0.2.0 (in beta, latest beta.2)

The ontology core: your own object types, typed links that change over time, time-aware properties (replacing a sensor no longer breaks the history of the pump it measures), provenance on every fact and actions run by deployed flows, with a non-destructive migration from 0.1. It also carries what has landed since beta.8: pages, document search, investigation cases, Vision Lab, AI reports, geo providers and the maintenance calendar, then a documented REST API with an MCP server and an admin CLI, roles and service accounts, a to-validate inbox, open-data imports, mailboxes and business packs. In beta since v0.2.0-beta.1; the latest pre-release is v0.2.0-beta.2, and what landed after it is on main and in the nightly build. The release will state what it delivers rather than promise it in advance.

Don’t do this yet

  • ✗ Run a critical process or safety equipment with it
  • ✗ Count on upgrades without breaking changes between betas
  • ✗ Upgrade a beta without planning a USB reflash of every board (the device contract may break between betas)
  • ✗ Expose it to the internet without reading the security page

Try it on a Raspberry Pi

One command gives you a complete, TLS-everywhere PNeX server on a Raspberry Pi 4/5 or any Debian / Ubuntu machine (amd64 or arm64). Docker is installed if missing.

Beta: install it on a test machine, not next to a process that must not stop. A public server with Let’s Encrypt is covered in the docs.

curl -fsSL https://raw.githubusercontent.com/Pnex/pnex-deploy/main/install.sh \
  | sudo bash -s -- --admin-user [email protected] --admin-password 'choose-a-strong-one'

Served on https://<hostname>.local with a private certificate authority generated on the box.

  1. 1

    Install

    Run the one-liner on the server. The admin account is created on first install.

  2. 2

    Trust & sign in

    Open https://<hostname>.local, trust the server CA once per device, sign in as admin.

  3. 3

    Connect a board

    Register a device, flash it from the browser, and wire your first flow.