Mira

Mira Network is a Swiss-based blockchain ecosystem focused on Real-World Asset (RWA) tokenization and digital investment infrastructure. The platform is developing capabilities that enable organizations to launch compliant tokenized assets on-chain, supporting fractional ownership, transparent transaction tracking, and scalable global participation.

Beyond tokenization, Mira Network integrates a mining-based engagement layer within its application, allowing millions of users to participate in ecosystem activity and interact with on-chain infrastructure as the platform continues to expand.

The organization was founded in 2023 in Switzerland by Joshua Elder and Dominique Letsch, but the business is globally distributed. 

The Mira Network platform has grown fast, and in 2025, it handled millions of users and processed approximately 19 million queries each week. However, the infrastructure stack had grown organically, and as such, had turned into a ‘black box’ of manual configurations. 
Every change to the system had begun to become a risk, and troubleshooting could be very difficult. The business was also incurring increasingly expensive bills with its hyperscale provider, largely due to oversized, unoptimized instances. 

At the same time, the team had very little visibility into system health due to a lack of centralized logging and metrics. The deployment cycles relied on manual intervention rather than automated CI/CD, and database architecture was spread across three zones, creating unnecessary complexity and latency.

“We had a significant infrastructure challenge. Our stack was an expensive, manually configured setup that lacked visibility and couldn’t deliver the required reliability. We were keenly aware that our infrastructure wasn’t just a cost centre or bill we received each month – it was the foundation of whether users trusted us or not. We needed to migrate and simplify, and we needed an agile, reliable partner to do this with us. We set ourselves the incredibly ambitious timeframe of fixing the stack within just two months.” 

Dominique Letsch, Co-Founder and CEO of Mira.

Mira Network had recently applied for and been accepted into the OVHcloud Web3 accelerator program and met DevOps consultancy Dysnix through the scheme. Dysnix engineered, planned, and conducted a transition to OVHcloud, leveraging high-performance cloud and managed Kubernetes services. The strategy focused on "right-sizing," "automation-first," and visibility principles.

The Dysnix team designed a migration and implementation roadmap that aimed to tackle the transition within 17-25 days, leaving ample time for troubleshooting. The Dysnix team re-architected the infrastructure from the ground up, making sure that there was monitoring, alerting, and logging software present from the very first day, as well as scalability by design, planned for the future implementation. 

The previous hyperscale solution handled provisioning via manual systems, which the Dysnix team switched over to Terraform and Terragrunt, running infrastructure as code. Orchestration changed from either being unmanaged or manual Kubernetes to OVHcloud’s managed Kubernetes service, and the oversized RDS database moved to an optimized, managed PostgreSQL database. The new solution used predictive / horizontal pod autoscaling to ensure scalability, and VictoriaMetrics, Grafana, and Loki monitoring; none of these systems were in place previously.  

The core backend and data layers were moved into a streamlined, two-zone high-availability setup in the OVHcloud Germany (Limburg) region, and instances were chosen based on carefully profiled traffic needs. The Dysnix team also put load balancers in place to ensure traffic optimization.

“We took several steps to make sure the system worked well,” said Daniel Yavorovych, CTO at Dysnix. “At the backend, we configured health checks to detect and restart unhealthy pods automatically, as well as rolling updates to ensure that traffic always kept moving during deployments – which also allowed us to trigger automatic rollbacks if error rates spiked after a new deployment. There was a lot of work that went into designing every aspect of the system, because we knew that Mira Network was growing fast – and that meant keeping things moving.”

The frontend assets were migrated from the hyperscale provider to OVHcloud's object storage and CDN, working closely with OVHcloud’s customer success team, ultimately reducing latency for end users globally. CI/CD pipelines were configured for the front end, ensuring new versions could be seamlessly deployed to S3. The previous setup relied on manual deployments and ad-hoc scripts. Dysnix deployed a GitHub-based CI/CD pipeline using industry-standard tools that automated every step from code commit to production release. This unified deployment model eliminated the operational friction of managing separate frontend and backend release cycles.

The Dysnix team also put in place a multi-layered monitoring stack to make the system self-aware and self-healing. This included using Prometheus to scrape metrics from every Kubernetes node, pod, and application endpoint every 15 seconds. This captures CPU, memory, disk I/O, network throughput, and custom application metrics, such as query latency and blockchain transaction confirmation times.

The Grafana stack (Loki, Alloy, Grafana) dashboards provided real-time visualization of system health, and a set of automated alert rules was also put in place.

It was critical that none of Mira’s four million users experienced disruption, so Dysnix built and replicated the entire stack alongside the legacy infrastructure, syncing data until the very last moment of transition.

“The switchover was completed in just under ten minutes, but we didn’t think of it as a single moment in time,” continued Daniel Yavorovych. “We maintained the hyperscale environment as a standby for a week to make sure that if we needed to rollback, we could. We never needed it, but it was a key part of the migration to have the option available.” 

Mira Network is now hosted in OVHcloud’s managed Kubernetes environment and has 99.99% uptime. There are no longer failures due to manual setup or complexity sprawl, and there has been a considerable reduction in infrastructure costs. 

“The new system moved us from manual to automated deployment, reducing deployment time from hours to minutes and eliminating human error as a source of outages,” continued Joshua Elder, Co-Founder and COO of Mira. “Furthermore, the team now sees query patterns, database connection pools, and pod restart rates at a glance. We have custom dashboards tracking KPIs which are specific and bespoke to our company,  including user login rates, mining session activity, reward distribution metrics, and tokenization transaction volumes. We also have alert rules which trigger automated responses, sending messages to engineers when necessary.” 

The new infrastructure stack allows Mira Network to ship updates in minutes rather than hours and has significantly enhanced observability over the system.

“We’ve moved from firefighting to optimizing,” concluded Joshua Elder. “Furthermore, this is only the very first step; we’re looking at advanced autoscaling to make sure that we can handle ten times more users in the future. Not only has this migration given us better operational and commercial transparency, but we also feel secure that we’ll be able to scale from millions to tens of millions of users without the fear of infrastructure collapse or runaway costs.”