MERAK · Zero trust invisible network platform
No exposed IP. No open ports. Zero attack surface. A genuinely invisible enterprise network, built on zero trust.
CONNECTED · AUTHORIZED
NODES 128
Zero Trust Access
Hidden Network
The service is visible and an encrypted session is established. Every access is verified dynamically, over the shortest path and at the lowest latency.
STATUS ● CONNECTED
WHY MERAK
AI-driven automated attacks run around the clock. Merak removes the attacker’s starting point at the architectural layer.
Attackers cannot find the entry point in the first place.
Learn more 02Data reaches its destination directly, never relayed through a third party.
Learn more 03Even when a single node is breached, the threat is stopped from spreading sideways.
Learn moreFLAGSHIP PRODUCT
Leave behind the VPN risk of one key opening the whole building. Merak issues one credential per identity and re-verifies it at every door; an unauthorised request cannot even see where the service is.
HOW IT WORKS
Deployment requires no change to the existing network. Users notice nothing; attackers see nothing.
01
Each endpoint is issued its own cryptographic credential, so identity is verifiable.
02
No change to the existing architecture; the environment is provisioned quickly.
03
Register the service with the platform and close its inbound ports, so it disappears from the public internet entirely.
04
Role-based access control (RBAC) defines precisely who may reach what.
05
Once verification passes, a point-to-point connection is built automatically, and the user notices nothing.
BY THE NUMBERS
Figures below are drawn from statistics across production deployments.
99.9 %
Service availability SLA
85 %
Proportion of deployments reporting a significant drop in security incidents
80 %
Average reduction in the time taken to configure account permissions
BLOG
Written by the technical team. Not a product pitch. New to zero trust? Start with these three.
How the three remote access architectures differ across attack surface, data path, access granularity and deployment, with the limits of each.
Read the articlePlane separation, certificate identity, layered encryption, per-connection authorisation and the outbound dial — eight diagrams covering each mechanism of a zero trust network, and what each one costs you.
Read the articleFor the people who sign off the budget rather than build the systems: what zero trust solves, how it differs from what came before, what it is worth, and what to ask your IT team.
Read the articleSynology NAS devices on outdated DSM were hit by .L0CK3D ransomware. Why an exposed NAS has an attack surface before login, which flaws MFA cannot stop, and which risks service hiding, patching and backups each cover.
SDP v3.0 demotes single packet authorisation from definition to option. What the new guide actually changed, why SPA struggles on IoT and cloud functions, where the line between SDP and microsegmentation really falls, and what to do first.
What CISA’s exploited-vulnerability catalogue says about VPN vulnerabilities: how many in six years, why patching starts late, and what a patch cannot undo.
LATEST
Announcements, events and awards.
At Taiwan Innotech Expo 2026, Kunan Technology showed how a service-hiding architecture protects satellite and critical communications — authenticate first, connect second, and stay invisible to everyone else.
The site now carries a dedicated Merak product page, a resources centre and a full English version, with every news item on its own shareable URL.
FAQ
The questions that come up most often during evaluation. If yours is not covered, please get in touch.
See how Merak fits into your existing architecture without disruption, and brings zero trust protection with it.
