MIT open source software store documentation

Licentivo Launch is open source under the MIT license. Download the source and host your own software store.

MIT open source software store: commercial use and customization

Licentivo Launch is open source under the MIT license. Download the source and host your own software store.

Versions and complete workflow

The server package runs the storefront; the client package integrates the customer's application. The client already embeds a pinned official Licentivo SDK, so no separate copy is needed.

Requirements

Use the release package for a normal installation. The server does not require Go, Git, Node.js, or a compiler; those tools are only for source development.

Deploy a self hosted software store on Windows and Linux

licentivo-launch_0.3.4-beta_source.zip · SHA256SUMS.txt · GitHub source

First sign-in

The first start with a new database creates an administrator automatically. Open the local site and use:

Software store configuration, payments and license delivery

Configure in the following order and begin with the test payment environment.

Complete the first test purchase

Custom licensing API

Launch supports Licentivo and custom licensing services. Select one store-wide provider in System settings → Licensing system.

Add store account login to desktop software

Open Program integration → Integration checks and code in Launch administration. Select an existing product, language, and sandbox or live environment, then generate the connection function. Launch fills the storefront public URL, Launch-to-Licentivo product mapping, signing public keys, and environment automatically.

Install Launch client packages for nine languages

Install only the Launch package shown below. Every package includes official Licentivo SDK v0.11.6, the default adapter, and linking configuration; do not install a second official SDK.

Correct call lifecycle

Isolate caches by store origin, customer account, product, and payment environment. Keep the client object alive for the application lifetime so floating seats can send policy heartbeats.

Desktop app account login and protected feature examples

Copy the generated connection function for your language first, then adapt these snippets to your project. Read email and password from your login UI and replace export with a real policy feature. Each snippet shows one operation; keep one client alive throughout the application and close it on exit.

Nine-language SDK function and return reference

Browse public Launch functions, parameters, successful returns and failures by language. Optional parameters and defaults follow the matching source version.

Troubleshoot login, entitlement synchronization and offline licensing

English · Deutsch · Italiano · 简体中文 · 繁體中文 · हिन्दी · Español · العربية · Français · বাংলা · Português · Bahasa Indonesia · اردو · 日本語

Integrate Licentivo Launch with AI

Open Operations tools → AI quick integration in administration. Choose the language, platform, project type, existing product, environment, and protected feature. Enter a secret-free English project description, generate the prompt, and give it to your own AI coding tool.

Software store HTTPS deployment, backup and recovery

In production, use a dedicated low-privilege system account to run launch serve, fixing the working directory and configuration path in the service manager. Use systemd for Linux startup and Restart=on-failure to restart after abnormal exits. On Windows, a trusted service manager can run the same launch.exe serve command.

Common questions

Prepare MySQL, download the package matching the operating system and CPU, run launch init, complete config.yaml, then run launch serve. Complete the local first sign-in and password change before configuring the domain and HTTPS.