Our storage is a pile of drives and hope
We match the storage to the job: one approach for the data you cannot lose, another for a big archive of mixed drives with scheduled parity. We tell you what each one protects and what it does not.
Infrastructure & self-hosted platforms
Servers that keep running.
Storage, containers, backup and recovery for systems you own, with restores we have tested. We build and run this kind of platform for ourselves, and we bring the same discipline to yours.
Start a projectProblems we solve
We have backups. Nobody has tried a restore
A backup is only real once it comes back. We build backups that encrypt the data, reuse what has not changed, and are verified by restoring files and comparing them with the originals.
If one box dies, everything stops
We design for the failure and then test it. We pull the power on a real three-node cluster and write down what happened. In our last drill, failover did not complete, and we recorded that instead of calling the system highly available.
Every new server is a new routine
One dashboard can run many Docker hosts on Linux, macOS and Windows. Hosts enrol once with a token, and everything after that is authenticated and encrypted.
The server is stuck and nobody can see why
Out-of-band control shows the real console, sets the BIOS, mounts install media and restarts the machine, with nobody at the keyboard.
The app is running, but nobody can reach it
We tie the address to the container. Declare a hostname once and the DNS record follows. Then we check the real address, because a record alone proves nothing.
What we build
Storage platforms
Pools, shares, snapshots and permissions that fail closed, with a setup wizard so a new box is ready for real work.
Backup and recovery
Deduplicated, encrypted backups with retention, integrity checks and restores tested on the systems your people use.
Container and virtual machine hosts
Apps, containers and virtual machines managed from one interface, with catalogues of ready-to-run apps.
Multi-host management
One place to operate many hosts, with a clear next step when a host drops out or needs to enrol again.
Hardware control
Headless install, console capture, power, boot and BIOS control for Dell servers.
Network publishing
DNS, tunnels and proxies wired to your containers, checked from the outside.
Installers and updates
Install media, first-run setup and self-updates that verify the new version, check its health and can roll back.
Who it’s for
Creators and small studios
Years of footage and project files get a home with a real backup behind it.
Home-server owners
A growing pile of containers turns into one system you can understand and repair.
Small businesses
Shared storage without handing every user the keys to the whole machine.
Teams with servers in several places
One dashboard for all of them, and a documented way back when one fails.
Operators of Dell hardware
Installs and recovery that no longer need someone standing at the machine.
How we work
Understand
We list what you run, what you cannot afford to lose and how you would notice a failure. That sets the design.
Design
We choose the storage, backup and recovery approach for each kind of data and say plainly what it does and does not protect.
Build
We build and test on real hardware, including failure drills. Work is ticketed and checked before it ships, and every release is recorded automatically.
Run
We can keep running it with you. Updates verify themselves, backups get checked, and incidents are written up so the same one does not come back.
Proof
Eight.ly OS
Storage, containers and virtual machines in one operating system, with a choice of storage approaches and a recorded failover drill.
Eight.ly Backup Server
Encrypted, deduplicated backups with restores verified byte for byte on Linux, macOS and Windows.
Eight.ly Agent
Docker management across many hosts, with one-time enrolment and authenticated connections.
iDRAC Commander
Headless control of Dell servers, built after a firmware prompt stalled an install.
HomelabARR
An open-source dashboard that makes self-hosted apps one click each, with a catalogue that is its own.
Questions
How long does a project take?
It depends on what has to be proven. We usually start with one working piece, such as a storage design or a tested restore, so you see results early and decide the next step from evidence.
Can you work with the servers we already have?
Often, yes. We design around the drives and servers you own where we can, and tell you where they fall short.
Who owns the code and the configuration?
You do, outright. Whatever you pay us to build is yours, with full rights: the complete source code, the configuration and the documentation. Several of our own platforms are open source, so open source is a normal option too.
What happens after launch?
We build it and we run it. We can stay on to maintain the platform, check the backups and handle what breaks, or hand it over with the runbooks you need.