Mandara Systems

White-label & capabilities

Your brand, my engineering.

Infrastructure capacity for IT teams and agencies who occasionally need deeper systems engineering than their core team covers. Proxmox clusters, ZFS storage, firewalls and self-hosted office – delivered remotely, under NDA, behind your brand. Swiss sole proprietorship, single accountable contact, open technologies with no lock-in.

Discuss an engagement What I build

When this helps

Depth on demand, without hiring for it

  • A client needs a Proxmox or NAS build your team doesn't do every day.
  • You're at capacity and a migration window won't wait for the next hire.
  • You want a second opinion on a backup, DR or ZFS design before you commit.
  • You need the work invisible – your brand in front, an NDA in place.

Infrastructure stacks

What I build and look after

Proxmox clusters & HA

Virtualisation on Proxmox VE – multi-node clusters, high availability, live migration and a clean replacement for an ageing VMware estate.

TrueNAS / ZFS storage

Storage designed on ZFS – pool and vdev layout, checksums against data decay, snapshots, replication and capacity planning that lasts.

pfSense/OPNsense + UniFi

Networking and segmentation – open firewalls, VLANs, VPN and a UniFi fabric, with rules and topology documented for your team.

Nextcloud & self-hosted office

Self-hosted files, collaboration and office documents on Nextcloud – a SharePoint/OneDrive alternative your client owns outright.

Backup & disaster recovery

3-2-1 backup designs with off-site copies and tested restores – Proxmox Backup Server, replication and a DR plan that has actually been rehearsed.

Documentation & handover

Every build leaves a runbook – topology, credentials path, restore steps – so your team can operate, audit or take it over without me.

Engagement types

Three ways to work together

One-off migration or build

A defined project against a fixed scope – a VMware-to-Proxmox move, a NAS rebuild, a firewall replacement or a Microsoft 365 exit.

Overflow / subcontract

Extra capacity during peaks or staff gaps – I take a workstream off your team and deliver it under your brand.

Specialist consult

A focused review or second opinion – architecture, backup/DR strategy, ZFS layout or network design, where you want depth on one topic.

How it works

A white-label arrangement, kept simple

The premise is straightforward: your brand stays in front of the client, my engineering stays behind it. I work as a subcontractor under your company name, communication with the end client runs through you, and I don't approach your clients directly. You keep the relationship and the invoice; I provide the infrastructure work. Documentation, handover notes and runbooks can carry your branding, and the level of my visibility – from named specialist to entirely invisible – is agreed up front. For agencies and small IT shops that occasionally need deeper systems engineering than their core team covers, that means depth on demand without hiring for it.

NDA-friendly is the default, not an exception. I'm happy to sign your mutual or one-way non-disclosure agreement before any details of your client, environment or architecture are shared. As a Swiss sole proprietorship I'm a single, accountable point of contact – no offshore team rotating through your credentials. Access is granted least-privilege and time-boxed, credentials are handled through your password manager or vault where possible, and everything I touch is documented so your team can audit and revoke it afterwards. If you have a security or compliance checklist, I work to it.

The work is remote-first and built on open technologies on purpose. Proxmox, TrueNAS/ZFS, pfSense/OPNsense, UniFi and Nextcloud are open, well-documented platforms with no per-seat licence treadmill and no proprietary OS holding the data hostage – which matters twice over for a white-label build: your client owns a system they can run without me, and your own team can take over the documented build at any time. Swiss data residency is the default where the client wants it. I'm happy to work within a vendor stack you already standardise on, but the recommendation is infrastructure you and your client both stay in control of.

Process

From enquiry to delivery

Scoping call

We discuss the work and sign an NDA – no obligation.

Proposal

A clear scope, working rhythm and fixed key figures.

Delivery

Remote engineering to your change windows, behind your brand.

Handover

A documented runbook so your team can run and audit it.

Common questions

Good to know

What does white-label mean in practice?
It means your brand stays in front of the client and my engineering stays behind it. I work as a subcontractor under your company name: documentation, handover notes and runbooks can carry your branding, communication with the end client runs through you, and I do not approach your clients directly. You keep the relationship and the invoice; I provide the infrastructure work. This is a common arrangement for agencies and small IT shops that occasionally need deeper systems engineering than their core team covers, without hiring for it. Scope, naming and the level of my visibility are agreed up front and can be as invisible as you want.
Will you sign an NDA?
Yes. NDA-friendly is the default here, not an exception. I am happy to sign your mutual or one-way non-disclosure agreement before any details of your client, environment or architecture are shared. As a Swiss sole proprietorship I am also a single, accountable point of contact – there is no offshore team rotating through your credentials. Access is granted least-privilege and time-boxed, credentials are handled through your password manager or vault where possible, and anything I touch is documented so your team can audit and revoke it afterwards. If you have a specific security or compliance checklist, send it over and I will work to it.
Can you work remotely, on our schedule?
Yes – the work is remote-first. Most infrastructure engineering – Proxmox clusters, TrueNAS/ZFS storage, firewall and network configuration, Nextcloud, backup and disaster-recovery design – is done over a secure connection into your environment, so geography is rarely a constraint. I work to your maintenance windows and change-management process, including out-of-hours cut-overs where a migration or upgrade needs them. For tasks that genuinely require hands on hardware, that part can be coordinated with your local staff or scheduled as an on-site block. We agree availability, response expectations and the working rhythm before the engagement starts.
What kinds of engagement do you take?
Three shapes, mainly. A one-off migration or build: a defined project such as a VMware-to-Proxmox move, a NAS rebuild on TrueNAS/ZFS, a firewall replacement or a Microsoft 365 exit, delivered against a fixed scope. Overflow or subcontract capacity: I take a workstream off a busy team during peaks or staff gaps, working under your brand. And a specialist consult: a focused review or second opinion on an architecture, a backup and DR strategy, a ZFS layout or a network design, where you want depth on one topic rather than a full build. Engagements can also start as a consult and grow into delivery.
Why open technologies rather than a vendor stack?
Because they keep your client free of lock-in and keep the work auditable. Proxmox, TrueNAS/ZFS, pfSense/OPNsense, UniFi and Nextcloud are open, well-documented platforms with no per-seat licence treadmill and no proprietary OS holding the data hostage. For a white-label arrangement that matters twice over: your client owns a system they can run without me, and your own team can take over the documented build at any time. I am happy to work within a vendor stack you already standardise on, but the default recommendation is open infrastructure that you and your client both stay in control of.

Contact

Have a build you'd rather not staff for?

Tell me the shape of the work and your timeline. NDA first, then a clear scope – I'll get back to you within 24 hours.

Discuss an engagement See example builds