kodbox: a self-hosted web file manager with a browser code editor

The problem kodbox solves, and the people it is aimed at

Most file managers on a server assume you will be comfortable on a command line. kodbox goes the other way. The README describes it as "a file manager for web" and as "a web code editor, which allows you to develop websites directly within the web browser". The interaction model it copies is Windows: box selection, drag and drop, ctrl+c and ctrl+v, f2 to rename, right-click menus that change with the file type. If your team already knows Explorer, the learning curve is short.

The audience is narrower than the feature list suggests. This is for someone who has a PHP host, or is willing to run one, and wants a shared file space that also mounts storage the server does not own. The README lists local disk, ftp, webdav, Alibaba Cloud OSS, Tencent Cloud COS, Qiniu, minio and "S3 compatible protocol" as backends. That mix is the actual product: one browser interface over several storage accounts, with permissions per folder and per person.

The second audience is the developer who edits on the server. The text editor claims highlighting for 120 code languages, hex mode for binary files, and fragment loading so large files open without pulling the whole thing into the browser. Markdown gets live preview, formulas, flowcharts, sequence diagrams and UML. Whether that replaces a local editor is a personal call, but the intent is clear.

How kodbox works: PHP application, storage adapters, COW deduplication

The repository layout tells you most of the architecture. index.php sits at the top level as the entry point, with app/, config/, data/, plugins/ and static/ beside it. That is a conventional PHP application: config/ holds settings, data/ holds runtime state, plugins/ is the extension point, and static/ carries the front-end assets. There is no build step described in the README, which fits a project that has to run on shared PHP hosting.

The storage layer is the interesting part. Rather than treating one disk as the truth, kodbox presents several backends through the same file operations. The README claims a COW (copy-on-write) mechanism, with file metadata recording "double hash authentication" and automatic full deduplication. In practice that means an uploaded file whose hash already exists is not stored twice; the README calls the result "seconds transfer" and says folder moves and copies complete quickly. That is a claim from the project, not something verified here.

Above storage sits the collaboration layer: history versions generated when files are edited online, per-file and per-folder permissions, external share links with passwords and expiry dates, and an activity feed the README calls "document dynamics". The permission model is the one to examine before you commit. The README says permissions can be set differently for different people or groups, which is flexible and also means the access rules live in the application database rather than in the filesystem, where your operating system's own tools cannot see them.

Installing kodbox and opening the first folder

The README does not contain install commands. It states that the only requirement is PHP 5, and it points to three places: the download page at https://kodcloud.com/download/, the documentation at https://doc.kodcloud.com/v2/#/, and a live demo at http://demo.kodcloud.com/ with the credentials demo/demo. Treat the documentation as the install source, not this article.

The demo is the fastest way to see the interface before you commit a server. It is a shared public instance, so do not upload anything you care about.

# Open the hosted demo in a browser
demo.kodcloud.com
# user: demo
# password: demo

For a local deployment the README describes running kodbox "either online or locally, on Linux, Windows or Mac based platforms". The repository ships index.php at the top level, so the deployment shape follows the usual PHP pattern: serve the directory with a PHP-capable web server and open index.php. The README does not name a web server, a PHP extension list, or a database, so check the documentation for the current requirements before you pick a host.

Once the application is reachable, the first real task is attaching storage. The README lists the supported backends (local disk, ftp, webdav, Alibaba Cloud OSS, Tencent Cloud COS, Qiniu, minio, S3 compatible). Adding one of those is where kodbox stops being a plain file listing and starts being the multi-cloud tool it advertises. The exact screen and field names are not in the README; the documentation is where they are described.

Where kodbox is the wrong tool

The stated PHP 5 requirement is the first thing to weigh. PHP 5 reached end of life years ago, and most managed hosts no longer offer it. If the documentation still says PHP 5 when you read it, you are deploying on a runtime your host may refuse to provide, and one that receives no security fixes. That is a deployment constraint, not a stylistic preference.

The licence is the second problem. The repository has no licence file among its top-level entries, and the project metadata lists the licence as unknown. For personal use that may not matter. For a company putting internal documents on it, an unidentified licence is a question for whoever signs off on software, and it cannot be answered from the repository.

Third, the feature list is broad enough that it should make you cautious. Online preview and editing of Office documents, PhotoShop and Illustrator files, AutoCAD drawings, online decompression of zip, tar, gz, 7z and rar, Visio flowcharts: each of those is normally a separate piece of software. The README does not explain which of them run server-side, which need an external service, and which are partial. If your use case depends on one specific format, test that format first rather than assuming the whole list behaves the same.

Finally, this is a file manager, not a sync engine or a document collaboration platform. The README mentions clients for web, H5, iOS, Android, PC and WebDAV mounting, but if what you actually need is conflict-free simultaneous editing of one document by several people, that is a different class of product.

kodbox compared with Nextcloud and with plain WebDAV tools

The comparison people search for is kodbox versus Nextcloud, and the difference is in where each puts its weight. Nextcloud is built around sync clients and a calendar, contacts and mail suite around the files. kodbox is built around the browser file manager: the README's emphasis is on selection behaviour, shortcut keys, right-click menus, view modes and the online editor, with sync described only as client coverage and WebDAV mounting. If your users live in a desktop sync folder, Nextcloud's model fits better. If they open a browser and work in it, kodbox's model is the closer match.

Against a minimal WebDAV file browser, the difference is the storage layer. A plain WebDAV server exposes one filesystem. kodbox's README describes a layer that can present local disk, ftp, webdav, OSS, COS, Qiniu, minio and S3-compatible storage through the same interface, with deduplication across uploads. That is more moving parts and more configuration, and it is the reason to choose kodbox over something smaller.

One more distinction worth stating: kodbox is a PHP application with a top-level index.php and a plugins/ directory, and the README presents it as installable on ordinary PHP hosting. Products in this space that require containers, a database cluster and a background worker process are not drop-in replacements for it, and kodbox is not a drop-in replacement for them either.

Maintenance, releases and what the missing licence means for upgrades

The repository is not archived, and the last push was on 2026-08-21, which is the same timestamp as the 1.69.03 release. Before that, 1.68.10 landed on 2026-07-01 and 1.67.02 on 2026-05-13. That is a roughly six-to-eight-week rhythm across the three most recent releases, which is enough to plan around and not so fast that upgrades become a weekly chore. The ChangeLog.md file at the top level is where the project records what changed, so read it before each upgrade rather than after.

Upgrade cost is hard to estimate from the repository alone. The README does not document a rollback procedure, a migration path between versions, or whether the database schema changes between releases. Because the application keeps its own metadata (the README describes metadata recording double hashes for deduplication, plus history versions and permissions), an upgrade touches state that a plain file copy would not. Back up data/ and your database before applying a release, and check the documentation for the supported upgrade route.

The licence question returns here. With no licence file in the repository, there is nothing to read about redistribution, modification or commercial use. That is a factual gap, not a legal opinion, and it is the first thing to resolve if kodbox is going anywhere near company data.

Editorial conclusion

Adopt kodbox if you want a Windows-like file manager you can host yourself, with multi-cloud storage and browser editing of code and Markdown, and you accept PHP 5 as the stated requirement. Do not adopt it if you need a documented licence before deployment, or a release cadence you can plan upgrades around: the repository carries no licence file, and the last push was on 2026-08-21. Before installing, open https://doc.kodcloud.com/v2/#/ and read the section for your platform, because the README itself gives no install commands.

Frequently asked questions

Official sources

1. Issues
2. kalcaddle/kodbox on GitHub
3. Project website
4. README
5. Releases