Fyzno

Studio

Small on purpose.

The person who answers your mail is the person with root. That is the whole pitch, and it is the reason the rest of this site can be specific.

How we work

One primary, documented

There is no multi-region failover cluster here. There is one well-understood machine at OVHcloud in Gravelines, a written failover design, and encrypted daily backups held in Strasbourg. Knowing exactly where your single point of failure is beats not knowing where six of them are.

Written before built

Hosts, mail routing, certificates, models, and backups are laid out in writing before anything is provisioned. If the plan cannot survive a read-through, it will not survive production.

You keep the keys

Source, runbooks, DNS, and the accounts stay yours throughout. Ending an engagement is a handover, not an extraction.

We say no in writing

If something is outside what we can operate well, we will say so and point you somewhere better. A referral costs less than a bad quarter.

An engagement, start to finish

  1. 01

    Brief

    You write what you are running and what you want. We read it and reply within 48 hours, signed.

  2. 02

    Read

    Two or three sessions and access to whatever exists already. We look before we propose.

  3. 03

    Written scope

    A document with the architecture, the sequence, the price, and what is explicitly out of scope. A signed scope fixes its price.

  4. 04

    Build

    Vertical slices, shipped weekly. Each one is a working piece rather than a layer of a diagram. You watch the same deploys we do, and anything that slips is in writing before you have to ask.

  5. 05

    Hand over

    Source, runbooks, credentials, and a walkthrough. Maintenance afterwards is optional and priced per term.

Send a brief. A partner reads it.

Tell us what you are running now and what you want it to do. No form letters back. The person who replies is the person who would do the work.

Open a brief

Mon–Fri · 09:00–18:00 CET · Reply within 48 hours, S/MIME-signed.