NTFS File Manager Fast USB OTG & internal storage, direct NTFS/exFAT access

Custom software · Android · AI integrations

Software built by the team behind NTFS File Manager

No stock logos or anonymous testimonials. Our main reference is a product you can install today: a native Android file manager on Google Play, with a C filesystem driver, built-in network servers, and more than 1,100 automated tests. We bring the same engineering habits to client work.

Tell us about your project Read the case study

Case study · our own product

Open Windows drives on Android, without root

Android cannot write to NTFS, and many phones cannot read it at all. People with a Windows USB drive had to find a PC first. The app fixes that on the phone, then grew into a full file manager.

What we built

  • Full NTFS read and write through the open-source libntfs-3g driver, compiled for Android and called from Kotlin over JNI
  • An exFAT implementation written in plain Kotlin, including formatting drives from the phone
  • One explorer across internal storage, USB, Dropbox, OneDrive, and SMB, SFTP, FTP and WebDAV shares
  • The phone as a browser, WebDAV or FTP file server, protected by a PIN, with QR pairing
  • Google Play Billing subscriptions, and Google’s consent flow before personalised ads

How we keep it reliable

  • Tests run against real fixtures: generated exFAT disk images, and embedded servers on real sockets
  • Path-traversal attacks are tested over raw sockets, because an HTTP client quietly removes “../” before sending
  • Credentials are stored with Android Keystore-backed encryption, and never fall back to plain storage
  • GitHub Actions runs CI and deploys to Google Play; trade-offs are written down as architecture decisions (42 so far)
  • Kotlin
  • Jetpack Compose
  • Material 3
  • C / JNI
  • CMake
  • SQLite FTS4
  • Coroutines
  • Robolectric
  • Play Billing
  • GitHub Actions

Services

What we can build for you

Five kinds of build work, plus a review if you are not ready to build. Each one lists what you receive at the end, not just a label.

Custom web & mobile applications

Native Android, web front ends and the APIs behind them, built to be run and changed by your team after launch.

You receive

  • Source code in your repository, with CI set up
  • Sign-in, billing and store releases where needed
  • Automated tests for the parts that can lose data or money

Reference: NTFS File Manager

Model Context Protocol (MCP) integration

MCP servers that expose your databases, tickets, files or internal APIs as tools that Claude, Cursor and other MCP clients can call.

You receive

  • An MCP server with narrowly scoped tools and input schemas
  • Authentication and read/write limits for each tool
  • Logs showing which tool was called, by whom, with what inputs

Automated AI workflows

Pipelines that take a slow, repetitive process — triage, extraction, drafting, review — and automate the steps a model can do reliably.

You receive

  • A mapped process, with a human sign-off where mistakes are costly
  • An evaluation set so quality is measured rather than assumed
  • Retries, cost limits and a runbook for when it fails

Developer & internal tools

CLIs, admin dashboards and release tooling that remove the copy-and-paste between systems your engineers do every week.

You receive

  • A tool that fits your existing stack and access controls
  • Usage documentation written for your team
  • A before-and-after measure of the time it saves

Local & on-premises MCP servers

The same MCP approach for sensitive data, running on your own hardware or private cloud, with no data leaving that network.

You receive

  • Deployment on infrastructure you control
  • Secrets handling and network egress rules written down
  • A hardening checklist your security team can review

Technical review of an existing codebase

Not ready to build? We can review what you have — security boundaries, test coverage, architecture — and give you a prioritised, written list.

You receive

  • Findings ranked by risk, each with a reproduction or file reference
  • What to fix now, later, or leave alone

Process

How a project runs

  1. Discovery callWe talk through the problem, constraints and deadlines, and say plainly if custom software is not the right answer.
  2. Written scopeYou get milestones, risks, what is out of scope and a quote before any code is written.
  3. Build in milestonesWorking software at each milestone, in your repository, with tests and a short demo.
  4. HandoffSource, deployment notes and recorded decisions, so your team can own it without us.

Ways to work together

Pick the shape that fits

Prices are quoted after the scope is written, not before.

Fixed-scope project

A defined outcome and milestones. Best when the problem is clear.

Ongoing development

A monthly block of engineering time for a product that keeps changing.

Review & advice

A codebase or architecture review with written findings.

What to include in your first message

  • The problem, and who has it today
  • Systems, APIs or data involved
  • Any deadline, and what is driving it
  • Hard constraints: on-prem only, compliance, data residency

Please don't include passwords, keys or confidential data in the form.

Have a project in mind?

Send a short description through our Google Form. We use it to arrange a discovery call — no pitch deck, no obligation.

Tell us about your project See our work