Redmine, supercharged and run for you. Full Redmine admin access on every plan, from $29/month for 25 users, in the region you choose.
Managed Redmine hosting is Redmine run for you by a provider rather than installed on a server you own. The provider is responsible for the machine, the Ruby and Rails stack, the database, security patching, upgrades and backups. You get a working Redmine at a web address and you configure the application itself.
Redmine cloud and Redmine SaaS are the same product under different names. All three phrases describe software delivered as a service instead of a download, and the choice between them is a matter of what a buyer types into a search box rather than a difference in what arrives. RedminePRO is all three.
The distinction that does matter when you compare vendors is not cloud against self-hosted. It is whether the hosted version is still Redmine. Some offerings are a fork with a different data model. Some keep stock Redmine and withhold the administration panel. RedminePRO is stock, current, open-source Redmine with the admin panel included, which is why the rest of this page can talk about what you control rather than what you are permitted to request.
No SSH, no bundle install, no 2am patch window, no migration script that fails at step 14. The word “managed” is used loosely in this market, so here is exactly what it covers.
Provisioning and scaling. Your workspace is created, sized and kept sized. Growth is a plan change rather than a migration project.
Redmine version upgrades. We run the upgrade: the application, the database migrations, the compatibility checks and the rollback plan. Redmine 7.0.0 was released on 30 June 2026 and requires Rails 8.1 and Ruby 3.2 or later, checked against redmine.org on 2 August 2026. Self-hosted, an upgrade of that shape usually means moving the Rails major version, the Ruby version and often the database together. That is precisely the class of work that stops being yours.
Patching. Operating system and stack patches are applied on our schedule rather than yours. Ruby and Rails advisories land regularly, and on a server you run yourself, applying them is somebody's unbudgeted evening.
Backups with point-in-time recovery. Backups are continuous and encrypted. Point-in-time matters more than a nightly copy does: if someone bulk-edits 400 issues at 14:20, restoring to 14:19 is a different outcome from restoring to midnight.
Encryption. AES-256 at rest on databases and disk volumes, TLS 1.2 or higher in transit on all services and APIs.
Monitoring and incident response. Uptime and health monitoring with our team responding, rather than an alert that wakes you. The Business plan carries a 99.9% uptime SLA. Enterprise carries a custom SLA and DPA.
24x7 support in English, on every plan, including the entry tier. Priority support is included from Business.
“Managed” should describe the infrastructure, not your permissions. A good deal of managed Redmine takes the server off your hands and takes the administration panel with it, and the restriction is easy to miss when you are comparing prices because it never appears in a pricing table. It appears the first week you need a new tracker.
Every RedminePRO plan includes the real Redmine administration interface on your workspace: trackers, workflows, statuses, custom fields, roles and permissions, authentication, notification rules. Not a curated subset, and not a support ticket that reaches an engineer who makes the change on your behalf. That matters because extensibility is the reason teams choose Redmine in the first place. A tracker for change requests, a custom field an auditor asked for, a workflow that matches how the team actually works. A managed Redmine that fences off the admin panel has removed the reason you picked Redmine.
It is also the claim on this page most worth checking rather than believing. The live demo hands you the demoadmin login and the same Administration panel every paid plan includes.
You choose your region at signup, from four: the United States, the European Union in Ireland, France in Paris, and India. Your workspace data resides in that region. Not “primarily”, not “usually”. It stays there.
That single choice settles most of the data-residency conversation before it starts, and it is a question every procurement review asks. A chosen region is a written answer for your customer's questionnaire. An assigned one is a shrug. Teams buying from India have their own page covering local pricing: Redmine hosting in India. If you need a region outside those four, talk to us about Enterprise.
Choose at signup: US · EU · FR · IN
How the platform is secured, in detail.
These are worth asking of every provider you shortlist, including this one. Price is the easiest thing to compare across hosts and the least likely to be what you regret.
1. Do you get the administration panel? This decides whether changing a tracker, a workflow or a permission is something you do or something you request. It is the most common restriction and the one people notice latest, because it costs nothing until the week it costs a lot. RedminePRO's answer: yes, every plan, from the entry tier.
2. What exactly does the export contain, and what does it cost? Ask for the database and the files archive, not a CSV. A vendor who answers with a support process rather than a file format is telling you about the next five years. RedminePRO's answer: full database dump and files archive on request, any time, no fee.
3. Which region does the data sit in, and do you choose it? There is a real difference between picking a region and being assigned one, and it shows up in procurement rather than in engineering. RedminePRO's answer: four regions, chosen by you at signup, and the data stays there.
4. Will they migrate you, and what does that cost? Migration is where most moves stall. “We provide documentation” and “our engineers do it” are different products at the same price point. RedminePRO's answer: done for you, after a free assessment, then a quoted one-time fee.
A fifth question is worth asking if you are moving from another host rather than from your own server: is it stock Redmine or a fork? A fork's data has nowhere standard to go, and that single fact decides whether your next migration is a restore or a rebuild. Two of the comparison pages go through this in detail: managed against self-hosted and the full provider comparison.
Worth saying plainly, because a page that only lists wins is not much use when you are deciding. Managed hosting takes the operational work. It does not decide how your team should track work, and moving to it will not fix a tracker nobody agreed on. If your current Redmine is unloved because the workflow was never settled, the same workflow arrives here running faster.
It also does not remove the work of a migration, it relocates it. Someone still has to decide what comes across, what gets archived and what quietly stops being used, and those are your decisions rather than ours. What changes is that the server work, the version work and the recovery plan stop being anyone's side project. For most teams that is the whole of the problem. For a few it is only half, and those teams are better served knowing that before they move rather than after.
Flat tiers. No per-user fees on any plan, unlimited projects on every plan, and storage from 50 GB to 1 TB.
| Plan | Monthly | Users | Storage |
|---|---|---|---|
| Startup | $29/mo | Up to 25 | 50 GB |
| Plus | $79/mo | Up to 100 | 100 GB |
| Business | $199/mo | Up to 250 | 250 GB |
| Enterprise | On quote | Unlimited | 1 TB |
Annual billing is ten months' price for twelve, which the site describes as two months free. Registered non-profits get 30% off the Business plan. Every plan includes full Redmine admin access, unlimited projects and 24x7 support, and the higher tiers add capability rather than unlocking the basics. Full pricing and plan comparison, and what each plan includes.
There is no free plan. The way in is a 7-day trial with full access to the plan you choose. A card is required to start it, and billing begins on day 8 unless you cancel. If you would rather look around first, the demo needs nothing at all. Teams looking specifically for a no-cost route have their own page: free Redmine hosting options.
Moving to managed hosting is the part people put off, so we do it. The assessment is free. The migration itself is a one-time professional-services fee, quoted after that assessment, so the number is known before anything moves.
We migrate from self-hosted Redmine, from Jira and from other trackers: projects, issues, wikis, attachments, users and years of history, typically in hours. You do not touch a server. If you are on a Docker Compose stack somebody set up in 2019, or on a box whose last upgrade is a mystery, that is the normal case rather than a hard one. How migration works.
Managed Redmine against self-hosted Redmine is the right comparison if you are running your own server today and costing out the move. The provider comparison puts published figures from every managed Redmine vendor side by side, each with its source and the date it was checked. Free Redmine hosting covers the no-cost options honestly, including what they are genuinely good for and where they stop being appropriate.