On-Premise

Linetrack in your
own data centre

For companies whose project and personnel data must not leave their own network: Linetrack runs entirely on a server in your building. The same application, the same feature set – on your infrastructure and under your control.

Data stays inside your network
No internet access needed to operate
Perpetual right of use

The on-premise installation is available on request. Scope, schedule and terms are agreed per installation.

How it works

From first enquiry to handover

An on-premise installation is a project, not a download. Four steps in a fixed order – who takes which one is settled beforehand, not halfway through.

Agree the requirements

Together

System environment, network structure, sign-in method, and the question of which existing lists are to be migrated. The result is a clear split between what your IT provides and what we deliver.

Provide the server

Your IT

You provide a virtual machine running Linux with Docker, plus an internal DNS name and a certificate. The requirements are listed below and can be passed on as they stand.

Installation and setup

Linetrack

We install the application, the database and the reverse proxy, set up authentication and load your master data: projects, departments, resources, calendars.

Briefing and acceptance

Together

Your IT is briefed on start, stop, backup and restore, and receives an operations handbook. Acceptance runs against a set of test cases agreed in advance.

Feature set

The same software, just on your server

Running it yourself does not mean a reduced version. Whatever can be planned in Linetrack can be planned on your server – the interface your staff see is the same one.

Linetrack portfolio view showing several projects in one shared Gantt chart

Multi-project management and portfolio

Every running project in one overview, with dates, milestones and dependencies across project boundaries.

Portfolio and single project
From the overall picture down to the individual task, without switching planning tools.
Change history
Who moved which date and when stays traceable – stored on your server.

Linetrack resource utilisation overview across several departments

Scheduling and capacity planning

Capacity across all trades and departments, calculated against the tasks actually planned.

Utilisation instead of gut feel
Whether three more projects fit into the plan becomes a calculation.
No double booking
A resource booked twice shows up while planning, not on the day.

Linetrack planning view of an outsourced work package with dates and deliverables

Suppliers and external parties

External parties work on a clearly bounded section of your plan, with their own dates and deliverables.

Access from your network
Running it yourself, your IT decides how external parties reach the system – over VPN, through a hardened portal, or not at all.
Feedback inside the project
What the supplier reports lands on the task, not in an inbox.

The trade-off

What changes compared to us running it

Running it yourself solves exactly one problem: your data stays with you. Everything else we take care of becomes your IT department's job. Both sides are set out here.

	Operated by Linetrack	Operated by you
Where the data sits	Data centre in Germany, ISO/IEC 27001 certified	Your data centre
Internet access during operation	Required	Not required
Operation and monitoring	By Linetrack	By your IT
Backup and restore	Multi-tier, by Linetrack	By your IT, on your routine
New features and updates	Continuous, nothing to do	On request, as an agreed package
Time to go live	Short notice	To a project schedule
Mobile app	Included	On request, as its own build
Sign-in via Microsoft 365	Included	On request
Exchanging MS Project files	Included	Not included

This comparison describes the standard case. Which of the on-request items make sense for your installation is something we settle in conversation – some of them require an opening in your network that may conflict with your own IT policy.

Requirements

What your IT needs to provide

Nothing exotic: a virtual machine running Linux with Docker. These details are written so you can pass them to your IT department unchanged.

Virtual machine

At least 4 vCPU, 8 recommended. A dedicated VM, not a shared application server.

Memory

At least 12 GB, 16 GB recommended. Application, database and the plan export service run on the same machine.

Storage

At least 100 GB, 250 GB recommended. Consumption grows with project documents and attachments, not with the number of users.

Operating system

Debian 12 or Ubuntu 24.04 LTS with Docker Engine 24 or later and the Compose plugin. Root access for the setup.

Network and certificates

An internal DNS name and a TLS certificate from your own authority. The server only needs to be reachable where your users work.

Backups

Your existing backup routine for the VM and the database. We document which directories belong to it and how a restore is verified.

The full system requirements, including port rules and restore verification, come as an annex to the quotation.

Straight talk

When running it yourself is the wrong call

Not every company that asks for on-premise actually needs it. These three points are why most of our customers end up letting us run it after all.

Operations become your job

Availability, monitoring, operating system updates and certificate renewals sit with you. Without an IT department behind it, you are buying a standing task rather than a solution.

New things do not arrive by themselves

Your installation stays at the state it was delivered in. Further development is a separate, agreed piece of work – not something that happens overnight.

Recovery depends on your backup

A backup that has never been restored is not a backup. Running it yourself, your IT verifies that, not us – and the day it matters is the worst day to try it for the first time.

Common questions

Questions about running it yourself

Is running it yourself right for you?

In a short call we work out whether your requirement really calls for on-premise – and what it means for your IT department.

Does the full feature set run on-premise?

Yes, with one exception: exchanging MS Project files is not part of the on-premise installation. Project scheduling, the Gantt planner, resource and capacity planning, the portfolio overview, supplier access, templates, change history, the KPI dashboard, Excel import and PDF export of plans are all included.

Does the server need internet access?

Not for day-to-day operation. The installation works entirely inside your network. Internet access is only needed if you later have an update applied or want to use one of the optional connections.

How do new features reach our installation?

On request, as an agreed package. You tell us which function you need, or a security update becomes necessary. We look at your installation, work out the effort and quote a fixed price in advance. There is deliberately no automatic update when you run it yourself – nobody pushes software into your network unasked.

Can we keep using the mobile app?

On request. The app from the public stores connects to our environment and cannot reach your server. Your own installation needs its own app build, pointing at your server address and distributed through your device management.

Does sign-in via our Microsoft 365 work?

On request. Technically this is the most straightforward of the optional items, because the sign-in happens in your users' browser. It requires your IT to provide a corresponding application registration.

Can an AI assistant be connected?

On request, via an MCP interface. Worth knowing: the interface itself runs on your side, the assistant using it usually does not. Asking questions in natural language means opening a read-only path outbound. That should be a deliberate decision, not a side effect.

Can existing Excel and Access lists be migrated?

As a rule, yes. The effort depends on how your lists are built. If we look at two or three of them up front, we can size the migration reliably.

What if we later want you to run it after all?

That is possible, it is the same data. A move is a migration project with data transfer and a shutdown date for the old installation, not a switch. We plan it like the initial installation.

Linetrack on your server

Tell us what your policy requires and what system environment you have. We will tell you what an installation at your site would look like – and whether it is the right route.