Skip to content
NetworkBound

NetworkBound sites

NetworkBound here Infrastructure and NOC engineering. The services side. Game hosting Your own game server. Free tier: sleeps only when the host is busy. PC audit A $5 Windows gaming audit that tells you what is actually wrong. Cortex Self-hosted AI dev cockpit. Every model, one window. Signals SEC Form 4 insider-purchase screening, open and dated.
Contact

Infrastructure & NOC engineering

14 practice areas

Infrastructure that tells you the truth.

We design, build and hand over the parts of an estate that have to be right when something goes wrong: monitoring that covers what actually breaks, a ticket path that opens one incident per outage, failover that has been performed, and a restore that has been timed.

Every figure on this site is a measurement, and each one links to the work that produced it. Where something is unproven, it says so.

Start a conversation Everything we can do Join the Discord
Monitoring NOC & ITSM High availability Virtualisation Backup & DR Networking Hosting & edge Security assessment Identity & access Mail Self-hosted AI Agent tooling Automation & IaC Consulting & labs

01 Start here

Which of these sounds like you?

In your words, not infrastructure vocabulary. Each one opens with what would actually be done about it, and together they suggest the shape the work would take.

Select any that apply — more than one is normal.

What that means in practice

Monitoring that covers the things that actually break, with alerts scoped so the ones that fire are worth reading.

Monitoring & observabilityHigh availability & resilience · usually assessment, 3–5 days

What that means in practice

Alarms grouped by cause in the monitor, and one incident opened that already lists every affected circuit. Re-running returns the same ticket instead of a second one.

NOC & ITSM integrationMonitoring & observability · usually build, 2–6 weeks

What that means in practice

A restore attempted for real, against real media, before the answer matters. Then a regime whose green state has been tested.

Backup & disaster recoveryVirtualisation & compute · usually assessment, 3–5 days

What that means in practice

First, proof that alerts can reach a person at all — one audit found 13 of 10,388 had. Then the false ones removed, and thresholds set against measured behaviour rather than defaults.

Monitoring & observability · usually remediation, 1–4 weeks

What that means in practice

Exposure checked from outside, every key and token audited for age and use, and a numbered findings list — then the fixes, and a harness that proves they held.

Security assessment & secret hygieneIdentity & access · usually assessment, 3–5 days

What that means in practice

A single reasoned access path — default-deny, MFA enforced, no inbound ports — that can be described in one diagram.

Identity & accessNetworking · usually remediation, 1–4 weeks

What that means in practice

Hosting with TLS automation, zero-inbound publishing and a deploy path that is repeatable rather than remembered.

Web hosting & edge deliveryNetworking · usually build, 2–6 weeks

What that means in practice

Self-hosted models on your own GPUs, with the agent tooling around them, so the data never leaves your estate.

Self-hosted AI & small language modelsAI agent workflows & tooling · usually build, 2–6 weeks

What that means in practice

Design agreed up front, built in version control, handed over with the runbooks needed to operate it without us.

Virtualisation & computeAutomation, IaC & NOC operations · usually build, 2–6 weeks

What that means in practice

Scheduled verification of the things that must not quietly break, change history kept, and a named contact when something does.

Automation, IaC & NOC operationsConsulting & lab build-outs · usually ongoing, Monthly retainer

02 What we can do

The detail, one press away

Fourteen practice areas in five groups, the write-ups that show the work being done, and the two offers people ask about most. Each has its own page.

03 Engagement

Four ways this gets bought

Most work starts as an assessment, because it is the cheapest way to find out whether the expensive thing is necessary.

01 3–5 days

Assessment

A read of what you are running and what is currently untrue about it. Ends in a written findings list ordered by what it costs to fix versus what it costs to leave.

  • Inventory of hosts, services and dependencies as they actually are
  • Every alert rule reviewed for whether it can fire, whether it should, and whether anyone would receive it
  • One restore attempted end to end from real backup media

A written findings list, ranked by risk and effort, that you keep.

Fits when You inherited an estate, or you suspect the dashboards are lying.

02 2–6 weeks

Build

Design and delivery of a defined system — a monitoring estate, an alarm-to-ticket integration, an access layer, a backup regime, a hosting platform — including the documentation and the handover.

  • Design agreed in writing before anything is provisioned
  • Built in version control and rehearsed on a replica, with the configuration reproducible
  • Handover session, plus runbooks for the parts that will need touching

A working system you can operate without us.

Fits when You know what you need and want it built once, properly.

03 1–4 weeks

Remediation

Targeted work on a system that exists but is not trusted: alert noise, silent gaps, failed restores, an integration that opens duplicate or thin tickets, an access layer nobody can reason about.

  • Noise removed first, so the remaining signal can be judged
  • Each fix verified against the failure it is supposed to catch
  • Changes recorded, so the estate stops being its own only record

A system whose green state means something again.

Fits when It technically works and nobody believes it.

04 Monthly retainer

Ongoing

Continuous operation and improvement, with change history, scheduled verification of the things that must not quietly break, and someone to call.

  • Scheduled verification of backups, alerting and access paths
  • Change history maintained, with a monthly written summary
  • A named contact for incidents, with agreed response expectations

The estate stays true after the project ends.

Fits when You need the estate to keep being true after the project ends.

  1. 01

    Describe what you are running

    What the estate is, and what is currently going wrong with it. No inventory spreadsheet required — a paragraph is enough to tell whether there is useful work here.

  2. 02

    A short call to scope it

    We agree which shape fits, what would be in scope, and what the finished thing has to be able to demonstrate. If the answer is that you do not need anyone, you get told that instead of a proposal.

  3. 03

    Written scope, then work

    Scope written as verifiable outcomes rather than a component list, because a component list can be delivered without the system working. Access is scoped to the task and revoked at handover.

Game hosting

Host a game server, free.

83 games, every one of them on a free tier. Pick a game, pick a hostname, and the platform provisions the server and its DNS for you.

  1. 01

    Pick a game

    Minecraft, Valheim, Terraria, Satisfactory, Mumble and more — search or filter the catalog.

  2. 02

    Pick a name

    Choose your own hostname. DNS is created automatically and is yours to share.

  3. 03

    Play

    The server provisions itself and gives you an address. Free servers sleep when idle and wake on connect.

Browse the games Create an account

Free tier · No card required · Your own hostname · networkbound.org

In the catalog

  • Minecraft: Java Edition
  • Minecraft: Bedrock Edition
  • Luanti (Minetest)
  • Terraria (TShock)
  • Factorio
  • Satisfactory
  • Vintage Story
  • Eco
  • +75 more

Servers run on NetworkBound's own hardware. Idle free servers suspend and wake on the next connection.

PC audit

Find out what is actually wrong with your gaming PC.

A read-only Windows gaming audit. It tells you what is actually misconfigured, what it is worth to you, and what will do nothing for you.

  • It will tell you no

    Most of what circulates as optimisation does nothing. The report says so, by name, with the reasoning — including for settings it found switched on.

  • It asks before it changes anything

    The audit is read-only and touches nothing. A separate tool applies only what you tick, records how to undo each change before making it, and puts it all back on one command.

  • Honest unknowns

    A check that could not run says it could not run, rather than being rendered as a pass or quietly dropped.

See the audit — $5 once

$5 once · Lifetime key · Undo on one command · networkbound.org

Contact

Start a conversation.

Describe what you are running and what is currently going wrong with it. A short exchange is usually enough to say whether there is useful work here, and roughly what it would take.

Send a message See the evidence