Skip to main content
Infrastructure

Hosting, DevOpsand someone awake.

We run what we build, and we'll run what others built. Environments, pipelines, monitoring, backups and the security posture underneath, sized to the product rather than to a cloud bill.

Who this is for

Products that need to stay up without hiring an ops team.

Products we built

Every build ships onto infrastructure we operate, under a Run tier. This is what that tier is made of.

Products someone else built

You have an app and nobody who wants to be on call for it. We audit, take it over and make it boring.

Teams outgrowing a platform

Bills or limits on a PaaS are hurting. We move you to infrastructure you control without a rewrite.

What we run

Everything between your code and your users.

01

Managed hosting

Railway or Coolify for most products, dedicated Kubernetes on Hetzner when you need it. Cloudflare in front, R2 for storage.

02

CI/CD and environments

Preview, staging and production from one pipeline. Every merge deployable, every deploy reversible.

03

Monitoring and alerting

Uptime, errors, performance and cost, watched by people who know the system and can act on what they see.

04

Backups and recovery

Tested restores, not just scheduled backups. Recovery objectives agreed and rehearsed.

05

Security hardening

Access control, secrets management, patching, network posture and the audit trail to prove it.

06

Scaling and cost

Capacity that follows usage, and a monthly look at what you're paying for and whether you should be.

How we work

Sized to the project. Not to the cloud provider's ambitions.

We don't default to AWS and its bills. We default to the smallest thing that runs your product reliably, with a clear path to the next size.

Principle

Boring by design

Well-understood tools, standard configurations, nothing clever that only one person understands.

Principle

Everything as code

Infrastructure, pipelines and configuration in the repository you own, reviewed like any other change.

Principle

Your accounts, your keys

We operate inside accounts registered to you. Leaving us never means migrating away from us.

Principle

Rehearsed failure

Restores, failovers and incident response practised before they're needed.

FAQ

Questions about hosting and operations.

Straight answers to what comes up on every first call. If yours isn't here, ask us.

Yes. We prefer to: the accounts should be yours regardless. If your current setup is expensive or fragile we'll say so and propose a migration, but the choice is yours.

Got an idea?Tell us about it.

Send a short brief. We'll come back with questions, a call slot and a straight answer on whether we're the right team.

Start a project