OpenProject vs Leantime: which team should choose which tool
A team without a dedicated project manager should choose OpenProject when it needs Gantt-based planning and a clear path to enterprise sign-on, and choose Leantime when the work is driven by goals, ideas and Lean-style tracking that a small group can run without a planner. If single sign-on or LDAP group sync is a hard requirement, OpenProject is the stronger starting point, because those features sit in its paid Enterprise plans rather than in the free Community edition. OpenProject fits teams that want scheduled dependencies and roadmap views and can install through Docker Compose, the recommended route, or the .deb and .rpm packages on a supported Linux distribution. Its database requirement is PostgreSQL 16 or later with the pg_trgm, btree_gist and unaccent extensions, so the team needs someone able to operate PostgreSQL.
Leantime fits teams whose planning centers on goals, metrics, idea boards and retrospectives, with Kanban boards, Gantt charts and timesheets included in the open-source version. It runs on PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later behind Apache or Nginx, and the README recommends the official Docker image. Several capabilities that a larger organization may expect, such as Strategy management, Program Management, Whiteboards and Custom Fields, are paid plugins sold through its Plugin Marketplace, and SSO on the hosted Enterprise plan is priced separately. Leantime's README also lists LDAP and OIDC integration and two-factor authentication for the self-hosted version, so confirm which of these your identity setup needs against the current Leantime pricing page.
The decision turns on three checks. First, whether single sign-on or LDAP group sync is mandatory, since that determines whether OpenProject Enterprise or a Leantime plan has to be priced into the budget. Second, which paid features the team truly needs, such as portfolio views or plugins, because each one adds a recurring license or plugin cost. Third, which database and runtime the team can operate: PostgreSQL 16 for OpenProject or MySQL or MariaDB with PHP 8.2 for Leantime. Ask each vendor for a written quote tied to your user count and edition, and test the install path on a non-production host before committing.
Which OpenProject vs Leantime scenario fits your team
This table maps common team situations to the platform that fits them better, and states the condition that would reverse each pick. Read each row against your own requirements, especially identity policy, schedule needs and whether you expect to buy paid add-ons later.
| Scenario | Better fit | Why and when it stops being true |
|---|---|---|
| A small team that wants tasks and goals in one tool | Leantime | Leantime's open-source version bundles goal and metric tracking, Kanban, subtasks and wikis in one app. This stops being true if you need the portfolio or resource views that OpenProject reserves for Enterprise, or if you need strict schedule control. |
| A team that needs Gantt schedules and baselines | OpenProject | OpenProject's Community edition includes Gantt charts, and its Enterprise plans add full baseline comparison. This stops being true if you do not need baselines, since Leantime's Gantt view may then be sufficient for your planning. |
| A policy that requires SAML or Kerberos single sign-on | OpenProject | OpenProject lists SAML, OpenID Connect, CAS and Kerberos as Enterprise features. Leantime's README lists LDAP and OIDC, and its SSO option sits in the Enterprise plan. This stops being true if your policy accepts OIDC or LDAP only, and then you should confirm Leantime's Enterprise SSO options directly with the vendor. |
| A team that wants Lean and strategy workshops | Leantime | Leantime's open-source version includes Lean and Business Model Canvases, idea boards and retrospectives. Its strategy management and program management features are paid plugins. This stops being true if you need strategy management included without buying plugins. |
| A PHP-run shop | Leantime | Leantime requires PHP 8.2 or later with MySQL or MariaDB and Apache or Nginx, which matches an existing LAMP-style operations model. This stops being true if your team has no PHP operations experience or prefers a PostgreSQL-centered stack. |
| A PostgreSQL-run shop | OpenProject | OpenProject officially supports PostgreSQL 16 or later and requires the pg_trgm, btree_gist and unaccent extensions. This stops being true if your database standards forbid those extensions or require a different engine, so confirm this with your DBA. |
| A team that expects to add paid plugins later | OpenProject | Leantime's paid plugins are sold through its Plugin Marketplace and are licensed separately from the AGPL core. OpenProject's paid features come through Enterprise plans that are priced per named user. This stops being true if your plugin needs are small and fixed, since a one-time plugin purchase may cost less than a per-user plan. |
How the PHP and Ruby stacks change daily operations
Leantime and OpenProject put different components under your care, so the day-to-day work differs as much as the install. The cards below cover the operational concerns that shape staffing: runtime and web server, database, install methods, scaling and upgrades. Confirm each item against the current requirements pages before you commit to a stack.
Runtime and web server
Leantime runs on PHP 8.2 or later behind Apache or Nginx, so your team needs PHP patching, PHP extension management and web server configuration skills. Confirm the OpenProject application runtime language and any web server requirements on its system requirements page before choosing a stack team. The runtime you pick decides which language your on-call engineers must read when a request fails.
Database engine and extensions
Leantime supports MySQL 8.0 or later and MariaDB 10.6 or later. OpenProject officially supports PostgreSQL 16 or later and requires the pg_trgm, btree_gist and unaccent extensions. Check that your database team can install and maintain those extensions, and that backup and restore tooling covers the engine you choose.
Install methods
Leantime's README recommends its official Docker image with a docker-compose file. OpenProject recommends Docker-based installation and also ships .deb and .rpm packages for 64-bit Linux on a limited set of distributions. If your standard OS is not on the supported list, the packaged route may not be available, so confirm that before you design the host build.
Scaling with Kubernetes
OpenProject documents Kubernetes with Helm charts for horizontal scaling, which suits teams already running a cluster. Leantime's supplied documentation centers on Docker and docker-compose, so ask the vendor how it expects to be scaled beyond a single host. Scaling needs add ingress, shared storage and database sizing decisions that should be written into the quote scope.
Upgrades and version pinning
OpenProject ships minor releases roughly monthly, so plan a regular upgrade window and a test environment that mirrors production. Leantime's Community Edition and its paid plugins move on their own release cadence, and plugin compatibility should be checked before each Leantime upgrade. Ask both vendors for their upgrade and migration notes for each version jump you expect to make.
OpenProject vs Leantime features side by side
This table sets OpenProject against Leantime on license, free edition contents, identity options, runtime and database, install methods, integrations, extension model and latest releases. Where a fact is not supplied, the cell tells you what to confirm with the vendor or in your own test install. The main takeaway is that OpenProject places SSO behind its Enterprise plans, while Leantime lists LDAP and OIDC in its open-source README, so check both against your target version.
| Capability | OpenProject | Leantime |
|---|---|---|
| License | GPL-3.0, developed by OpenProject GmbH | AGPL-3.0 core. Plugins may carry separate licenses, including the vendor's enterprise license |
| Free edition contents | Community: work packages, Gantt charts, agile boards, time tracking, dashboards, community support | Community: Kanban, Gantt, sprints, milestones, wikis, timesheets. Strategy, Program Management and Whiteboards are paid plugins |
| SSO and LDAP | SAML, OIDC, CAS, Kerberos and Okta SSO, plus LDAP group sync, are Enterprise features | LDAP and OIDC listed in the open-source README. SSO sits on the Enterprise plan. Confirm LDAP on your version |
| Two-factor authentication | Not stated in the supplied pricing or docs. Confirm for your edition with OpenProject | Listed in the README. Confirm which version or plan you need |
| Runtime and database | PostgreSQL 16 or later with pg_trgm, btree_gist and unaccent. Confirm the application runtime with OpenProject | PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, behind Apache or Nginx |
| Install methods | Docker (recommended), .deb and .rpm packages for 64-bit Linux, Kubernetes with Helm charts | Official Docker image with docker-compose file (recommended). Confirm other packaging options |
| Integrations | Nextcloud integration documented. Jira migrator is in beta and covers Jira Data Center only | Slack, Mattermost and Discord integrations |
| API and plugin model | Confirm API and extension options for your edition with OpenProject | Plugin system, JSON-RPC API and a Plugin Marketplace for paid plugins |
| Latest release | 17.9.2, released October 15, 2026 | v3.12.0, released October 15, 2026 |
What each license and paid edition covers
OpenProject is licensed under the GNU General Public License version 3 (GPL-3.0) and developed by OpenProject GmbH. The free Community edition includes work packages, Gantt charts, agile boards, time tracking and dashboards, with community support only. Paid features sit in the Enterprise plans, which for on-premises use are priced per named user per month, so the cost recurs for as long as you keep the subscription.
- License scope: GPL-3.0 governs the code you run and any modified version you distribute. Confirm with your legal team how it applies to an internal deployment that you do not distribute.
- Community edition: Free, with the feature set described above and no paid support included.
- Basic: 5.95 euros per named user per month on premises, according to the OpenProject pricing page. Enterprise features such as SSO and LDAP group synchronization are listed across the paid tiers.
- Professional and Premium: 10.95 euros per named user per month with a 25-user minimum for Professional, and 15.95 euros per named user per month with a 100-user minimum for Premium.
- Corporate: Priced on request for 250 or more users, so the number that matters is your count of named users, not active sessions.
Confirm which feature sits in which tier before you size the purchase, since the SSO protocols, portfolio and resource management, and custom branding are listed as Enterprise features. Ask whether your user count clears each minimum and whether the named-user model fits how your team actually logs in.
Leantime's core application is licensed under GNU AGPL-3.0. Plugins in its app/Plugins directory may be licensed separately, including under the vendor's enterprise license, so the license of the core does not automatically cover every add-on you install. The open-source version includes Kanban boards, Gantt charts, subtasks and dependencies, milestones, sprints, retrospectives, wikis, documents and timesheets, and it is free to self-host with community support.
- Paid plugins: Strategy management, Program Management, Whiteboards, Notes, Pomodoro and Custom Fields are sold through the Plugin Marketplace for the open-source version. Each one carries its own price and license terms.
- Leantime Pro cloud: Hosted by the vendor at 10 US dollars per user per month billed monthly or 8 dollars per user per month billed annually, according to the Leantime pricing page. This is a cloud service, not a self-hosted install.
- Enterprise plan: Custom pricing for on-premise deployment, SSO, audit logs and data residency. The source does not publish a price, so request a written quote.
- Community edition: Free, self-hosted under AGPLv3, and supported by the community rather than the vendor.
Before you commit, list every plugin your team needs and check its license file and price in the Plugin Marketplace. Confirm whether SSO and audit logging are available on your chosen plan, because those controls are tied to the Enterprise plan on the vendor's pricing page.
Both products bill on different units, so a fair comparison needs identical inputs. OpenProject Enterprise bills per named user per month with tier minimums, while Leantime Pro bills per user per month with a choice between monthly and annual billing. Plugin fees and implementation work are separate line items, and they change the total more than the headline per-user rate suggests. Ask each vendor for a written quote built from the same user count, feature list and term length.
- Recurring seats: Both per-user models repeat every billing period, so headcount growth raises the annual total. Ask how minimums apply if you add users mid-term.
- Billing terms: Annual billing is cheaper per user on Leantime Pro than monthly billing. Ask whether OpenProject offers equivalent term discounts for your structure.
- Currency and tax: OpenProject prices are listed in euros and Leantime Pro prices in US dollars. Ask how each quote converts and which taxes apply.
- Plugin and feature scope: List every paid plugin or Enterprise feature you need, then ask each vendor for its license terms and price in writing.
- Self-hosting and services: Hosting, backups and upgrades remain your costs. If you hire an implementation partner, DeployOpen works to a written fixed scope, and that fee is one-time, with optional retainers for ongoing support.
Request written quotes for both products with the same named-user count and feature list before you compare totals.
How single sign-on and LDAP differ once the free edition is running
The main point is that the free edition does not give you the same identity options on both sides, so check protocol support before you commit to either. OpenProject lists single sign-on with SAML, OpenID Connect, CAS, Kerberos and Okta, along with LDAP group synchronization, as Enterprise features beyond the free Community edition. Leantime's README, by contrast, lists LDAP and OIDC integration and two-factor authentication among its open-source features, while its pricing page places SSO under the Enterprise plan. Read those two claims carefully: the Leantime README and pricing page do not match on where SSO sits, so ask Leantime to confirm in writing which login methods the Community edition accepts.
Before you decide, list the protocols your identity provider actually exposes to you (for example SAML 2.0, OIDC, LDAP bind, or Kerberos) and test each one against a free install in a non-production environment. Confirm whether your directory's group membership can drive role assignment in each product, since OpenProject's LDAP group synchronization is an Enterprise feature and Leantime's LDAP support may differ in depth. Ask both vendors what happens to existing accounts and sessions when you move from local login to federated login.
The protocol list alone does not show how much configuration each option needs. Expect a difference in the work involved: an OIDC or SAML setup typically requires registering the application with your identity provider, mapping claims, and agreeing on certificate or client secret rotation, while LDAP requires bind accounts, search bases and attribute mapping. Those tasks fall to whoever runs the platform, and DeployOpen can plan, implement and document them as part of a fixed-scope engagement, with the scope agreed in writing before work starts. Ask for the configuration steps and the owner of each one before you request a quote.
What drives the running cost of each platform
Running either platform costs more than its license line. The cards below separate infrastructure, seats, add-ons, administrator time, upgrades and support, and name who is paid for each. Ask both vendors for the same written breakdown before comparing totals.
Infrastructure sizing
OpenProject's sizing guide suggests 4 cores and 4 GB RAM for up to 200 users, 8 cores and 8 GB for about 500 users, and 16 cores and 16 GB for about 1,500 users. Those figures set the server line on your bill, and PostgreSQL 16 or later with the pg_trgm, btree_gist and unaccent extensions adds database work. For Leantime, ask for the equivalent sizing in writing for your user count, its PHP 8.2 and MySQL or MariaDB stack, and the expected database growth, because the vendor's own guidance is what you should budget against.
Licenses and seats
OpenProject Community is free, while Enterprise on-premises is billed per named user per month, with a 25-user minimum at Professional and a 100-user minimum at Premium. Leantime's free Community Edition has no seat fee, but Leantime Pro cloud is billed per user, and its Enterprise plan is custom priced. Count named users, not active users, and confirm in writing how inactive accounts, guests and contractors are billed.
Plugins and add-ons
Leantime lists Strategy management, Program Management, Whiteboards, Notes, Pomodoro and Custom Fields as paid plugins for the open-source version, sold through its Plugin Marketplace, so these purchases recur if you adopt them across teams. OpenProject keeps SSO, LDAP group sync and portfolio management in its Enterprise tiers. Build a list of the features your team needs, map each to a plan or plugin, and ask whether plugin prices are per instance, per user or per year.
Administrator time
Each platform needs someone to own the stack. OpenProject runs on Docker, packages or Kubernetes with Helm, and Leantime recommends its official Docker image and docker-compose file. Administrator time covers patching, backups, LDAP or OIDC configuration and plugin management. Ask each vendor which tasks are customer responsibilities and which are covered by a support plan, and estimate the hours from your own environment rather than from a vendor claim.
Upgrade effort
OpenProject publishes roughly monthly minor releases, for example 17.7.0 on August 5, 17.8.0 on September 2 and 17.9.0 on September 30, 2026, so the upgrade cadence is frequent and needs a regular test window. Leantime's release line, including v3.11.0 and v3.12.0 in October 2026, also moves quickly. Ask each vendor for its upgrade path, supported skip versions, rollback steps and the typical effort per release in writing before you commit.
Support and services
OpenProject Community support is community-based, while Enterprise plans include vendor support. Leantime's Community Edition is community-supported, and its Enterprise plan adds SSO, audit logs and data residency under custom pricing. DeployOpen can plan, implement, harden, back up, upgrade and support either platform inside your own infrastructure under a fixed scope agreed in writing, and ongoing support is available as a retainer. Request the service levels, response windows and included upgrades in every quote.
Moving from one to the other without losing project history
This sequence moves projects, people and their permissions from Leantime to OpenProject, or back, while keeping a dated record of what was moved and what was left behind. No direct importer between the two products appears in the supplied facts, so the work is a controlled export, mapping and re-entry exercise that ends with an archived source.
Inventory projects, users, roles and custom fields
The team lead and an administrator on each side list every active project, its open and closed tasks, attachments, milestones, and the people attached to each. They also record the roles each person holds, any custom fields in use, and which Leantime plugins (such as Strategy management, Program Management or Custom Fields) hold data that would have no native home in the target. The output is a signed-off inventory spreadsheet that names every object to move, every object to leave behind, and the owner who approved each decision. Confirm the export options for your Leantime version, including whether the JSON-RPC API exposes the objects you need, with Leantime before you rely on it.
Map Leantime concepts to OpenProject objects
Build a written mapping table that states where each Leantime concept lands in OpenProject, or the reverse. Tasks and subtasks usually map to work packages, and milestones and sprints need an explicit decision on whether they become versions, phases or work packages with a type. Goals, ideas, Lean and Business Model Canvases have no direct equivalent in OpenProject, so decide whether they become wiki pages, attachments or are archived only. Flag every row marked as lossy. The output is a mapping document reviewed by the project owners, with each lossy row accepted in writing by someone who will live with the result.
Set up the identity mapping
Decide how each source account becomes a target account before any data moves. Compare the login methods available in each product: Leantime lists LDAP and OIDC integration and two-factor authentication in its README, while OpenProject lists SAML, OIDC, CAS, Kerberos and LDAP group synchronization as Enterprise features. Create a mapping of usernames or email addresses to target identities, confirm which accounts are inactive or external, and agree who owns orphaned work. Note that single sign-on in OpenProject sits in the Enterprise tier, so confirm your edition before you design the login flow. The output is a reviewed user list with a target identity and role for each person.
Run a pilot on a copied database
Restore a copy of the source database into a separate test environment and run the export and re-entry steps against it. For OpenProject, use a test install that meets the documented PostgreSQL 16 or later requirement with the pg_trgm, btree_gist and unaccent extensions. For Leantime, use the MySQL 8.0 or MariaDB 10.6 or later stack in its README. Pick one representative project with attachments, comments and dependencies, then compare record counts, dates, assignees and statuses against the source. Log every discrepancy. The output is a pilot report that lists what matched, what changed, and what needs a manual fix before the real cutover.
Schedule the cutover window
Agree a freeze window with the project owners in which no new work is created in the source. Confirm who will run the final export, who checks it, and who can roll back to the source if reconciliation fails. Communicate the window to every user and point them to the new location for work created after cutover. Because this is an operational decision, set the window length with your own change process rather than with a figure from this page. The output is an approved change record that names the owners, the freeze start and end, and the rollback decision point.
Run the final migration and reconcile
Execute the final export and import using the mapping and the steps proven in the pilot. Then reconcile the target against the frozen source by project, object count, assignee and status, and spot-check attachments and wiki content. Reconciliation should be done by someone other than the person who ran the import. The output is a reconciliation sign-off per project, with any exceptions logged and approved by the business owner. Only after sign-off should users be given access to the target as the system of record.
Archive the source and record the decisions
Keep the source read-only for a retention period set by your own records policy, and store a full export alongside the mapping document, pilot report and reconciliation sign-off. Remove write access for users and document the date the source was retired. Keep the archive in a location the original owners and your auditors can reach, and confirm the restore path works before decommissioning the old server. The output is an archive package with an index, so anyone asking later about a project's history can trace where it went and what was left behind.
Where implementation projects usually run long
Implementation projects on either platform run long when identity and role design are treated as a final step after data has already moved. On OpenProject, single sign-on through SAML, OpenID Connect, CAS, Kerberos or Okta and LDAP group synchronization are Enterprise features, so the team must confirm the edition before design starts. Group names from the directory then need mapping to OpenProject global and project roles, and that mapping shapes what the import should carry over. Leantime's LDAP and OIDC integration and two-factor authentication sit in the open-source README, but its enterprise plan covers SSO and audit logs, so confirm which sign-in path your edition and deployment actually support. Settle group-to-role rules first, then test them with a few pilot accounts before any bulk user load.
On the database and runtime side, OpenProject expects PostgreSQL 16 or later with the pg_trgm, btree_gist and unaccent extensions, so a team that plans to reuse an existing database server should check those extensions early. Leantime runs on PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later behind Apache or Nginx, and the hardening work there (PHP settings, web server configuration, database permissions, backup routines) belongs to the operator. Plugin needs are the other common delay. Leantime's Strategy management, Program Management, Whiteboards, Notes, Pomodoro and Custom Fields are paid plugins, so a feature that a pilot team relies on may turn out to need a license decision late in the project. Inventory required features against each edition and plugin list before committing to a design.
Data cleanup and upgrade ownership cause the longest tails. Imports from Jira or other sources need cleaning first: duplicate users, orphaned tasks, inconsistent status names and unused custom fields all create rework. The OpenProject Jira Migrator supports Jira Data Center 10.x and 11.x only, is in beta and is documented for test setups, so a Jira Cloud source needs a different plan. Both platforms also release often. OpenProject shipped 17.9.0 on September 30, 2026 and 17.9.2 on October 15, 2026, and Leantime shipped v3.12.0 on October 15, 2026, so someone must own patching, backups and upgrade testing from day one. Ask each vendor or your partner to name that owner, the test environment and the rollback path, and budget user adoption sessions alongside the technical work.
OpenProject vs Leantime questions buyers ask before hiring help
Can Leantime Community replace OpenProject Enterprise SSO?
Not on the free tier as a direct substitute, so confirm the requirement first. Leantime's README lists LDAP and OIDC integration and two-factor authentication among its open-source features, which may cover some sign-in needs. OpenProject's pricing page lists SAML, OpenID Connect, CAS, Kerberos and Okta single sign-on, plus LDAP group synchronization, under Enterprise. Leantime's Enterprise plan includes SSO, but it is custom-priced, so the cost comparison depends on a written quote. Map your identity provider, group-based access rules and audit needs against each product's documentation before deciding which edition you need.
What drives the cost of each platform?
Cost falls into licensing, infrastructure, implementation and recurring operations. Licensing differs in shape: OpenProject Enterprise on-premises is priced per named user per month, with Basic at 5.95 euros and Professional at 10.95 euros per user per month, and minimums apply to Professional and Premium. Leantime's pricing page lists Pro cloud at 10 US dollars per user per month billed monthly or 8 dollars billed annually, and its paid plugins are sold separately. Ask any quote to itemize licenses, plugins, hosting, implementation hours and support, and to state which items recur each year.
How long does an implementation take, and what sets that time?
No duration applies to every team, so the timeline comes from the written scope. The main variables are the number of users, the identity integration, the number of plugins or add-ons, any data import and how many environments you need. OpenProject's sizing guide scales hardware from 4 cores and 4 GB RAM for up to 200 users to 16 cores and 16 GB for about 1,500 users, so user count affects infrastructure as well as configuration. A Jira import also adds time, because the OpenProject Jira Migrator supports Jira Data Center 10.x and 11.x only and is in beta. Request a timeline tied to these items in the scope document.
What does the work need from our own team?
Your team supplies decisions and access, and the implementer supplies configuration and delivery. Expect to name a business owner for workflows, a project lead who signs off on fields and roles, and an identity or infrastructure contact who can provision SSO, DNS, certificates and the database. For OpenProject, a PostgreSQL 16 or later instance with the pg_trgm, btree_gist and unaccent extensions must be available. For Leantime, you need PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later. Ask the provider to list every client-side task and its owner in the written scope.
Can our team set up OpenProject or Leantime without outside help?
A technically capable team can often install a free edition, but production readiness usually takes more work. OpenProject supports Docker-based installation, which it recommends, along with .deb and .rpm packages and Helm charts for Kubernetes. Leantime recommends its official Docker image and docker-compose file. The harder parts are SSO configuration, backups, upgrades, monitoring, hardening and migrating existing data. If your team lacks capacity for these, a fixed-scope engagement can cover them with written deliverables. Decide which tasks you will own before you ask for a quote.
How hard is it to switch between OpenProject and Leantime later?
Switching is manageable when you plan the data model early, but it costs time whichever direction you move. Both products store work items, users and project content in their own structures, so a move usually means exporting, mapping fields and statuses, and validating results with real users. Check which items each tool can export and whether plugin-based data, such as paid plugin fields, has an equivalent target. Keep a clean export of your projects, document your custom fields and roles, and ask any implementer to price the migration as a separate line in the written scope.
How DeployOpen works on this
DeployOpen plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For OpenProject vs Leantime, we start by agreeing which edition, identity setup and plugins your team actually needs, then build and document that decision.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope names the OpenProject edition or Leantime plan, any Enterprise or paid plugin features, and the identity provider to integrate.
- Ask for a quote that separates license purchases, implementation, data migration and any retainer for ongoing support.
How we build
- We install the chosen platform in your environment and confirm the PHP or Ruby runtime, database and reverse proxy stack.
- We configure SSO or LDAP sign-in and test group mapping against your directory before users are onboarded.
- We check that the features you depend on, such as Gantt views or plugin functions, behave as scoped in your own environment.
How we hand over
- You receive documentation covering installation, configuration, backup and restore steps, and upgrade procedures for your team.
- We walk your administrators through daily operation, user and role management, and how to apply platform updates.
- Deliverables are written for your own staff, so the platform remains operable without ongoing DeployOpen involvement.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers agreed separately from the initial scope.
- Retainers can cover applying minor releases such as those OpenProject and Leantime publish, after testing in a staging copy.
- Ask whether support covers plugin changes, identity provider changes and restore testing, and confirm this in the written scope.
