What our engineers handle on GitLab (self-hosted)
This is the hands-on work, done by a person: the jobs the automatic tools cannot do for you.
- 1Follow the upgrade path, including required stops, with a backup and a rehearsal
- 2Back up repositories, database, uploads and the configuration and secrets file
- 3Manage runners, registry and storage, and clear old artefacts
- 4Set up email, SSO and TLS, and size the server for the team
Problems we fix
Problem
An upgrade failed halfway
What we do
We read the logs, restore from the pre-upgrade backup if needed and re-run the upgrade through the correct path.
Problem
GitLab is slow or runs out of memory
What we do
We tune Puma, Sidekiq and PostgreSQL to the server size, or recommend a larger instance.
Problem
Backups exist but do not include secrets
What we do
We add the configuration and secrets files to the backup, and test a full restore.
Automatic tools, and our team for the rest
RootManage is automatic server management with every tool in one place. The tools run by themselves on a schedule and report to one dashboard. Everything they cannot do, and every emergency, is handled by our engineers by hand.
Automatic
RootManage tools, running by themselves
- Server Health agent reports load, disk use and failed login attempts to your dashboard.
- Metrics agent draws CPU, memory, disk and network charts, sampled every five minutes.
- Uptime checks check the server every minute and email you when it stops answering, and again when it recovers.
- Backup agent runs scheduled backups at 02:00 IST to storage we provide or to your own SFTP or S3 box, with help restoring.
Manual, by our engineers
Everything else, and every emergency
- Hands-on work. Fixes, tuning, migrations, upgrades and the other jobs listed above on this page.
- Emergency work. A hacked site, an outage or a failed update is handled by a person who investigates and fixes it, not by a script.
- Things we do not automate. Anything the tools do not cover is done by hand, over SSH, WHM or RDP, on a login you can remove at any time.
The tools are optional, run on Linux servers and are installed by you with one command each. Every job our team does is recorded as a task in your dashboard with the details, and you get an email when it is updated.
How it works
- 1
Sign up
Create an account, choose a plan and add the server you want managed.
- 2
Install the tools
Run one command per tool. They then work by themselves and report to your dashboard. For hands-on work you give us a login you can remove at any time.
- 3
Automatic, with people behind it
The tools watch, scan and back up automatically and alert you. Our engineers do the rest by hand and handle every emergency, and you follow each task in your dashboard.
Questions about GitLab (self-hosted)
GitLab or Gitea for a small team?
Gitea is much lighter. GitLab brings built-in CI and more features. We run both and recommend by team size and needs.
Can you move us from GitHub to self-hosted GitLab?
Yes. We set up the server and import repositories and issues, and configure runners.
What does it cost to have GitLab (self-hosted) managed?
Managed plans start at ₹1,999 a month for one server, and GitLab (self-hosted) is managed as part of the server. The pricing page lists what each plan includes. If a server is already infected, the emergency cleanup is a one-time ₹9,000 job.