Hosting, delivery and operations
Getting software live and keeping it there. Hosting on your accounts, deployments that are boring, monitoring that reaches a person, and costs you can predict.
- Kind
- Operate
- Timeline
- 1 to 3 weeks
What this is
The work between "it runs on my laptop" and "customers rely on it". Accounts, domains, certificates, environments, deployment pipelines, backups, monitoring, alerting and cost control. We set this up on every project we build, and we also do it for software built by others.
What you get
- Hosting on your own accounts, in your name, with us as invited collaborators who can be removed in one click.
- Two environments at least: a test address where changes land first, and production. Promotion is a button, rollback is a button.
- Deployments from the repository on every merge, with checks that must pass first. No deploy from a laptop.
- Backups taken automatically and restored on a schedule to prove they work.
- Monitoring and alerts that reach a named person by the channel they actually read, with runbooks for the common cases.
- A monthly cost you can predict. Most systems we build cost less to host than one lunch.
Where it runs
On the platform that suits the work and your company: a serverless edge platform for most business software, or Azure, AWS or Google Cloud when you already run there or the workload needs it. We say which and why in the scope, in writing, and the account is always yours.
Typical scope
- Taking an existing application from a single server to a reproducible, monitored deployment with test and production environments.
- Setting up accounts, domains, email, DNS and secrets for a new company or product, properly, once.
- A cost and reliability review of what you run today, with the fixes done.
Timeline
One to three weeks for a full setup; days for a review.