First Update in 2026

First Update in 2026

Happy New Year! 2026 is here, and we're excited to share with you our first upcoming major update. This update will bring you a new management dashboard, Identity DNS, and more.

New Management Dashboard

The new management dashboard will be released soon. You'll be able to manage your VeilNet Conflux instances, Registration Tokens, and Private Realms in a more intuitive and user-friendly way.

The new management dashboard will shift from Flutter to Nuxt 4. This means it will no longer be a Progressive Web App (PWA), but a full-stack web application.

Don't worry—although a full-stack web application can't run offline from your browser like the current management dashboard does, we will open-source the code and provide a Docker image for you to run it on your own server. Here is a preview of the new management dashboard:

Identity DNS

The world's first decentralized secure DNS system that eliminates the need for a central DNS registry. This means you'll soon be able to integrate VeilNet Conflux instances as service endpoints with DNS names, without spending anything on a domain name from a registrar.

Your private realms will be almost identical to a private internet.

Most importantly, this will be the most secure DNS system in the world. All DNS queries are encrypted and authenticated by Kyber KEM and Dilithium DSA, just like any other control realm traffic in VeilNet. The DNS services will be managed by VeilNet Conflux instances themselves, not by an external service provider, ensuring zero downtime and zero maintenance.

There will be no additional cost or configuration required. The DNS name will be simply determined by the tag of your VeilNet Conflux instance. For example, if your VeilNet Conflux instance is tagged as "my-service", you can access it via "my-service.veilnet".

Multiple VeilNet Conflux instances can share the same DNS name, and you'll automatically get load balancing and failover across all instances. Pretty cool, right?

Removal of Supabase Realtime Subscription

Currently, VeilNet Guardian, the authentication microservice, relies on Supabase Realtime to sync state across all instances to achieve a stateful API service. However, we've discovered that the realtime subscription is fairly unreliable and often leads to silent disconnects.

We've implemented a self-recovery middleware to handle disconnects and reconnects, but it does put the microservice into a 503 (service unavailable) state.

In our next update, we will remove the Supabase Realtime subscription and use a more reliable and scalable solution to sync state across all instances: Veil Master, the global NATS super cluster. This means VeilNet Guardians will have their own control realm as well and will use gRPC based on events!

Although you won't see any difference in the API, the underlying infrastructure is completely different and more reliable.