One API.
Every protocol
your Java app needs.
jMount is a unified connector suite for Java teams tired of stitching together open-source libraries for every new protocol. A dozen connectors – and growing fast – spanning file & network protocols, object storage , collaboration platforms, and cloud file shares. One maintained API, one vendor, one SLA.
Trusted By
Different problems.
Same solution.
Stop stitching connectors together. Start shipping features.
You’ve been handed a bunch of separate protocol integrations, each with its own API, its own authentication model, its own update cycle, and its own failure modes. Adding a fourth is another rabbit hole. jMount changes that equation.
- One unified API surface across all protocols – learn once, connect anywhere
- Drop-in replacement for fragmented vendor SDKs and isolated protocol libraries
- Each connector independently adoptable or combined as your architecture requires
- 24/7 support from dedicated protocol experts, not documentation you have to reverse-engineer
Migration was smooth thanks to clear docs and examples. Support responded within an hour and resolved our ticket overnight.
Michael Reif, IT Department, Enterprise Customer
Multiple storage backends. One API and modular foundation.
You’re designing a platform that needs to reach multiple storage backends. Right now that means a different integration point for each one – different dependencies, different authentication flows, different risks. jMount gives you a single, extensible foundation that grows with your requirements.
- Shared API surface – add protocols without rearchitecting your integration layer
- Unified auth model – write to one credential and session model in your code; jMount maps it to each backend’s native authentication (Kerberos, SigV4, SAS, OAuth2)
- Production-ready architecture – engineered from the ground up for stability, thread safety, and resource efficiency
- Clean migration path – seamless transition from existing jNQ deployments
The system integration process was trouble-free.
— Remek Trzaska, Manager, Vestiacom / Swisscom
From fragmented protocols overhead to accountable experts’ SLA.
Your teams are spending engineering cycles managing a patchwork of isolated protocol connectors – each one its own vendor relationship, its own maintenance burden, its own compliance question. jMount consolidates that into a single commercial platform with one contract, one SLA, and one team accountable for all of it.
- Replace fragmented vendor SDK relationships with a single unified platform
- Redirect engineering capacity from connector maintenance to core product development
- Direct SMB patent license from Microsoft – zero IP exposure risk
- Engineered for FIPS, NIS2, and enterprise compliance
After years with open-source connectivity libraries, Visuality proved to be the only solution offering reliable support and faster speeds.
— Alistair Jones, CTO, Ohalo
Connector Maintenance
Is A Tax On Every Release.
Java environments often end up managing a fragmented layer of protocol connectors. Teams either build and maintain them in-house or support inherited code without vendor backing. Either way, protocols become an ongoing liability – not a capability.
Protocol maintenance overhead
IT squads waste time maintaining complex connectors. Instead of scaling operations, they drain engineering capacity that could be used to build products.
Different API per library
Every open-source connector has its own interface, its own quirks, its own failure modes. There’s no consistency across the different protocols.
No SLA, no owner, no escalation path
Storage protocols and cloud APIs continuously evolve. When a silent update breaks an integration in production, custom-built connectors leave your team with no vendor accountability, delayed security patches, and failing compliance reviews.
The Full Connector Set.
File and network protocols
- SMB
- NFS
- FTP/FTPS
The protocols enterprise infrastructure runs on, with full dialect and version coverage.
Object storage
- Amazon S3
- Azure Blob Storage
- Google Cloud Storage
Object stores mapped onto consistent file access patterns, so your application logic does not change per backend.
Enterprise collaboration platforms
- SharePoint
- OneDrive
- Google Drive
Document platforms with authentication, metadata, and versioning handled for you.
Managed cloud file shares
- Azure Files
Cloud-hosted file shares accessed through the same file semantics your application already uses.
Not every backend supports every file operation natively.
We document exactly what each connector supports, and how
jMount maps a uniform API onto backends that behave differently.
Start with what you need.
Expand as you grow.
jMount available modules support on-premises file protocols, cloud storage, and enterprise collaboration platforms. Adopt one, adopt several, or adopt the entire suite. Each connector works independently behind the same API.
A single, protocol-agnostic API facade – Mount, File, Directory, and standard streams – unifying file, cloud, and collaboration storage under one interface.
- Connect to file shares, object stores, and collaboration platforms through a single consistent interface
- Zero native code dependencies; load only the specific connector modules your deployment requires
- Clear, documented backend capabilities with explicit error handling where backends genuinely diverge
- Built-in tracing and internal, Wireshark-readable pcapng packet captures generated directly inside the JVM
Robust SMB integration for enterprise Java apps where file access is a core capability. Built by the team behind the most widely deployed commercial SMB protocol libraries.
- Full SMB2 through SMB3.1.1 client: signing, AES-GCM encryption, Kerberos/IAKerb and NTLM
- SMB over QUIC with a built-in TLS 1.3 stack - file shares across the public internet, no VPN
- Proven interoperability with Windows Server, Samba, NetApp, Azure Files, FSx and Nutanix
- Licensed under Microsoft's SMB patent program
Enterprise NFS connectivity for Java applications, from on-premises NAS filers to managed cloud file services – covering the version spectrum that most Java libraries do not reach.
- NFSv3, NFSv4.0 and NFSv4.1, with NFSv4.2 negotiated
- NFS over TLS (RFC 9289) and NFS carried inside a TLS tunnel - encrypted transport with no stunnel, no OS mount helper and no native code
- Kerberos via RPCSEC_GSS, with per-request integrity and privacy
- Reaches Amazon EFS, Azure Files NFS shares, Google Filestore, Azure NetApp Files, the Azure Blob NFS 3.0 endpoint, and NetApp, Isilon, Qumulo and Nutanix filers
Standard FTP with explicit TLS, for the transfer endpoints that remain in production across every enterprise estate.
- FTP (RFC 959) with explicit FTPS, protecting both control and data channels
- Passive mode with EPSV and PASV; IPv6 supported
- Reaches vsftpd, ProFTPD, Pure-FTPd, FileZilla Server, IIS FTP and AWS Transfer Family
- Same API, credentials and error model as every other connector
Buckets behind the same Mount, File and Directory API your application already uses for file shares.
- Full S3 REST support with AWS SigV4 request signing
- One connector reaches the S3-compatible world: MinIO, Ceph, Wasabi, Cloudflare R2, Backblaze B2, Dell ECS, NetApp StorageGRID, OCI, IBM COS and more
- Streaming transfers and ranged reads; object semantics documented, never emulated
- Built on the official AWS SDK for Java, with credentials managed centrally
Containers and blobs mapped onto consistent file access patterns, so application logic does not change per backend.
- Azure Blob REST across all access tiers, with shared-key authentication
- Works against the Azurite emulator and Azure Stack Hub for local development
- Streaming transfers and ranged reads through the standard java.io stream adapters
- Built on the official Azure Storage SDK
Google Cloud Storage buckets through the same unified API, authenticated with service-account credentials.
- GCS JSON API with service-account authentication
- Also reaches the GCS XML interoperability endpoint
- Streaming transfers and ranged reads; provider limits surfaced as explicit errors
- Built on the official Google Cloud client library
Document libraries reached through Microsoft Graph, with enterprise authentication handled for you.
- SharePoint Online document libraries through the Microsoft Graph API
- Microsoft Teams files included - every Team is a SharePoint site underneath
- OAuth 2.0 client-credentials flow with short-lived scoped tokens; no passwords on the wire
- Documents, folders, metadata and enumeration through the same API as every other backend
Per-user drives through Microsoft Graph, using the same tenant and app registration as SharePoint.
- OneDrive for Business and OneDrive Personal
- Microsoft Graph API, with the same token model as the SharePoint connector
- OAuth 2.0 client-credentials flow with short-lived scoped tokens
- File and directory operations through the unified API, no Graph-specific code in your application
Managed cloud file shares with real directory semantics, reached over HTTPS rather than over a network mount.
- Azure Files over the FileREST API: real directories and server-side rename
- Ranged reads and chunked uploads, with shared-key authentication
- The same Azure shares are also reachable over SMB or NFS 4.1 - choose the transport per deployment
- Amazon EFS, FSx, Azure NetApp Files and Google Filestore are served through the NFS and SMB connectors as configuration
Beyond Open Source.
Enterprise-Grade
Storage Innovation.
One API, every protocol
A shared interface across SMB, NFS, cloud and future connectors. Add protocols to your stack without redesigning your integration layer or learning a new implementation model each time.
A team that owns it with you
When something breaks, you’re not posting on a forum and waiting. You have direct access to the engineers who built the protocol stack, helping with bug fixes, new features, and ongoing development so your team isn’t carrying that weight alone.
Full accountability, one vendor
One contract, one SLA, one team responsible for every connector in your stack. No finger-pointing between maintainers. No wondering if the library you depend on is still being watched by anyone.
Modular adoption
Start with one connector. Add object storage, cloud file shares, or collaboration platforms on your own timeline. Each connector works independently or as part of the suite, without rearchitecting your integration layer.
Always current
Protocol standards evolve. Security requirements change. jMount tracks them – so you do not have to assign engineers to monitor spec updates, patch vulnerabilities, or chase compatibility issues across multiple codebases.
Enterprise-ready from day one
Designed for organizations where “good enough” isn’t an option for production infrastructure. jMount combines native enterprise auth like Kerberos with an architecture designed to support FIPS, NIS2, and ISMAP regulatory baselines.
One API, every protocol
A shared interface across all thirteen connectors and every one that follows. Add protocols to your stack without redesigning your integration layer or learning a new implementation model each time.
A team that owns it with you
When something breaks, you’re not posting on a forum and waiting. You have direct access to the engineers who built the protocol stack, helping with bug fixes, new features, and ongoing development so your team isn’t carrying that weight alone.
Full accountability, one vendor
One contract, one SLA, one team responsible for every connector in your stack. No finger-pointing between maintainers. No wondering if the library you depend on is still being watched by anyone.
Modular adoption
Start with one connector. Add object storage, cloud file shares, or collaboration platforms on your own timeline. Each connector works independently or as part of the suite, without rearchitecting your integration layer.
Always current
Protocol standards evolve. Security requirements change. jMount tracks them, so you do not have to assign engineers to monitor spec updates, patch vulnerabilities, or chase compatibility issues across multiple codebases.
Enterprise-ready from day one
FIPS, NIS2, Kerberos, and ISMAP readiness built in. Designed for organizations where “good enough” is not an option for production infrastructure.
Since 1998. Powering Millions of
Enterprise Systems Worldwide.
200+
Global enterprise customers
25+yr
Protocol expertise
24/7
Engineer-level support
“Visuality guided our shift to a secure file transfer system, and their on-site support helped us quickly identify and resolve integration issues.”
| Pavan Chenjeri, R&D SW Program Manager – ZEISS |  |
“Visuality Systems adapts quickly to requests or changes, reflecting the same commitment we offer our own customers.”
| Udo Bartmus, Head of Connectors Dev – Seeburger | |
“We have been impressed by Visuality’s five-star support services. We look forward to continuing working with them for years to come.”
| Mazhar Lateef, CTO – ShareArchiver | |
