OpenProject On-Premises

Self-hosted project management with work packages, schedules, agile boards and collaboration.

8 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 →

OpenProject project-operation and authentication fixes

A critical project-editing flaw can expose restricted information or permit unintended operations, including deletion.

Scope: The critical issue affects 17.2.0 onward before the applicable fixes: 17.5.2, 17.6.1, 17.7.3, 17.8.2 or 17.9.7. The release also fixes other issues.

Project visibility is required; anonymous visitors can be affected on public instances. The release separately addresses second-factor and other authorization flaws.

Action: Apply a fixed supported release. Instances on 17.2–17.4 must move to a patched line.

Primary source · Reviewed 2026-11-17

OpenProject 17.9.8 security update

OpenProject 17.9.8 fixes eight authorization, disclosure, SSRF, virus-scan enforcement and meeting-operation vulnerabilities.

Scope: OpenProject 17.9 line; the GHSAs linked from the release define exact affected ranges on other branches.

Meeting access, cached activity or work-package responses, invitations, repository URLs and external-storage attachments determine applicability.

Action: Upgrade to the fixed release for the installed supported branch and review every linked GHSA.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Linux packages, Docker Compose or Helm deployment

  2. Operated by

    Your team

    Customer manages infrastructure, backups and updates; support scope depends on the selected plan.

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 methodLinux packages, Docker Compose or Helm deployment
InfrastructureServers / containers
Docker Compose deploys persistent application, database and supporting processes; packages run on a customer server. Persistent storage and external HTTPS termination must be configured.
Licensing modelOpen Source / Open Core
OpenProject states that Community, Enterprise and Enterprise add-ons are GPLv3 software. Paid Enterprise plans provide support, services and add-on enablement; they do not establish proprietary feature-code licensing.
LicenseGPLv3 across Community and Enterprise software; paid Enterprise plans provide support, services and add-on enablement

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.

7 of 12 fields researched (58%) · 7 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The SAML administrator guide documents federated authentication as an Enterprise add-on. Configure the identity provider and claim mappings for the selected self-managed instance.

OpenProject Enterprise SAML integration · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

SCIM user/group synchronization is an Enterprise add-on. Configure an authentication provider and privileged SCIM client; token lifecycle and deletion settings need explicit administration.

Self-managed Enterprise add-on; not Community · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The Docker guide documents signed release provenance, SBOM and VEX attestations and verification commands. These software supply-chain artifacts are distinct from an organizational SOC/ISO attestation. Current review: v17.9.8 contains eight fixes for meeting authorization, cached activity and work-package disclosure, invitation-mail disclosure, repository-URL SSRF, external-storage virus-scan enforcement and meeting-outcome authorization. Upgrade and validate branch-specific guidance in the linked GHSAs.

OpenProject 17.9 line; individual GHSAs define exact affected ranges · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

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

OpenProject distinguishes slim application images for production Compose/Helm installations from the all-in-one quickstart. Choose a versioned image tag and run the required migration/seeder jobs during upgrades.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (select X.Y.Z or X.Y.Z-slim image tag) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The minimum single-server guidance is a quad-core CPU at 2 GHz or above, 4,096 MB RAM and 20 GB free disk for up to 200 total users. Separate scaling examples allocate additional database and worker resources; concurrency changes requirements.

Minimum single-server guidance, distinct from distributed scaling examples · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The v17.9.8 project is GPLv3. The vendor distinguishes free Community from Enterprise on-premises with additional features and professional support. Confirm the chosen subscription tier, user requirements and current commercial quote rather than transferring hosted-plan charges.

Open-source project versus paid Enterprise on-premises subscription; excludes infrastructure · Source ↗ · Enterprise on-premises guide ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

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

OpenProject v17.9.8 was published November 19, 2026. It fixes eight authorization, disclosure, SSRF, virus-scan enforcement and meeting-operation vulnerabilities. Review each linked advisory for branch-specific affected and fixed versions.

OpenProject 17.9 release snapshot; linked advisories define other affected and fixed branches · Source ↗ · Prior reviewed release context ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (5 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
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

OpenProject explicitly states that Enterprise add-ons remain open-source GPLv3 software, not proprietary extensions. The recommended production Docker path separates processes with Compose; the all-in-one quick-start container is not the recommended production setup. Feature availability and support depend on the plan. OpenProject 17.9.7 fixes a critical CVSS 9.4 flaw that allowed users, and anonymous visitors on public instances, to invoke unintended project operations including deletion or restricted-data reads. It also fixes a second-factor bypass and multiple authorization and disclosure issues. Installations on 17.2–17.4 must move to a patched supported release; patched 17.5–17.8 branches are also available. OpenProject 17.9.8 adds eight security fixes covering meeting authorization, cached activity and work-package disclosure, invitation-mail disclosure, repository-URL SSRF, external-storage virus-scan enforcement and unauthorized meeting-outcome movement. Upgrade the 17.9 line and review the linked advisories for other affected branches.

Category fit

Project management
Project planning and delivery through work packages, Gantt charts, agile boards, time tracking and collaborative project records.

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
  • Leantime Self-HostedCustomer-hosted project and task management application for cross-functional teams.
    • Railway
    Customer-operated · Open Source / Open Core
  • MantisBTSelf-hosted issue and bug tracking application.
    • AWS
    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.

    • OpenProject Community deployment on Railway ↗ · Railway

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

      The community template uses upstream OpenProject 17 application images with web, worker and scheduler roles, PostgreSQL, Redis, Hocuspocus and an edge proxy. This is a customer Railway project with platform-managed infrastructure. Confirm matching image versions, attachment storage, credentials, backups and Community versus licensed features.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory