Fintech
Fewer things to defend. Fewer things to audit.
Connect branches, cloud accounts and core banking systems in minutes. Nothing answers the public internet, nothing passes through VeilNet, and your risk register carries one fewer vendor.
- Time to connect a site
- Minutes
- Answers a scan
- Nothing
- Vendor in the payment path
- None
- Failover
- Automatic
Networks that stop being projects.
Join a branch, a cloud account or a single database in minutes, with no appliance to install. Publish a database, a queue or a trading system as easily as a web app, including the systems you never dared connect.
No hardware
VeilNet is software on the servers and laptops you already run, on Linux, Windows, macOS and the BSDs. No appliance to size, patch or replace.
Quick deployment
Commission a system in your guardian and one command enrols it. It finds the network in under a minute, with no port to forward and no change window.
One dashboard, full visibility
Your own console shows every system's connections, peers and routes, refreshed every 30 seconds and kept for 90 days. Payloads are never reported.
Eliminate cloud complexity
Put clusters in AWS, Google Cloud and Azure on one network, or run PostgreSQL across regions with no database proxy or VPN gateway in between.
Stays up when a link doesn't.
Branches, ATM networks and trading floors can't go offline. VeilNet measures every route, steps around a failed one on its own, and drops a dead server within two seconds, so there's no failover runbook to rehearse.
Instant failover
Run two servers on one address. If one stops, clients drop it at once. If it's cut off, they drop it after two seconds of failed traffic, and new connections go to the other.
Multi-pathing
Every route is costed by measured round-trip time, and traffic takes the cheapest. Where several servers share an address, flows spread across all of them.
Bridge every banking network
A subnet router puts a whole branch LAN on the network. The systems behind it keep their real IPv4 addresses and need no new software.
Unique device IDs
A system's ID is a hash of its own post-quantum public key, and its IPv6 address comes from that ID. It never rotates, so moving a workload changes nothing.
Europe's coordinated roadmap: start by the end of 2026, move high-risk systems to post-quantum cryptography by 2030, and finish by 2035.
Source: EU coordinated roadmap ↗Secure networks. Shorter audits.
Financial data crosses networks you don't control, and it may be recorded today for decryption later. VeilNet encrypts and authenticates every connection, with no third party in the path.
End-to-end encryption
Traffic is encrypted twice: hop by hop with TLS 1.3, and end to end with ML-KEM-1024 and AES-256-GCM. Today's intercept won't become tomorrow's disclosure.
Zero-trust authentication
Every system proves its membership with a signed credential chain before any data moves. A stolen password or a trusted subnet gets an attacker nowhere.
Smarter permissions
Taints split the network into compartments: two systems exchange data only if one carries every taint the other does. Suppliers, auditors and test environments each stay in their own, and no system can put itself in one.
Need post-quantum protection before the deadline?
Start with the system you'd least like exposed. The assessment shows what you can safely publish today, what still lacks post-quantum protection, and what each option costs. You keep the report, whatever you decide.