Managed hosting
Your site on infrastructure we run and watch ourselves: certificates, caching, mail routing and DNS handled, with a restore path we have actually tested.
Studio of two
Two people. Hosting and design, strong like a sapphire.
We build websites and then keep them running. Same two hands on the server, the design and the Tuesday-morning fix, so nothing gets lost in a handover.
—
Uptime
—
Sites shipped
—
Reply time
Slot 01 — Portrait 4:5
Slot 02 — Landscape 16:10
About
The scale of two
Christian and Bosse. No account layer, no ticket queue between you and the people doing the work.
Two people who read the long tail of every project as a shared obsession. The redirect nobody asked about, the font that loads a beat late, the backup that has never actually been restored — that part of the work is the part we like.
Being two is a constraint we chose. It caps how much we take on, and it means the person who designed a page is the person who knows why the server is configured the way it is. Decisions stay in one head, or at most two.
We work in the open: you get access to the hosting, the repository and the domain from day one. If you ever want to leave, everything you need is already in your name.
Christian Bosse
Slot 03 — Wide 16:9
Slot 04 — Square
Slot 05 — Square
Capabilities
Four things, done properly
Usually all four together. They can be taken on their own if you already have part of it covered.
Site building
Hand-built pages, or a CMS your team can hold without training. Fast by default, because the hosting and the build are decided in the same room.
Design
Type, structure and hierarchy first, decoration last. We design in the browser so what you approve is the thing that ships.
Care & maintenance
Updates, monitoring and small changes on a standing arrangement. You write to one address and one of us answers.
Labs
Notes from the bench
Working notes on the parts of hosting nobody sees. Drafts, not case studies.
Slot 06 — 3:2
What to cache, and for how long
Most pages can sit at the edge far longer than people assume. The hard part is deciding what has to stay fresh.
Slot 07 — 3:2
A backup is a restore you have not done
Notes on rehearsing a full restore on a schedule, so the first attempt is never on a bad day.
Slot 08 — 3:2
Moving a domain without a quiet hour
Lowering time-to-live in advance, keeping the old host warm, and what we check before cutting over.
Slot 09 — 3:2
Alerts worth waking up for
Fewer checks, better ones. An alert that fires often enough to be ignored has stopped being an alert.
Slot 10 — 3:2
Editing screens people actually use
Fewer fields, clearer names, and a preview that matches the page. Most content debt starts in the editor.
Method
Listen, design, build, run
Four stages, in order. The last one has no end date, which is the point of hiring a studio that also hosts it.
-
Slot 11 — 4:3
Listen
One long conversation about what the site has to do, who maintains it, and what already works.
-
Slot 12 — 4:3
Design
Structure and type first, in the browser, on real content. You review pages, not pictures.
-
Slot 13 — 4:3
Build
Built on the hosting it will live on, so staging and production differ only by the domain.
-
Slot 14 — 4:3
Run
Monitoring, updates and small changes, month after month. The same two people who built it.
Selected work
Two issues, for now
Case write-ups are in preparation. Placeholders below stand in for the real pair.
Slot 15 — 16:10
A small site, rebuilt and rehosted
Draft summary. Design, build and migration handled end to end, then kept on a care arrangement.
Slot 16 — 16:10
An editor the team stopped dreading
Draft summary. Content model simplified and the publishing flow cut down to the steps people actually need.
What people say
In their words
— , —We write to one address and the person who answers already knows the site.
Partners
Managed hosting
Site building
Design
Care & maintenance
Get in touch
Tell us what you have, and what it should become
One email reaches both of us. A short description of the site and the deadline is enough to start.
contact@saphir.media