ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Database-backed filesystems served over NFS and FTP, mounted from any desktop

The disk tool and the script dictionaries mount as NFS shares with per-user isolated views, short-lived caches and permission bits from file attributes. FTP gains TLS, rate limits and idle timeouts.

A developer's editor expects files. The platform keeps scripts and documents in the database. This release serves them as a network drive, so any editor on any desktop works against the dictionary without a plugin.

NFS

  • Authenticated, per user An NFSv4.1 server exposes the same database-backed filesystems the FTP server already did, with each user's view isolated and credentials carried in the path.
  • Fast enough Short-lived attribute and directory caches; a write channel cached and evicted to the database.
  • Correct enough Permission bits derived from file attributes and read-only state, client address checked against company policy, and virtual tables for the error log and active mounts.

FTP and the desktop

  • FTP hardened A daemon with a configurable backlog and idle timeout, per-transfer rate limits, explicit TLS on the client, and the access type enforced at login.
  • Mount commands shown The user configuration page shows connector cards with the mount command for macOS, Linux and Windows, including the Windows caveat on port and edition, and a ready-made lftp command, in ten languages.

Mounts are audited and evicted when idle since a later release. This is where the drive appeared.