How working together works.

Who you are dealing with

Keeps Running is a sole operator business run by Aryan Neopane. There is no team behind it. The person who quotes the work is the person who builds it and the person who answers when something breaks.

Prices and scope

The prices published on this site are fixed prices for a standard scope, and they are ceilings rather than starting points. They are what the described job costs.

Before anything starts I will confirm in writing what is included, what is not, and what the price is for your specific job. That written confirmation is the agreement — it takes precedence over anything on this website, which is a description rather than an offer.

If you ask for something outside the agreed scope while the work is under way, I will tell you what it adds before I do it. You will not receive a surprise line on an invoice.

Payment

Half the fixed price up front, half when the work is live and handed over. Monthly services are billed monthly in advance.

There is no hourly billing on fixed-price work. If a build takes longer than I estimated, that is my problem and my cost, not an adjustment to your invoice.

What every build includes

Deployment to infrastructure you own. Structured logging and alerting, so a failure reaches a person. A one-page runbook covering how it runs, how to restart it and what to check first. The source code in a repository you control. Thirty days of fixes after handover at no charge.

The thirty days covers defects — the thing not doing what we agreed it would do. New features and changes of mind are new work, quoted separately.

Timelines

The durations on this site are honest estimates from having done the work before, not guarantees. Delays caused by waiting on access, credentials, content or decisions from your side move the finish date accordingly, and I will say so at the time rather than at the end.

Who owns the work

You do. On final payment, the code written specifically for you, and the deliverables that go with it, are yours outright. You can modify it, extend it, or hand it to another developer without asking me.

I keep the right to reuse general knowledge, techniques and non-client-specific building blocks in other work — the ordinary tools of the trade. Nothing confidential to you and nothing written specifically for you is reused elsewhere.

I would like to describe the work publicly as a case study. I will always ask first, and I will accept no as an answer.

Costs you pay directly

Domains, hosting, and any paid API or model usage are billed to you by those providers, not by me. I will set the accounts up in your name and estimate the running cost before we start. That money never passes through me, so there is nothing marked up.

Cancellation

You can stop a project at any point. The deposit covers work already done and is not refundable, but you keep everything completed to that point, including the code.

If I cannot deliver what we agreed, I will tell you as soon as I know and refund the deposit in full. I would rather return money than hand over something that does not work.

Monthly services can be cancelled with thirty days' notice, after any stated minimum term.

After handover

Once the thirty days are up, you are not obliged to keep paying me anything. Everything runs on your infrastructure, from your repository, and the runbook is written so another developer can pick it up.

Monitoring afterwards is optional and priced on the services page. Plenty of builds never need it.

Warranties and limits

I will do the work with reasonable skill and care, and fix defects reported within the thirty days at no charge.

Beyond that, the work is provided as it is. Software that depends on third-party services can be affected when those services change, and I cannot warrant that an outside provider will not alter or withdraw something it offers.

My total liability for any claim connected to a project is limited to the fees you paid me for that project. I am not liable for indirect or consequential losses, including lost profit or lost data. Keep your own backups — every build I ship includes them, and you should verify they are running.

Nothing here limits liability that cannot lawfully be limited.

Confidentiality

Anything you share with me about your business stays private, during the project and afterwards. I will sign your NDA if you have one. If you do not, treat this paragraph as the commitment.

Governing law

These terms are governed by the laws of the State of Colorado, USA.

One honest note

I am an engineer, not a lawyer, and these terms are written to be clear rather than to be exhaustive. They are meant for the size of work described on this site. If you are procuring something substantial, or your organisation has its own contract, send it over — I would rather sign your paperwork than argue about mine.