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 →

Operating a machine from Studio: its own key, ten root operations, tickets

Studio reaches each managed machine with a key of its own, may run as root only a fixed catalogue of ten operations shipped with the product, and opens every SSH terminal by a one-time ticket issued on the server.

Running an operation on a database host from an administration console raises one question first: what exactly may the console do as root? This release answers it with a narrow account, a program that knows a fixed list, and terminals the browser cannot point anywhere.

A key per machine

  • One Studio key per machine An ed25519 pair made inside the keystore, its private half never leaving it, so a stolen key opens one machine.
  • A restricted account The install script creates an account with no usable password whose authorised keys are exactly Studio's, accepted only from the Studio nodes, and proves the install by a login with the key alone.
  • Rotation without a password A next key is written beside the active one, Studio logs in with it before anything is retired, and only then is the old key removed and recorded as retired.

Ten operations, fixed in code

  • The only root program The account may run one program through sudo. It knows ten operations: disk free, service status, start, stop and restart, and Informix status, logs, checkpoint, start and stop.
  • Refused before it runs Any other code, or a parameter that is not a plain service or server name, ends with a refusal before anything executes.
  • Shipped, not stored The commands ship with the product rather than in a table, because whoever could write that table would choose what runs as root.
  • Recorded Each operation is a row with its result and the SHA-256 of its output; a stop asks for the machine's code to be typed.

Terminals by ticket

  • One use, sixty seconds A ticket is 32 random bytes held in the node's memory, valid once and for its owner only.
  • Resolved on the server Redeeming it reads the target and its credential again and applies the access rules again; the host, the host-key policy and the audit fields never come from the browser.
  • No trust-all hop Every hop checks its host key against known hosts or a pinned fingerprint.

The result is a console that can restart a service or checkpoint a database server, and nothing else, with a record of every time it did.