Origin
Built for a world we wanted to operate.
Mirage started as infrastructure for Industrium, the Minecraft network behind Project Caligo. We wanted players to move through a distributed network while staying inside the same uninterrupted experience.
The system became real inside our own technology stack. A public demonstration then reached more than 30,000 views and attracted network builders who recognized both the opportunity and the work required to maintain it. Their response made the next step clear. The technology could serve more than one network if the team, deployment, and ongoing operation travelled with it.
Two roles
The technology and the program around it.
The names describe two connected parts of the same work. Keeping them distinct makes the offer easier to understand.
Mirage connects backend servers behind one continuous player experience.
Project Caligo covers assessment, integration, operation, updates, support, and a commercial agreement shaped around the network.
The name
Mirage hides the boundary. Caligo represents the illusion.
Caligo is a genus of owl butterflies known for the large eye-like patterns on their wings. Those patterns change how the butterfly is perceived. The infrastructure behind Mirage is still made of separate servers, while the player perceives one continuous world.
The butterfly gives the idea a visual form. Its two separated wings can represent distinct servers. Seen together, their symmetry becomes one complete shape.
The Latin word caligo can mean mist, obscurity, darkness, or dimness of sight. It suggests something real concealed behind a veil. That meaning complements Mirage, which keeps server boundaries and infrastructure complexity outside the player's experience.
Separate infrastructure. One continuous world.
Present
What Mirage offers today.
Mirage is already used within Industrium and is offered as a managed proprietary service. Its present value is focused on continuity inside a multi-server Minecraft network.
Seamless backend transfers
Players move between backend servers with control intact and no visible loading screen or transfer artifact. The familiar initial Minecraft connection remains unchanged. Continuity begins once the player is inside the network.
Cross-server visibility
Server meshing synchronizes relevant players and entities across backend boundaries so the world can remain visually connected.
Managed integration
The team assesses the network, plans the deployment, integrates Mirage, and provides the infrastructure and operational work agreed with the customer.
Ongoing operation
Updates, maintenance, hosting options, documentation, infrastructure tooling, and direct support can remain with the people who build and operate Mirage.
Direction
One roadmap, without artificial dates.
We treat near-term improvements and long-term ambition as one continuous direction. There is no public ETA and no split between a short roadmap and a distant promise. Each step should move Mirage closer to a shared world across distributed Minecraft servers.
Seamless backend transfers and cross-server visibility establish the player experience.
Deeper meshingOngoing work expands how servers exchange the information needed to keep worlds and activity connected.
Shared-world ambitionThe long view is to make distributed servers behave increasingly like parts of one world and support Minecraft experiences that were previously impractical.
Progress is guided by real operation inside Industrium, the needs of suitable partner networks, and the reliability expected from managed infrastructure. We will communicate meaningful progress when it is ready to demonstrate.
Fit
Designed for networks that are ready to connect worlds.
The starting network shape is one proxy and at least two backend servers. Proxy count, backend count, resources, deployment, hosting, support, and licence term are then discussed directly with the team. Monthly and yearly agreements are available so the service can follow the network's operating model.
Mirage infrastructure is currently hosted in France, which makes European networks the closest operational fit. Networks in other regions are welcome to start a conversation so latency, architecture, and deployment fit can be assessed together.
People
A small team with complementary experience.
BENZOOgataga brings systems engineering, infrastructure architecture, hosting, systems administration, and network operations. Lodjo brings experienced software development and long-term product engineering.
Together, the team can review a network from infrastructure through software, then remain responsible for the managed service around it. Revenue from Project Caligo supports continued development of Industrium, Mirage, the team, and the hosting used to operate the service.
Continue
Bring us the world you want to build.
If your network has one proxy and at least two backend servers, tell us what should feel continuous. We will review the fit and come back to suitable projects for a direct discussion.