Skip to content
PandaSuite Docs

Standalone Linux package for offline installation

Get a standalone Linux package that can be installed 100% offline, which is especially useful for Linux devices disconnected from the network.

When generating the Linux package, you can activate the Asset management (offline) option. By including all assets, your application can be installed without an internet connection.

As a reminder, Linux applications generated by PandaSuite can run without an internet connection once installed. This option specifically concerns the installation package and the embedded assets required for a fully offline deployment.

Asset management offline option in the Linux export form

The Asset management (offline) option can significantly increase the size of your package and the time needed to download, distribute, or install it.

This option requires a Yearly or One-Time Payment plan and is available only if your application contains a single project.

When to use an offline Linux package

Use a standalone Linux package when your target devices are:

  • deployed in a disconnected environment;
  • installed in an exhibition, showroom, museum, or training room with unstable connectivity;
  • prepared in advance by an IT team before being used without network access;
  • running in kiosk mode on a dedicated Linux terminal.

How it changes the deployment workflow

With the offline option enabled:

  • the installation package contains the required assets;
  • the application can be deployed in environments where the network is unavailable or restricted;
  • content updates are no longer immediate: you must export a new Linux package and reinstall it on the target devices.

Before large-scale rollout, validate the offline package on at least one Linux device representative of the target environment, with the correct package format and architecture.

Update an offline Linux deployment

To update an application installed from a standalone Linux package:

  1. Export a new Linux package from the PandaSuite dashboard.
  2. Redistribute the new package built for the correct format and architecture.
  3. Reinstall the application on the target devices.
  4. Revalidate the main flows, kiosk behavior, and critical usage scenarios.