Home · About · Services · Industries · Projects · Products · Process · Blog · FAQ · Contact
Linux servers that are set up properly and stay that way. Linux server administration services for Ubuntu and Debian: provisioning, user and SSH access, systemd services, patching, troubleshooting and clear runbooks.
Our Linux server administration covers Ubuntu and Debian servers that run applications, databases and internal tools. That means a clean base install, named user accounts with SSH keys and sudo rules, your services running under systemd with logs you can read, and security updates applied on a schedule. When something breaks, we find the cause rather than restarting until it goes away. Every change is written down, so the server is never a mystery to the next person who logs in.
What we usually find when we log in. Everyone shares one login The team connects as root or a single shared user with a password, so nobody can tell who changed what, and removing a leaver means changing it for everyone.
Nobody knows how it was built The server was set up by hand years ago. Packages, cron jobs and config edits were added over time and none of it is written down.
The app is kept alive by hand Processes run inside a screen or tmux session or a nohup command, so a reboot or crash takes the application down until someone notices.
Updates are postponed indefinitely The release is near or past end of standard support, security patches pile up, and everyone is afraid that upgrading will break something.
What our Linux administration covers. Provisioning Ubuntu LTS or Debian stable installed on cloud instances, VPS or physical servers, with partitioning, swap, time sync, hostname, locale and a minimal package set.
Users and access One named account per person, SSH key authentication, password and root login disabled, sudo rules per role, and a simple process for adding and removing people.
systemd services Your applications, workers and scheduled jobs written as systemd units and timers, with restart policies, resource limits, environment files and logs in journald.
Patching and upgrades Security updates through unattended-upgrades, planned reboots for kernel updates, and release upgrades tested on a copy of the server before production.
Firewall and network UFW or nftables rules that open only what is needed, database ports limited to approved IPs or a Tailscale network, Fail2ban on exposed services, and a check that Docker-published ports are not bypassing the firewall.
Web server and TLS NGINX as a reverse proxy for one or many domains, with Let's Encrypt certificates that renew on their own, including wildcard certificates through DNS validation.
Troubleshooting Disk full, services that will not start, memory pressure, slow responses, broken DNS or expired certificates, diagnosed from logs and metrics with the root cause written up.
Documentation and hand-over A server record covering what is installed, where configuration lives, how to deploy and how to recover, stored in your repository rather than ours.
Engagement options Server setup A fixed-scope project to provision new servers, or rebuild an undocumented one, and hand it over to your team.
Base install and hardening User, SSH and sudo setup Applications moved under systemd Server record and hand-over session Managed Linux administration A monthly retainer where we look after your servers alongside your developers.
Patching and planned reboots Access changes for joiners and leavers Troubleshooting and incident response Coverage hours and response times agreed in the retainer Server health check A one-off review for a server you have inherited or have stopped trusting.
Access, users and SSH review Patch level and support status Services, logs, disk and backups A written, prioritised fix list How it works Access and inventory You give us a named account. We record the OS release, installed packages, running services, open ports, cron jobs and users before changing anything.
Written plan We send a short plan listing what we will change, in what order, what needs downtime, and how each step can be rolled back.
Changes in small steps Work is done in maintenance windows you approve, with a second SSH session kept open during access changes so nobody gets locked out.
Hand-over or ongoing care On a project you receive the server record and runbooks. On a retainer we keep the server patched and respond when something goes wrong.
Why Infigini We run Linux ourselves Our private hybrid cloud of Ubuntu 24.04 instances for development and test, a campus server for a college group and a shared deployment server for a client are all Linux machines we administer.
We also write the software The same engineers build Python, Node.js and database-backed applications, so we can tell a server problem from an application bug and fix either.
Boring, standard choices We use the distribution's own packages, systemd, UFW and NGINX before anything exotic, so any competent administrator can take over later.
You keep the keys Servers, cloud accounts and credentials stay in your name. Our access is a named account you can remove at any time.
Technologies: Ubuntu LTS, Debian, systemd, OpenSSH, UFW, nftables, Fail2ban, NGINX, Let's Encrypt, Tailscale, PostgreSQL, Docker
Related projects Campus Server Platform — The central server for a college group, hosting every project API, database and subdomain on one instance.
Self-Service Deployment Server — A shared server that lets anyone in the organisation deploy applications through CI/CD to multiple domains and subdomains.
High-Performance Hybrid Cloud — A multi-node private cloud for development and test environments, with mesh networking and a web control plane.
Frequently asked questions What do Linux server administration services include? They cover the work of keeping a Linux server correct and available: installing and configuring the operating system, managing users, SSH keys and sudo, running applications as systemd services, applying security updates, configuring firewalls and NGINX, renewing certificates and fixing problems when they happen. We agree the exact scope in writing and record every server we look after.
Do you support Ubuntu, Debian and other distributions? Our main work is on Ubuntu LTS and Debian stable, which is what most of our clients and our own infrastructure run. We also work with Amazon Linux on AWS. If you run something else, such as a RHEL-compatible distribution, tell us what it is and we will say honestly whether we are the right fit.
Our server runs an old Ubuntu release. Can you upgrade it safely? Usually, yes. We take a full backup or snapshot, then rehearse the upgrade on a copy of the server to see which packages, PHP or Python versions and config files change. Upgrades go one LTS release at a time. If the jump is large, building a fresh server and moving the application across is often cleaner, and we will recommend that when it is.
How do you manage access for our team and for yourselves? Everyone gets a personal account with an SSH key, and root and password logins are turned off. Sudo rights are granted per role, so commands are logged against a name. Our engineers use their own named accounts too, which you can disable at any point. When someone leaves, removing their access is one documented step.
Can you fix a server that is down or misbehaving right now? Yes, if you can give us access. We start with the basics: disk space, memory, failed systemd units, recent journal entries and what changed last. Once the service is back, we write up the cause and the change that prevents it happening again. For clients on a retainer, response times are agreed in advance.
How is Linux server administration priced? Setup and rebuild work is quoted as a fixed price after we have seen the servers. Ongoing administration is a monthly retainer based on the number of servers, how much changes on them and the coverage hours you need. Health checks are a fixed-scope piece of work. Send us a short description of your servers and we will reply with an estimate.
Will we be locked in to you? No. Servers and accounts stay in your name, configuration lives in your repository, and we use standard tools any Linux administrator will recognise. If you hire in-house or move to another provider, the server record and runbooks are already there, and we will walk the new person through them.
Do you also handle containers, backups and monitoring? Yes, as part of the same retainer or as separate pieces of work. We run Docker and Docker Compose on the servers we manage, set up scheduled backups with tested restores, and add uptime and resource monitoring with alerts. Where a need grows larger, such as Kubernetes or a full disaster recovery plan, we cover it under our related services.
Further reading Linux server disk full: how to find and free space safely
Running apps as systemd services: a production unit file guide
SSH hardening checklist for Linux production servers (2026)
Monthly server maintenance checklist for Linux servers
Ubuntu server initial setup: the first hour, step by step
Infigini IT Services · 11 Kanwali Road, Dehradun 248001, India · info@infigini.com · +91 95684 87789