Premium · one-time €149

A public URL without an open port.

The free server connects through a tunnel you start each time. Premium gives the machine a permanent identity on a relay you can host yourself, reached over an outbound connection that no inbound firewall rule has to allow.

How it connects

Outbound only, both directions

The companion runs the ordinary MCP server on loopback and dials out. The relay never reaches into your network.

  1. 01

    Companion

    Runs omas on 127.0.0.1 and generates a 256-bit connector token plus a node id, stored in the platform state directory.

  2. 02

    Outbound WSS

    Dials relay.omas.taps.im and authenticates with an enrollment secret read from a file, never a command-line argument.

  3. 03

    Stable URL

    The relay publishes a fixed connector URL. Paste it into your client once and it keeps working across restarts and IP changes.

companion
    
          export LIBRAX_RELAY_SECRET_FILE=~/.config/librax-relay.secret
        
          ./librax-mcp-desktop
        
          local server  127.0.0.1:8787
        
          relay         connected · outbound wss
        
          connector     https://relay.omas.taps.im/t/<token>/mcp
        
  

What you get

Everything the OSS server has, plus the parts that need a server

The MIT package stays complete on its own. Premium is the relay, the desktop shell around it, and the packaging.

  • NAT relay

    Your desktop connects outward over WSS and receives a stable public connector URL. No inbound port, no router configuration, no dynamic-DNS.

  • Native companion

    A desktop window and tray icon showing the live connector URL, with copy-to-clipboard and a Ctrl+Shift+L visibility toggle. Closing hides; quitting stops the local server and the relay connection.

  • Packaged builds

    Windows .exe, Linux AppImage, and Flatpak, each built on its native CI runner. No cargo build required on the target machine.

  • Headless node

    For an existing headless MCP service, librax-relay-node ships with a systemd unit and an environment file. The local URL stays on loopback.

  • Self-hosted relay

    The relay server ships as Docker Compose with an Nginx example. The container is read-only, drops all Linux capabilities, and publishes only on host loopback.

  • Screen capture

    Optional screenshots and short videos, gated behind an explicit policy and a single-use local consent that expires in 60 seconds. Unavailable in the Flatpak, which deliberately has no host-spawn permission.

Boundary

The OSS package does not depend on any of this

The premium relay lives in an independent, non-publishable Cargo workspace that consumes the OSS server through a path dependency — not the other way round. Deleting that directory leaves the MIT package building with no manifest changes.

The root MIT licence does not extend to it; that directory carries its own proprietary licence. If you only ever want the free server, nothing here affects you.

One-time €149 · perpetual licence

Buy once. Verify offline. Keep it.

The licence key is signed and verified against a public key embedded in the companion, so the app keeps working with no licence server to reach.