All your work.
Entirely on your terms.

The free core gives you one workspace with a neutral Workspace identity, including projects, planning, documents, testing and the available AI workflows. You can use manual core workflows without a paid license or registration. AI needs a configured provider; creating issues, test cases, or projects through AI also requires a free registration and follows the instance license allowances. Your server, storage, email and provider usage are your operating costs. An eligible paid license adds custom branding and additional workspaces on the same instance.

The free self-hosted core has no per-seat software subscription. The standard White-label offer is licensed per installation; adding a teammate does not add a cloud seat subscription. Your infrastructure still needs enough capacity for the people and work it serves. Check the current pricing page and the terms shown in Instance Settings → License for the offer that applies to your installation.

Yes. Use the Docker Compose installer on a Linux server or the Helm chart in an existing Kubernetes cluster. Both deploy the application with its supporting services. The Compose installer can help install Docker and configures automatic HTTPS when your domain and network are ready. For production, plan persistent storage, service access, backups and capacity. The current API runs as one replica for consistent realtime updates; the web tier can scale separately.

Yes. Instance Settings → AI lets you configure providers, model names and endpoints, then test the connection. Supported provider types include OpenAI-compatible services, Anthropic, Google Gemini and Vertex AI. A compatible local endpoint, such as Ollama or vLLM, can run on your network. The selected models must support the workflows you want to use and be reachable from Leera. You cover provider usage or the infrastructure running your local models. Core workspace features remain available without AI configured.

The self-hosted core can run without registration, and paid offline licenses can be arranged for environments without outbound licensing connections. A connected deployment may contact licensing and update services. AI, email, login providers and integrations also need reachable endpoints, which can be internal where a compatible service is available. Plan how installation images and updates will reach an isolated environment, and discuss the network requirements with us before rollout.

An eligible license unlocks the product name, brand color, logo and favicon. It also allows additional workspaces on the licensed instance. The default Workspace identity already keeps Leera’s vendor links out of the application. Configure your identity in Instance Settings → Branding and review your entitlements in Instance Settings → License. Your public domain, email provider and storage configuration are part of the deployment setup; they do not depend on purchasing branding.

Yes. The default stack bundles PostgreSQL and MinIO, and the deployment guide covers using external PostgreSQL and S3-compatible object storage. Configure the database connection for your deployment and set the storage details in Instance Settings. File links use the public storage endpoint, so it must be reachable from your team’s browsers. Plan data transfer and backups before changing services on an instance that already contains work.

Your operating team owns the recovery plan, off-server backup copies, restore testing and update schedule. The Compose backup command captures the database, matching secret key and deployment configuration, and attempts to copy bundled object storage; verify that uploaded files are included, and protect external storage separately. With the updater enabled, Instance Settings → Updates can back up, download, migrate, restart and check the application. Server commands and Helm upgrades are also documented. Returning to older images does not undo database migrations, so keep a tested backup.

License duration and update coverage are separate. A perpetual entitlement can include a fixed update window. Releases published within that window remain eligible, and an installed version keeps running after the update window ends. Newer releases may require renewed update coverage. Check the current offer on the pricing page and the exact dates in Instance Settings → License; hosting and AI usage are separate from the license.

Your existing data, sign-in and workspaces remain accessible. The instance returns to the default Workspace identity, and creating additional workspaces requires an eligible license. License checks do not lock your team out of workspaces that already exist. Update eligibility follows the update window on your license, which is separate from access to your existing work.