Fyzno

digital infrastructure · Established in the Netherlands

Everything digitalis physicalsomewhere.

We run the machines your product sits on, the path your mail takes to an inbox, and the code on top of both.

Open a briefSee what's running
Facility
OVHcloud RBX9
Location
Gravelines, France
Position
51.01°N 2.13°E
  • Acquiring signal

Status endpoint

Plate 01 · Request traversal

A request crosses a fixed number of machines before anyone sees a page. We know which ones, and what each is doing when it slows down.

Where it runs

Your website lives in a building in Gravelines, France.

We can name the facility, the upstream, and the last thing that went wrong with it. On 22 February 2026 that was OVH rerouting our gateway during scheduled backbone maintenance; the host was unreachable for four minutes.

Most providers describe infrastructure in the abstract. Abstraction holds up right until something breaks, and then it is worth nothing to you.

What we operate

One system, five layers deep.

Read the detail

  1. Advisory

    read · plan · cut

    We read the stack, the invoices, and the contracts, then say plainly what to keep, what to move, and what to stop paying for.

    • Stack and spend audit
    • Sequencing
    • Migration plan
    • Hand-off

  2. Automation & AI

    models · agents · pipelines

    Models wired into the parts of a stack where they earn their cost. Document pipelines, triage, internal tooling. Every action logged and reversible by a person.

    • Retrieval over your own data
    • Tool-calling agents with guardrails
    • Local or on-premises models where the data warrants it
    • Audit trail on every write

  3. Systems & web

    next.js · apis · integrations

    The application on top of the infrastructure. Built in vertical slices, shipped weekly, handed over with the source and the runbook that operates it.

    • Design through launch
    • APIs and third-party integration
    • Performance and accessibility budgets
    • Source and runbooks are yours

  4. Mail transport

    postfix · dkim · s/mime

    Mail that arrives and is verifiably yours. We issue S/MIME keys on your domain, install them, and rotate them on a schedule, with SPF, DKIM and DMARC aligned underneath.

    • S/MIME issued, installed, rotated
    • SPF · DKIM · DMARC aligned
    • Bounce and reputation monitoring
    • Dedicated sending domains on request

  5. Hosts

    linux · tls · backups

    Linux machines we provision, patch, and answer for. Certificates that renew, backups that restore, and a person on the other end of the pager.

    • Provisioning and weekly patching
    • TLS and DNS under management
    • Encrypted daily backups, held off-site
    • One person on call, by name
  1. Composeyour client
  2. Submission587 · STARTTLS
  3. DKIM signatureselector fyzno-rsa
  4. Policy checkSPF · DMARC
  5. RelayMX lookup
  6. Inboxor not, which is the point

Plate 02 · The path a message takes

Six hops and two signatures between writing a message and someone reading it. When mail lands in spam it failed at one of them, and we can tell you which.

On the record

Four minutes, published.

22 Feb

2026

4MIN

Unreachable

0

Messages lost

22 February 2026. OVH rerouted the Gravelines gateway during scheduled backbone maintenance and the host was unreachable for four minutes. We called every affected customer inside a day and confirmed nothing was lost. The cause was upstream. The write-up is public anyway.

Read the status page

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

Reply within 48 hours, S/MIME-signed.

Or write directly: info@fyzno.com