In IT and development departments, the tools everyone else works with sit with you: issue tracker, wiki, repositories, credentials. Running them happens on the side.
We see this constellation often. Redmine is used intensively, but nobody has the time to take care of updates, security patches and backups. Self-hosting ties up resources that are missing in actual development.
We take over operation. Redmine runs in our cloud in Germany or on your server.
What your team does with it
- Tasks and ownership in one system. Issue tracking, roadmap, wiki and forums are part of the Redmine standard. Development, administration and support work in it with separate roles and permissions.
- Source code on the issue. The DevOps plugin connects GitLab and GitHub. Commits appear on the matching issue, deployments stay traceable.
- Credentials in the team. The Passwords plugin manages credentials by role, in the same system instead of a second application.
- Inventory and records. Hardware, licenses, SSL certificates, supplier contracts and technical specifications live in the DB plugin. Custom fields, filterable.
- Recurring work by rule. The Automation plugin creates issues, assigns them and reminds you of dates. Typical cases: onboarding, maintenance windows, certificate renewal.
- Reports without an export. The Reporting plugin delivers dashboards, effort reports and SLA times from data already in the system.
What that means day to day
- Cloud in Germany or your own server. With InHouse operation, SSH access restricted to our IP is enough.
- Redmine and GitLab from one provider. One contact, one server location, connected through the DevOps plugin.
- No user limits. Whether 50 or 500 people work in it, the hosting costs the same.
- We handle the updates. Security patches every four hours, major versions only after a plugin check.
Prices are listed openly on the hosting page, GitLab has its own overview.