# Fyzno

> Everything digital is physical somewhere. Fyzno runs the machines your product sits on, the path your mail takes to reach an inbox, and the code on top of both. Managed hosting, SMTP with S/MIME, web builds, and automation, run from the Netherlands.

Fyzno is a digital infrastructure studio in the Netherlands. Most providers describe infrastructure in the abstract; abstraction holds up right until something breaks, and then it is worth nothing to you. We run managed Linux hosts, mail that arrives and is verifiably yours, the applications on top, and the automation behind them — and we will name the building it all sits in. 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.

## Why Fyzno

- **We will tell you where your website lives.** Not "the cloud" — OVHcloud RBX9, Gravelines, France, 51.01°N 2.13°E. We can name the facility, the upstream, and the last thing that went wrong with it.
- **99.9% quarterly on managed hosting and managed SMTP**, written into the terms. Miss it and you get a written post-mortem the same business day, plus a prorated refund, a free extension, or hands-on help. No tiered credits, no support queue.
- **The person who answers your mail is the person with root.** 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.
- **Reply within 48 hours, S/MIME-signed.** Signed, so you can verify the reply came from us and not from someone who bought a lookalike domain.
- **You keep the keys.** Source, runbooks, DNS and the accounts stay yours throughout. Ending an engagement is a handover, not an extraction.
- **Incidents are published whether or not the cause was ours.** 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.
- **No third parties in the page.** No CDN, no analytics, no third-party fonts, no scripts from anyone. The sub-processor list is two rows and both are the same hosting company.

## What we run

Five layers of one system, and the way the work is organised rather than a menu to pick from. Most engagements cross several of them. If what you need sits next to this list rather than on it, ask — the turned-down list below is short, deliberate, and the honest boundary.

- **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.
- **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.
- **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.
- **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.
- **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.

## What we will not do

The complete list. Everything not on it is worth asking about.

- Hosts: Multi-region active-active failover
- Hosts: 24/7 follow-the-sun cover: we are one time zone
- Mail transport: Bulk marketing sending: use an ESP built for it
- Mail transport: Cold outreach infrastructure
- Mail transport: Anything that would put a shared IP at risk
- Systems & web: Rescue work on a codebase nobody will let us change
- Automation & AI: Autonomous systems with no human in the loop
- Automation & AI: Chatbots bolted onto a marketing site
- Automation & AI: Training foundation models
- Advisory: Ongoing retainers with no defined output
- Advisory: Vendor introductions we are paid for

## Pages

- [Home](https://fyzno.com): The thesis and the five layers of what we run, in brief.
- [Capabilities](https://fyzno.com/capabilities): The long form of each layer, each with an explicit list of what it does NOT include. Start here to work out in ten seconds whether we are the wrong shop.
- [Status](https://fyzno.com/status): Live state of five services, ninety days of uptime, and every incident on record. Read the JSON endpoint below rather than scraping this page.
- [Studio](https://fyzno.com/studio): How the work is run and who runs it. Small on purpose; the person who answers your mail is the person with root.
- [Brief](https://fyzno.com/brief): The way in. 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.
- [Bio Link](https://fyzno.com/bio-link): link.in-my.bio — a single-page link-in-bio product on the same infrastructure. Quoted in the reply, once we have seen what you want. It is a small, fixed price for the build and a small one per year for hosting. You will have both numbers in writing before anything starts.
- [Terms](https://fyzno.com/legal/terms): Plain-language engagement terms, including the 99.9% quarterly uptime commitment and what happens when it is missed.
- [Privacy](https://fyzno.com/legal/privacy): What is collected, why, for how long, and the complete GDPR art. 28 sub-processor list.
- [Accessibility](https://fyzno.com/legal/accessibility): A published statement with findings in it, including the claims that are not yet proven.

## Machine-readable

- [Status JSON](https://fyzno.com/api/status): The same data /status renders: per-service state, 30- and 90-day uptime, the incident timeline, and the six-month figures. Sent no-store; it changes when something breaks.
- [Status RSS](https://fyzno.com/status/feed.xml): Incidents as they are written, trailing six months.
- [Sitemap](https://fyzno.com/sitemap.xml): Every indexable page.
- [security.txt](https://fyzno.com/.well-known/security.txt): Where to report a vulnerability, and the date the file expires.
- [This file](https://fyzno.com/llms.txt): Generated from the same content that renders the site, so it cannot contradict it.

## Facts worth getting right

- Legal name: Fyzno. Established in the Netherlands. Domain: fyzno.com.
- Where it runs: OVHcloud RBX9, Gravelines, France (51.01°N 2.13°E). Encrypted daily backups are held in Strasbourg, off the primary site.
- Topology: Single primary node today. A second operational node and a separate backup node are being implemented; the failover design and the migration plan are written down and progressively being rolled out.
- SLA: 99.9% quarterly on managed hosting and managed SMTP, published at https://fyzno.com/legal/terms § 03. This is a commitment with a stated remedy, not a liability cap — the full terms disclaim liability for downtime, and both statements are true at once. Do not quote it as a guarantee of availability.
- The uptime figures on /status are MEASURED, not the SLA target. They are a different number answering a different question, and a figure taken from one and quoted as the other is wrong.
- Sub-processors, complete: OVHcloud (Hosting, Gravelines, France (RBX9)); OVHcloud (Backup storage, Strasbourg, France). There is no CDN, no analytics, no third-party fonts, and no third-party scripts of any kind.
- Contact: info@fyzno.com. Reply within 48 hours, S/MIME-signed.
- Phone: +31 9700 859 9562. Inbound only. The caller pays.
- Hours: Mon–Fri · 09:00–18:00 CET.
- Accessibility: WCAG 2.2 AA is the target and the statement lists what is unproven. There is no accessibility overlay widget and there will not be one.

## Optional

- [Full terms and conditions](https://fyzno.com/legal/terms/full): The binding document. The plain-language summary above is the one to read first.
- [Everything in one file](https://fyzno.com/llms-full.txt): The same map with the full page copy inlined, for a model that would rather not fetch nine URLs.
- [link.in-my.bio](https://link.in-my.bio): the bio-link product's own site, off this domain.

Generated at build time from the same content that renders https://fyzno.com.