Leantime Self-Hosted

Customer-hosted project and task management application for cross-functional teams.

10 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Official release package or documented Docker setup

  2. Operated by

    Your team

    Customer maintains the PHP/database or container stack, configuration, file storage, backups and application/plugin upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial release package or documented Docker setup
InfrastructureServers / containers
Persistent PHP web application and MySQL/MariaDB database, with customer-controlled data storage and optional Docker packaging.
Licensing modelOpen Source / Open Core
The downloadable application is GNU AGPL version 3. This entry covers that application; separately purchased marketplace plugins and hosted services are not represented as AGPL features.
LicenseAGPL-3.0 downloadable application; marketplace plugins have separate terms

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The configuration guide documents OIDC sign-in and LDAP/Active Directory integration. Configure the provider, callback, claim mapping and application roles; this is not evidence of SCIM provisioning.

Self-hosted Leantime OIDC and LDAP configuration · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream Docker repository supplies Compose with an environment template and MySQL. Replace demonstration passwords, configure persistent storage and select a compatible image before production.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The v3.15.3 README establishes PHP 8.2+, MySQL 8.0+/MariaDB 10.6+, web-server/extensions and supported standard/Docker installation paths, but no CPU, RAM or data-volume baseline was confirmed. Size the application, database, attachments, backups and HA arrangement for the intended load.

Reviewed runtime/deployment prerequisites; production hardware sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The v3.15.3 core is AGPL-3.0. Its README explicitly excepts plugins under /app/Plugins, which may use other terms including the enterprise licence. Assess plugin, support and hosting entitlements separately from core self-hosting rights.

Versioned core licence; commercial plugin and service entitlements are separate · Source ↗ · Versioned project licensing notes ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed upstream release is v3.15.3, published 2026-11-16. Includes the 3.15.1–3.15.2 privacy/session fixes and 3.15.3 onboarding fixes. No database changes are required; the earlier 3.15.0 plugin event migration still applies. This is a dated release snapshot, not a support or future-cadence promise.

Upstream Leantime/leantime release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Scope is the downloadable application. The vendor distinguishes its open-source project section and work dashboard from other offerings; do not assume all website or marketplace features are included. Verify each plugin license and compatibility separately. Releases v3.15.1 and v3.15.2 fix calendar-event exposure, continued use of deactivated-user sessions and tokens, draft-document leakage, cross-project comment leakage, and inactive-account LDAP/OIDC behavior. v3.15.3 fixes users being unable to resume or complete onboarding. All three releases state that no database changes are required; use v3.15.3 or later rather than stopping on an earlier 3.15.x patch. Plugin developers upgrading from before v3.15.0 must still replace the removed legacy HTMX ticket event aliases with the documented lt:tickets:* events or event classes.

Community & maintenance

The official release feed lists v3.15.3. Releases v3.15.1 and v3.15.2 contain security and privacy fixes for calendars, deactivated sessions and tokens, draft documents, comment polling, and inactive SSO accounts; recent releases credit multiple contributors. The vendor identifies Fraunhofer, Linksys and Techstars teams or users on its homepage; these logos do not establish organization-wide adoption or a hosting model.

Category fit

Project management
Open-source project and task planning, task boards, milestones and timesheets; selected marketplace capabilities have separate scope.

Compare within Project management

  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Ever GauzyOpen-source business operations platform for people, projects, time and financial records.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Railway
    • Render
    • Heroku
    • Fly.io
    Customer-operated · Open Source / Open Core
  • JetBrains YouTrack ServerCustomer-hosted project and issue management application from JetBrains.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    Customer-operated · Commercial Only
  • Jira Software Data CenterCommercial self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • KanSelf-hosted kanban boards for projects and team tasks.
    • Railway
    Customer-operated · Open Source / Open Core
  • KaneoSelf-hosted project, board and issue management application.
    • Railway
    Customer-operated · Open Source / Open Core
  • MantisBTSelf-hosted issue and bug tracking application.
    • AWS
    Customer-operated · Open Source / Open Core
  • OpenProject On-PremisesSelf-hosted project management with work packages, schedules, agile boards and collaboration.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 13 other listings in Project management. These products address related workflows; read their category-fit notes before comparing scope. See all of Project management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Leantime community deployment on Railway ↗ · Railway

      Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The community recipe builds upstream Leantime with PHP, Nginx and database configuration in a customer Railway project. Review and set the actual Leantime release/build argument, compatible PHP version, persistent uploads and database backups. This is not the vendor-managed Leantime cloud service or a vendor support commitment.

    • Source for the community Leantime Railway image ↗ · Railway

      Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The inspected Dockerfile downloads a selected release from Leantime/leantime and requires LEAN_VERSION to be set. It uses PHP 8.3 and supervises the application services; the recipe needs version and configuration review rather than treating all template defaults as production-ready.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory