Package generator

Everything in one file.

A package brings connections, tunnels and snippets to iPhone and iPad in one step. Put it together here, right in your browser.

You can create packages today. Opening them comes with one of the next versions of remoteNX; until then the generator checks every file against the same rules the app applies.

What is a package?

An .rnxconfig file is a JSON file with connections, groups, tunnels, Horizon servers, snippets and pinned host keys. You send it by mail or AirDrop, or keep it in the Files app. Whoever opens it gets entries of their own, which they can change and delete again.

What is never in it

How to open it on iPhone and iPad

  1. Get the file onto the device. By mail, AirDrop, Messages or as a download in Safari.
  2. Tap the file. remoteNX shows a preview of everything it adds.
  3. Choose. What you already have starts unchecked. Pinned host keys are only added once you turn on Trust these host keys.
  4. Import. The new entries are yours: none of them is managed or locked.

Questions

Is my data uploaded?

No. The generator runs entirely in your browser. There is no upload, no request to our server and no analytics. The page even forbids itself any network access through its Content Security Policy. Once loaded, it works offline too.

Why can't I enter a password?

Because a package can end up anywhere: in a mail thread, in a downloads folder, with colleagues. So passwords and private keys stay out. remoteNX asks for the password when connecting, and you pick a key after the import. If an opened file contains any of it anyway, the generator removes it and tells you what it removed.

Can a package change my device?

It can only add things. It cannot set policies, trust certificates or run shortcuts. You see everything it adds before the import and can delete it afterwards.

What happens to entries I already have?

Entries with the same name and host start unchecked in the preview and are marked Already there. An import always creates new entries and never changes existing ones.

What are the IDs for?

They link entries inside the package, such as a connection to its tunnel or group. remoteNX assigns new IDs on import. When you rename an ID in the generator, every link to it follows.

What about placeholders such as {{username}}?

remoteNX fills them in for MDM configurations, not for packages: enter the user name directly or leave the field empty. In snippets, placeholders such as {{host}} stay and are replaced when the snippet runs.

Can I check a package myself?

Yes, with the JSON Schema (remotenx-package.schema.json). The generator checks against the same schema as the app, and also that every link points to an existing entry.

And for a whole organisation?

For many devices, with policies and managed certificates, the MDM configuration is the way to go. Packages are meant for individuals and small teams.