Projects, requests and knowledge — on your own server.

MGProject and MG-WIKI are two applications for the daily work of a team: an issue tracker with sprints, a helpdesk and time tracking, and a wiki for the knowledge that grows alongside it. They run on a Linux server in your own network. If running it yourself is more than you want, we will run it for you.

Downloads Register, no strings attached

Both applications are currently in beta. We use them every day ourselves, but they are not yet cleared for production use at customer sites.

Two applications that know about each other

Each works on its own and is licensed on its own. Together they share sign-in, the user directory and their links: a wiki page shows the state of the issues, an issue points at the documentation.

MGProject

6.11.6 BETA

Issues, sprints and hours in one system

A complete issue tracker for teams who would rather not spread projects, support and development across three tools. You define the issue types, workflows, fields and screens yourself — and nobody else decides when any of that changes.

Issues and workflowsYour own issue types, transitions, conditions and post-functions. Fields, field configurations and screens per project.
Scrum and KanbanBacklog, sprints with a goal and a length, a board with swimlanes, burndown, and a planning overview across every project.
HelpdeskA customer portal with your own request types, queues, SLA clocks and incoming mail landing straight on the issue.
Time trackingHours booked on the issue, clock-in and clock-out with a daily journal, and reports by person, project and period.
Search and reportingA JQL-compatible query language, saved filters, dashboards with gadgets and CSV export.
ConnectionsEntra ID and LDAP for sign-in, Bitbucket for commits and branches, and an importer for existing Jira projects including their history.

Download MGProject

MG-WIKI

1.04.3 BETA

What the team knows, in one place

A wiki with spaces, page trees and versions. Meant for documentation that grows alongside the daily work, and that therefore has to be quick to write.

WritingAn editor with tables, images, code blocks and templates. Every change makes a version; versions can be compared and restored.
StructureSpaces, nested page trees, labels and a full-text search that reaches into attachments as well.
MacrosTables of contents, page lists, notice boxes, status markers, diagrams and embeds from MGProject.
Working togetherComments, mentions with notifications, watch lists and drafts nobody else can see.
Public help pagesPublish selected spaces as a lean, readable help site — no sign-in for your customers.
PermissionsRights per space and per page, sign-in through Entra ID or locally, and read-only mode for expired licences.

Download MG-WIKI

Why your own server is the quieter choice

Moving into someone else's data centre has cost many teams both money and control. These six points are what we hear most often from customers who want to come back in-house.

Your data stays in your house

Issues, attachments, customer requests and hours sit in a PostgreSQL database only you can reach. No data processing agreement, no transfer to a third country, no discussion at the next audit.

No migration anybody imposes on you

You decide when a new version goes in — and whether it goes in at all. An update is one call to deploy.sh and takes about a minute; configuration and database are left untouched.

Works without the internet

Production floor, laboratory, isolated network: after installation the application needs no connection to the outside. Licences are checked offline.

Costs you can plan for

One licence per user tier instead of an invoice that comes out differently with every change of pricing model. What you have licensed keeps running.

Modest requirements

A Linux server with two cores and 4 GB of RAM carries both applications for a team of fifty. It runs as a systemd service behind the reverse proxy you already have.

You can always leave again

Full export to CSV and JSON, attachments as files, and the database is yours. No format only we can read.

At your place or ours

MGProject comes both ways. The application is the same one; the only question is who looks after the server. You can switch later, in either direction, and take your data with you.

MG-WIKI currently runs on-premise only. A cloud edition is in preparation.
	On-premise You run it yourself	Moregate Cloud We run it for you
Where the data sits	On your server, in your network	In our data centre in Germany
Operation	Your administrators	Us: updates, backups, monitoring
Access from outside	Only as far as you open it	Over HTTPS, restricted by IP on request
Updates	You decide when	Announced in advance, in a maintenance window
Directory integration	Straight through LDAP or Entra ID	Through Entra ID
Changes to the system	Complete, down to the database	Through configuration and interfaces
Cost	A one-off licence per user tier	Monthly per user, hosting included
Getting started	deploy.sh on a Linux server	Your environment by the next working day
	Download the package	Ask for cloud access

Installation and updates

Both packages ship with a deploy.sh. It creates the service user, the directories, the virtual environment and the systemd unit, binds the application to localhost and checks for itself that it answers. The same command is the update later on: code and dependencies are renewed, configuration and database are left alone.

Requirements: Linux with systemd, Python 3.9 or newer, PostgreSQL or SQLite. Two cores and 4 GB of RAM carry a team of fifty.
Operation: The application listens on 127.0.0.1 only. For TLS and the public address you put your existing reverse proxy in front — HAProxy, nginx or Apache.
Sign-in: Local accounts, LDAP or Entra ID. Two-factor with TOTP or a passkey is built in.
Licence: One signed licence file per installation, checked offline. When it expires the system falls back to read-only — it never locks you out.