Redmine Hosting

How Redmine works

Administrators create projects, define trackers and issue statuses, assign roles, and configure which workflow transitions each role may use. Team members open issues, set priorities and dates, assign owners, add comments or attachments, and record time. Roadmaps, calendars, Gantt charts, and reports turn those records into broader project views.

Each project can include a wiki, documents, news, forums, files, and links to supported source-code repositories. PostgreSQL stores projects, issues, users, permissions, time entries, custom fields, and configuration. The default administrator credentials must be changed on the first sign-in before additional users are invited.

Key Redmine features

Custom fields and configurable workflows allow different teams to shape issue records without changing the underlying application. Cross-project views help managers search and report across several workstreams, while role permissions control what members may see or change.

Time tracking, version roadmaps, issue relations, watchers, and repository integration connect planning with delivery history. Plugins can extend Redmine, but each extension introduces its own compatibility and update considerations and is not included merely because it exists upstream.

Redmine vs Jira

Redmine is a self-hosted project and issue tracker with configurable workflows, roles, wikis, time tracking, roadmaps, repository links, and community plugins. Jira is a provider-managed project platform offering boards, backlogs, timelines, dashboards, reporting, automation, templates, and close integration with other Atlassian products.

Jira may suit organisations that want a polished hosted ecosystem, vendor administration, and extensive marketplace integrations. Redmine is more appropriate when a team values direct server control, flexible issue workflows, and a long-established self-hosted model, while accepting more responsibility for configuration and extensions.

Who uses Redmine

Software teams track defects and releases, engineering groups manage requests and milestones, and service departments organise internal work with custom issue types. Consultants can separate projects and permissions for different clients while still reporting across the complete installation.

The application can feel complex when roles, trackers, fields, and workflows are configured without a clear model. A small pilot should establish naming, permissions, and issue lifecycles before the system is opened to a broad organisation.

Self-hosting Redmine: requirements and cost

Workload depends on users, active projects, issue volume, attachments, search, custom fields, time records, repository integration, and plugins. PostgreSQL stores the core project data and is included with Redmine but remains unmanaged. Its memory sits outside the application minimum, so the database-adjusted recommendation moves up one plan.

Redmine carries no separate hosted software fee, and AvaHost maps the stack to Plan 2 at €5. One-click deployment, a custom project domain, automated HTTPS, automatic application updates, and scheduled backups are included. Application email is disabled, so issue notifications, invitation mail, and email-based password recovery do not operate on this service.