Most business software is sold, installed, and then quietly stops working.
Keeps Running exists for the third part of that sentence. Anyone can build the automation. What decides whether it was worth buying is month seven — when a vendor changes an API, a disk fills up, or a scheduled job fails at two in the morning and nobody finds out until a customer does.
So every build here goes onto infrastructure the client owns, with logging, alerting and backups, and a written runbook for running it without me. No platform to rent back, no account to keep paying for, nothing that stops working if I stop answering the phone. If the relationship ends, the system does not.
The price list is not the edge of the work. Those are the jobs quoted publicly because they come up most often and their scope is well understood. Plenty of what I take on is not on that page: an internal tool nobody sells off the shelf, a system someone else built and abandoned, a process that lives in one person's head and needs to not. If what you need is not listed, describe it — you will get a straight answer about whether it is a good fit, including when it is not.
This is one person, on purpose. There is no account manager between you and the person writing the code, no junior doing the work under someone else's name, and no queue. That means a fixed price agreed before anything starts, a direct line while it is being built, and an honest no when a job is better served by something off the shelf.
Keeps Running is me, Aryan Neopane — a software engineer in Aurora, Colorado. I build every system myself and run the servers they live on.