Overview The Journey What We Built A Day With Monty Tech Enablement The Dashboard Monty Home
🎩 Infrastructure  ·  Principles

Tech Enablement

Capable because it's secure, not despite it.

A powerful assistant with access to your life is only a good idea if it's locked down properly. These are the principles that let Monty do so much, safely.

We didn't bolt security on at the end. The whole thing is built on a few non-negotiable ideas, own everything, trust nothing by default, and give every part only what it needs.

Self-hosted

Every moving part runs on hardware we own and control. No rented platform sits between Monty and our data.

Zero trust

Nothing is trusted simply because of where it sits on the network. Every connection is verified, every time.

Least privilege

Each service, device, and credential gets the minimum access it needs to do its job, and not a scrap more.

Assume breach

Designed so that if one piece is ever compromised, the blast radius is small and contained by default.

Secrets, centralised

Credentials live in a dedicated, self-hosted vault, never hardcoded, never sitting in plain text.

Nothing exposed

No open doors to the public internet. Access happens through an encrypted private mesh, outbound-only at the edge.

Two layers, belt and braces.

Public-facing traffic is handled at the edge by a zero-trust gateway, no ports opened on our own connection, identity checks in front of anything private.

Internally, our own devices talk to each other over a self-hosted encrypted mesh. Two independent layers have to be satisfied before anything is reachable.

Edge zero-trust gateway Self-hosted mesh VPN Reverse proxy + auto-HTTPS Identity-gated access Secrets vault Containerised services

Edge layer

A zero-trust tunnel terminates public traffic with no inbound ports, fronting only what's meant to be public.

Mesh layer

Devices join a private encrypted network so internal services are reachable to us, and invisible to everyone else.

Service layer

Each service runs isolated and scoped, pulling its secrets from the vault and nothing else.

01
Audit & harden Ongoing

The whole estate was put through a full security review and hardened, and it's revisited as things change.

02
Monitor Always-on

Service health and uptime are watched continuously, with alerts the moment something needs a look.

03
Back up Automated

Memory and configuration are version-controlled and backed up, so Monty's continuity survives any single failure.

04
Update Routine

Components are kept current as a matter of routine, staying patched is part of staying secure.