Skip to content

Customer story / IT Consulting

Olbuz logoAhmedabad, India · 27 people

Backups stopped waiting on a developer.

How Olbuz brought files, deployments, monitoring and scheduled backups for four servers into one local app.

Read their story
The backup workflow

Before CtrlOps

  1. Request a backup
  2. Wait for an available developer
  3. Trigger the backup manually

With CtrlOps

Scheduled

Set a schedule.
Let backups run.

No recurring request to a developer to start each backup.

Servers in one local app
4Across multiple client projects
File-transfer tools replaced
2Cyberduck and FileZilla
Workspace for server work
1Terminal, files, deploys, backups and monitoring
About Olbuz
Olbuz logo

IT Consulting

Ahmedabad, India27-person team

Visit website
In this story

The Challenge

Olbuz runs multiple client projects at once, each with its own server, its own deployment needs, and its own maintenance routine. Like most growing IT consulting teams, the gaps in the stack grew faster than anyone wanted to admit.

File transfers ran through two separate tools. Cyberduck and FileZilla handled moving files to and from servers. They did that job, and nothing else. Anything past a file transfer meant leaving them and picking up something different.

Infra monitoring and backups had no dedicated tool at all. Checking server health and running backups were manual tasks, done by hand rather than through any system built for it. The gap was not a bad tool, it was no tool.

Server credentials were saved in Notepad. Developers on the team kept IPs and access details in plain text files. It worked, but it was never a convenient or reliable way to manage credentials.

Backups needed a developer to trigger them. With no automation in place, someone had to step in and start the process by hand every time, which made backups depend on whoever was free rather than on a schedule.

Before

Separate tools + manual work

  • File transfers

    Cyberduck + FileZilla

  • Backups

    A developer starts each run

  • Monitoring

    Server health checked by hand

  • Server access

    Credentials kept in Notepad

Two file-transfer tools, with the rest handled manually.

After · CtrlOps

4 servers

One local workspace

  • File transfers

    Built-in file management

  • Backups

    Backups run on a schedule

  • Monitoring

    Infra details visible in the app

  • Server access

    Access managed in CtrlOps

Plus terminal access and one-click deployment.

Two file-transfer tools replaced. Manual backups, infra checks and credential handling brought into one workspace.
“Previously, I had to rely on separate applications to access the terminal and manage server files, which was less convenient and interrupted my workflow. With CtrlOps, everything is available in one place through a clean and user-friendly interface.”
Rakesh PatelRakesh PatelTech Lead, Olbuz

The Turning Point

Jignesh Gohel, Founder of Olbuz, found CtrlOps through a LinkedIn post. With a 27-person team where only a handful of people touch server infrastructure directly, the appeal was straightforward: one local app that was fast, easy to set up, and did not require a separate panel installed on every VPS.

What stood out early was how quickly it loaded and responded, since everything ran on the local machine instead of round-tripping through a cloud service.

What Changed With CtrlOps

CtrlOps replaced Olbuz's file transfer tools and manual infra and backup work with a single local dashboard covering terminal access, file management, one-click deployment, backups, and infra monitoring.

One app for files and everyday server work

Terminal, file manager, deployments, backups, and infra monitoring now run from the same screen, replacing two separate tools and the manual checks that used to fill the rest of the gap.

PEM key connections that just work

Server connections and PEM key setup are straightforward, without the manual back and forth the old tools required.

Credentials out of Notepad

Server access is now managed inside CtrlOps directly, instead of a plain text file developers had to maintain by hand.

Backups that no longer wait on a developer

What used to be a fully manual process is no longer a recurring interruption for whoever happened to be available, because backups now run on a schedule.

Infra visibility without a panel

Server details are visible directly inside CtrlOps, with no separate panel needed on the VPS itself, and no more manual checks to get the same picture.

Local-first, and it shows

Because everything runs on the device rather than through the cloud, the day-to-day experience is simply faster.

The Results

Since switching to CtrlOps, the shift at Olbuz has been practical and immediate:

Olbuz before and after CtrlOps
BeforeWith CtrlOps
File transfers: Cyberduck and FileZillaFile management inside CtrlOps
Backups: A developer triggered each runBackups run on a schedule
Infra monitoring: Manual server-health checksInfra details visible in the app
Credentials: Access details in NotepadServer access managed in CtrlOps
Server workflow: Separate tools and manual work4 servers, one local workspace

Developers handle routine server work themselves, so the team's infrastructure time goes to the harder problems instead of day-to-day requests. Backup scheduling no longer needs a manual trigger from a developer, and day-to-day server work is faster since everything runs locally instead of through the cloud.

For Rakesh, the bigger shift was not just replacing two tools. It was that infra checks and backups stopped being manual work that fell on whoever was available, and credentials stopped living in a text file no one fully trusted.

“Earlier there was a need to trigger the developer for backups, but now that's gone. Server connections and PEM key setup are easy, and infra details are visible without needing a panel on the VPS.”
Rakesh PatelRakesh PatelTech Lead, Olbuz

Who This Is For

Based on running CtrlOps across a multi-project, multi-server IT consulting setup, this fits teams in a similar position: multiple client servers, file transfer tools that only cover part of the job, manual infra and backup work filling the rest, and a preference for one local app over that patchwork.

About Olbuz

Olbuz is an IT consulting company based in Ahmedabad, India, providing web development and digital marketing services. The 27-person team, led by Founder Jignesh Gohel with Tech Lead Rakesh Patel, runs 4 servers across multiple client projects through CtrlOps.

More
customer stories.

See how other teams make server work a smaller part of their day.

Make server work
a smaller part of your day.

One workspace for your servers. More time for the work you actually want to ship.

Download for MacDownload for WindowsBook a demo

14-day free trial, no credit card required.

Your privacy preferences. We use product analytics to improve CtrlOps. Google measurement runs without analytics cookies. Live chat stays off until you allow it. Cookie policy