Skip to content

Accounts and the trial

This page explains what you need from us before you can install a workspace, what the account and the license cover, and how to try the workspace on a spare server.

What is public

You can read this site and download the installer, https://images.hub.linnerprogramming.com/install.sh, without an account. Everything the installer fetches after that requires one: the releases and the platform images come from our distribution registry, which admits one account per customer.

The account

An account is a read-only user name and password for the distribution registry. install.sh uses it to fetch releases, the platform images and your license, and every upgrade and every image build on your side pulls with it. When a subscription ends, we remove the account, and the workspace receives no further releases.

The installer asks for the password once and stores it under /opt/velonde, readable by the user who ran the installation. Nothing of yours is sent to us: your images, apps and data stay in your workspace's own registry and cluster. The installer contacts our registry when it installs or upgrades and once a day for a renewed license, each time with your account. On a single host it also asks api.ipify.org once for the server's public address.

The license

A subscription comes with a license for the workspace. The license is a small text file that names your account and the last day it is valid. We sign it, so it cannot be edited. The workspace checks it itself and never contacts us for it. There is no license server and no seat count.

The installer fetches the license with your account at the install and at every upgrade. It also sets up a systemd timer, velonde-license-<overlay>, that checks once a day for a renewed license and installs it, so a renewal reaches the workspace within a day without your doing anything. To install a renewal at once, run:

bash install.sh license

This fetches the newest license for your account and installs it in the workspace, which follows within a minute. If your workspace cannot reach our registry, we send you the file, and you install it with bash install.sh license <file>. bash install.sh status shows the state of the license and its last valid day.

If the license is not renewed, the workspace goes through three steps:

When What happens
30 days before the last valid day A banner on the workspace's start page and a line in the output of every velonde command name the date. With the monitoring stack, the alert VelondeLicenseExpiring goes to the addresses in alerts_to once a day. Nothing else changes.
From the day after the last valid day New IDE sessions and deploys are blocked. A session that starts shows a page that explains why. Running sessions continue.
30 days after that The sessions that still run are ended.

In every step, what is deployed keeps running: apps, documents, APIs, MCP servers, pipeline schedules, scheduled reports and the package repository. Nothing new is made or changed until the license is renewed.

A workspace without a valid license, for example because its license file was deleted, is in the last step.

None of these steps deletes data. Home directories, projects, deployed apps with their images and settings, and pipeline stores stay where they are. velonde env, velonde logs, velonde history and velonde delete keep working, and an admin can reach every volume through the cluster. Once a valid license is installed, everything starts again within a minute, without a deploy.

There are two offers. Both use the same software and the same installer.

  • Hosted. We operate a dedicated machine for you that is not shared with other customers. We install, upgrade and monitor it, and your team logs in with your identity provider. The configuration belongs to you and moves with you if you later switch to your own infrastructure.
  • Self-hosted. You install and upgrade the workspace with the installer on your own Ubuntu server or Kubernetes cluster. We provide the configuration and help with problems. Your data stays inside your network.

Neither offer is priced per user. In both, Claude Code runs on your users' own Anthropic accounts, and Posit Assistant on their own Posit AI login or a model provider's API key.

The trial

A trial is a self-hosted installation with an account from us. It runs on any Ubuntu 24.04 server you can spare and needs no DNS:

curl -fsSLo install.sh https://images.hub.linnerprogramming.com/install.sh
bash install.sh install --trial --email you@acme.example --account acme-trial

With --trial, the workspace gets a name under sslip.io derived from the server's address, with real certificates, so the three host names resolve without any DNS record of your own. When the installer finishes, you have the IDEs, the agents and velonde deploy, and you log in with the built-in admin account whose credentials the installer prints when it writes the configuration. The trial command above sets up no identity provider, no monitoring and no backups. Installing on a single host describes the options that add them. Because the host name does not belong to you, do not put customer data on it. The trial's license runs until the end of the trial, and the workspace then stops as described in The license.

To move from the trial to a production workspace, run a new installation on the machine you intend to keep, with --domain, and with --auth oidc, --oidc-issuer and --oidc-client-id for your identity provider. Nothing moves over from the trial: projects, home directories and deployed apps stay on the trial machine. If you take out a subscription, you keep the same account.

Getting an account

Write to stefan@linnerprogramming.com and tell us what you have in mind: a trial, a hosted machine, or a quote for your own infrastructure.