Company announcements
Kunan Technology relaunches its website
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.
MERAK · Zero trust invisible network platform
Make your services disappear from the internet
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
Now that AI-automated attacks are the norm, invisibility is the last line of defence.
AI-driven automated attacks run around the clock. Merak removes the attacker’s starting point at the architectural layer.
01
Eliminate the attack surface
Attackers cannot find the entry point in the first place.
Learn more 02Point-to-point secure connectivity
Data reaches its destination directly, never relayed through a third party.
Learn more 03Service microsegmentation
Even when a single node is breached, the threat is stopped from spreading sideways.
Learn moreFLAGSHIP PRODUCT
MERAK Zero trust invisible network platform
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.
- One identity each Every user and device carries a digital credential that cannot be forged.
- Verified every time There is no free passage once inside; identity and permissions are re-verified on every connection.
- Invisible network-wide No inbound port is open at all. What cannot be scanned cannot be attacked.
HOW IT WORKS
From establishing identity to an encrypted connection, in five steps.
Deployment requires no change to the existing network. Users notice nothing; attackers see nothing.
01
Establish digital identity
Each endpoint is issued its own cryptographic credential, so identity is verifiable.
02
Deploy lightweight nodes
No change to the existing architecture; the environment is provisioned quickly.
03
Hide the core services
Register the service with the platform and close its inbound ports, so it disappears from the public internet entirely.
04
Set the access policy
Role-based access control (RBAC) defines precisely who may reach what.
05
Establish the encrypted tunnel
Once verification passes, a point-to-point connection is built automatically, and the user notices nothing.
BY THE NUMBERS
Protection that can be measured.
Figures below are drawn from statistics across production deployments.
UPTIME · SLA M · 01
99.9 %
Service availability SLA
INCIDENTS · ↓ M · 02
85 %
Proportion of deployments reporting a significant drop in security incidents
ACCESS · TIME M · 03
80 %
Average reduction in the time taken to configure account permissions
LATEST
News and engineering writing
News
Announcements, events and awards.
Engineering blog
Written by the technical team. Not a product pitch.
Architecture
What SDP v3.0 Changed: SPA Is No Longer the Definition
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.
Threat analysis
VPN vulnerabilities: why patching is always late
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.
FAQ
Frequently asked questions
The questions that come up most often during evaluation. If yours is not covered, please get in touch.
A VPN locks the door, but the door is still there waiting to be forced. Merak makes the service vanish from the outside view entirely: without successful verification, the service simply does not exist.
It begins with requirements gathering and an architecture review, followed by a small-scale proof of concept to confirm compatibility and effect. Formal rollout and staff training are then planned, expanding gradually from a test environment to the whole organisation.
Both agent mode, for company-issued devices, and agentless mode, for BYOD and third-party vendor access. Both preserve the separation between the control plane and the data plane.
No. The control plane handles verification and authorisation in the cloud, while the data plane runs point to point between client and service. Traffic does not pass through Kunan servers.
Use the demo request or the contact page to describe your requirements, and the sales team will follow up to arrange a walkthrough and discuss pricing.
Make your enterprise services invisible, starting today.
See how Merak fits into your existing architecture without disruption, and brings zero trust protection with it.