What We Do
Six things we do, priced before we start
Every engagement is a fixed scope with a written plan, or a monthly retainer with a set number of hours. We will tell you when a piece of work is not worth doing.
Migration
On premises to AWS or Azure, data center to colo, or one cloud to another. We inventory what you run, rehearse the move on a copy, and cut over on a weekend with a rollback written down and tested.
Dependency map so nothing moves before the thing it depends on
Cost model for the first twelve months in the new place
Two rehearsals before the real cutover, in a copy of production
Platform Engineering
We replace fragile, hand-built infrastructure with automated, version-controlled systems that are easy to reproduce and easy to reason about, across AWS, Azure, VMware, or hybrid environments.
Terraform / OpenTofu module design and self-service provisioning
Golden-path templates so new environments are consistent by default
Migrating undocumented, hand-configured systems into version control
Digital marketing
An independent design studio, discovery-led, building an identity and a site made specifically for your business rather than assembled from templates.
Discovery-led brand and naming direction, shaped around your business
Custom visual identity: logo, color palette, typography, brand patterns
Fully original web design and layout — no AI-generated templates
Managed services
Patching, backups, monitoring, and a number that a person answers. We test restores every quarter and send you the result. Month to month, cancel with thirty days notice, no three year contract.
Quarterly restore test with a written result
Named engineer who knows your setup, plus a backup engineer
Flat monthly price by device count, published on your invoice
Digital transformation
Paper forms, a shared spreadsheet, and one person who knows how it all works. We replace that with systems the whole team can run, and we train the team on them before we leave.
We watch the current process for a day before proposing anything
Change one workflow at a time, keep the old one until the new one holds
Written procedures your staff helped edit
Staff augmentation
A cloud engineer, an SRE, or a developer working inside your team for three months or a year. They join your standups, use your tools, and follow your review process. You can interview them first.
Working your hours, in your time zone
Two week trial before the longer contract starts
Handover notes written weekly, not at the end
How we bill
Three ways to work with us
Project. Fixed scope, fixed price, paid in three parts.
Retainer. A set block of hours each month, rolled over once.
Embedded. One of our engineers inside your team, billed monthly.
Whatever the shape, you see the hours. No line item that says consulting.
Not sure which one you need?
Most calls start with a problem, not a service name. Describe the problem and we will tell you which of these fits, or that none of them do.