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 →

A settings console a user can read: tokens, connectors, printers, mail

Users mint API tokens with a name and an expiry and revoke them all at once, read the commands to connect over NFS, FTP and MCP, manage printers, search their notifications, and see every mail sent for them.

A user's settings page is where a platform shows whether it respects the person using it. Over 2026 the console was rebuilt around the questions a user actually asks.

Access

  • API tokens A JWT token carries a name, a description and an expiry. Revoking them all rotates the user's signing salt, so nothing issued before survives. Labels in ten languages.
  • Secrets never shown Credential payloads stopped travelling to the browser. A four-character hint and the source the value falls back to are shown instead.
  • Connectors Cards for NFS with its domain and the Windows caveats, FTP with a ready-made command and automatic TLS, and MCP with its four endpoint worlds, each with the exact command to connect.

Everyday operations

  • Printers Managed with a default printer per user.
  • Cron logs Task logs with drill-down into each run.
  • Notifications A searchable inbox.
  • Mail The mail log held over eleven thousand rows that no screen showed. A Mails section lists them in three outcomes: sent, failed, never sent.

The menu is regrouped into six groups named after questions rather than subsystems. A user looks for "how do I connect" and finds it.