Host Redmine without installing anything
Issue tracking that bends to your procedure: each role sees the transitions it is allowed to make, and none of the others.
Starting at €8.99/month
Introduction
Redmine installed, updated and backed up by us, on a machine in France. Complete project management: issue tracking, Gantt chart, timesheets, wiki and forums per project. A robust classic, still widely used in business. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Confort at €8.99/month incl. VAT — 4 GB of memory. Redmine is a Ruby on Rails application, and Rails loads all of its classes and plugins into every worker process: you need several to serve a team, and each has its own footprint. Add the computation of a Gantt chart on a busy project, the PDF export of an issue list, and full-text search. The 4 GB give room for several processes, which translates simply: pages appear without a wait.
People come here to replace Jira, Mantis, or a backlog kept in a shared mailbox. What Redmine does better than most is procedure: for each issue type and each role, you describe which state changes are allowed and which fields become mandatory at each step. An approval by the manager becomes a constraint of the software rather than a reminder in a meeting. Issues import from CSV and export the same way, a REST API covers the rest, and every project carries its own wiki, forum and files.
What managed hosting changes
Workflows described role by role
A matrix crosses issue types, roles and states: the reporter can move from "New" to "Resolved", only the manager can close. Fields can be made mandatory at a given step. That is what lets the tool fit a quality procedure rather than the other way round.
A Gantt chart that fills itself in
The "precedes" and "follows" relations between issues, the start and due dates and the versions produce the chart without drawing it. A date that moves shifts what depends on it, and slippage becomes visible before the progress meeting.
Timesheets you can actually use
Time is logged on the issue, with an activity — development, meeting, travel — and accumulates per project, per person and per period. Cross-tab reports export to CSV, so you can bill or justify a budget without retyping.
Projects, subprojects and their annexes
A project can contain others and inherit their permissions. Each has its own wiki, forum, documents and calendar, with distinct roles: a client can see their own issues without reaching the neighbouring project.
Why hand it over rather than install it
An engineering office and its milestones
Ten jobs in parallel, dependencies between tasks, and contractual dates. The Gantt shows the real sequence, and moving one study reveals what it pushes back.
A software house tracking its releases
Issues are attached to a version, the roadmap shows what is left before delivery, and release notes are built from closed issues. Bug tracking and planning no longer live in two tools.
A department that has to record an approval
A change request goes through review, then authorisation, then deployment, each step reserved for a role. The full history stays available, which is exactly what an audit asks for.
A team billing for time spent
Everyone logs hours on the issue, the project totals them by activity, and the export feeds the invoice. The client receives the detail, and gaps against the quote appear along the way.
A public body keeping fifteen years of history
Redmine is stable software whose data sits in an ordinary database. That is often why it is chosen: a tool you know will still be readable in ten years, and that does not change its interface every six months.
Hosted in France
An issue tracker holds client names, incidents and sometimes contractual matter. Yours stays in our own infrastructure in Nouvelle-Aquitaine, which we operate ourselves.
Frequently asked questions
Through Redmine's built-in CSV issue import. You export from the old tool, create the matching trackers, statuses and custom fields first, then map the columns. What CSV does not carry: attachments and the comment thread. Two strategies — bring over only the open issues and keep the old tool read-only for history, or go through the REST API to replay comments and files, which takes a small script.
Any issue list exports to CSV and PDF, with the columns and filters you chose, and time reports the same way. An Atom feed follows a project in a reader, an iCal feed shows due dates in a calendar. The REST API covers issues, projects, time entries and users, and the database reinstalls elsewhere as it is.
The interface is twenty years old and it shows: dense and efficient, not seductive. There is no kanban board as standard — that is a plugin, often a paid one. And here is the most important point: plugin compatibility across major versions is fragile, so the more you install, the more delicate upgrades become. Our advice is to use few. Finally, browsing a code repository assumes the repository is readable from the machine: on a hosted instance that means a clone kept up to date, which is not automatic.
App Confort, at €8.99/month incl. VAT. It provides 4 GB of memory where the application asks for 1 GB at minimum: the headroom serves the system, not the decor. You can change plan later without reinstalling.
Yes, they are part of the service. On a Rails application, updating is precisely the operation people postpone when they host it themselves; here it is applied and checked by us.