CXApps — Official Applications for the ConnectX Network
Applications served directly from node to node over ConnectX. No web server, no exposed port, no hosting provider in the middle. This page is where official CXApps published by Anvil Development are distributed.
CXApp support is landing in CXNexus. The CXApp framework ships in ConnectX today, and CXNexus is gaining the install and render surface for it in an upcoming release. Bundles published here require that build. Until then, listings are shown for what is coming and what is already testable against a node directly.
Official CXApps
Every app listed here is built and signed by Anvil Development. Official bundles are distributed from this page only. A bundle obtained anywhere else is not official, regardless of what it is named.
RProx CXApp
Release PendingThe first official CXApp. Manage an RProx reverse proxy from another machine entirely over ConnectX, with no management port open to the internet and no web panel to defend.
The proxy host runs the app server. Routes, certificate state, and live traffic counters are exposed as @CXAppField values; management operations are exposed as @CXAppMethod calls. Your local node holds the template and renders it, so no markup ever crosses the wire, and every read, write, and invoke is a signed CX event gated by the permissions you granted that peer.
This is the practical case for CXApps: a headless RProx on a box you do not want to expose, administered from your desktop over an authenticated mesh rather than through a port you have to firewall, VPN, or reverse-proxy to reach.
Further official CXApps will be listed here as they are released.
What is a CXApp
A CXApp is a human-facing application that runs on the ConnectX network instead of on a server you have to host. A CXAppServer runs on the node that owns the data. A CXAppClient runs on your node and holds an HTML template. Field values travel between them as signed CX events and are substituted into the template locally.
Four operations travel over the wire: READ to fetch current field values, WRITE to update one, INVOKE to call a method, and REFRESH to re-render against current permissions. All of them move as APP_REQUEST and APP_RESPONSE events through the standard NodeMesh pipeline, signed and verified at every hop.
No HTML on the wire
The client already holds the template. Only field values travel, and values from remote peers are HTML-escaped before substitution, so a compromised peer cannot inject markup or script into your view.
Permission-gated fields
Field and method access is enforced per-permission on the server node. REFRESH silently omits fields the caller has no permission to read, rather than revealing that they exist.
No hosting required
The app is served by the node that owns the data. There is no web server to run, no certificate to renew, no port to expose, and no third party holding the deployment.
Session isolation
Each tab gets an independent session token on first load. Multiple tabs of the same app stay fully isolated even when they target different server peers.
The full framework documentation, including the render surfaces and the security model behind them, is on the ConnectX page.
What "Official" Means Here
CXApps can be written by anyone. That is the point of the framework. The apps on this page are a narrower set: built, signed, and maintained by Anvil Development, and distributed as bundles from this domain.
An app is only as trusted as the node serving it. Installing a CXApp client does not grant the remote server anything. Permissions run the other way: the node holding the data decides which fields and methods a given peer may reach, weighted per-permission, and enforces that on every request.
Verify what you install. Each release is published with its version and checksum alongside the download. Confirm the checksum before installing a bundle, particularly one you did not fetch directly from this page.
Installing a CXApp Bundle
Bundles published here are installed through CXNexus, which renders CXApps with JavaScript disabled and runs the node in-process. This is the surface intended for anything touching authenticated or critical data.
- Install CXNexus and provision or load a node, if you have not already.
- Download the bundle for the app you want from the registry above.
- Verify the checksum published with the release against the file you downloaded.
- Install it in CXNexus from the CXApps page, which registers the client against your node.
- Point it at the serving peer by CXID. The server node grants your peer the permissions it should have; anything ungranted simply will not appear.