SurrealDB client

Choose Auth Level for the user: Root, Namespace, Database, Record Access or Token. Namespace and Database require their names. Record Access also requires the access method and sign-in fields; Token accepts an existing JWT.

The driver talks CBOR over the HTTP RPC endpoint, so record links, datetimes, durations, decimals and UUIDs keep their types. A surrealdb:// link opens the connection form filled in, and a remote server can be reached through an SSH tunnel.

SSL starts Disabled, which is plain HTTP; every other mode uses HTTPS. Verify CA and Verify Identity check the certificate against the system trust store, and a CA file set in the SSL/TLS pane is ignored, so install a private CA in macOS first.

Run complete SurrealQL scripts, including RELATE, with statement completion. Explain and Explain Full run the query with EXPLAIN and return a text plan.

Namespaces sit at the top of the sidebar with their databases inside. Switching either never reconnects, because the namespace and database ride on each request. Only a root user sees every namespace.

Cell edits update only changed fields as typed parameters, preserving computed FUTURE fields and other writers’ changes. Leave id empty for an autogenerated ID. SCHEMALESS table columns come from fetched records.

Filters become SurrealQL, and a Raw SQL row takes one condition, such as a graph traversal. A condition that writes, holds a ; or a comment, or calls into fn:: or http:: is refused; run it in the editor.

The Structure tab is read-only. Create and change fields and indexes with DEFINE FIELD and DEFINE INDEX in the editor. A namespace or a database is dropped from its menu, and selecting several asks once for all of them.

There is no import. Export a table or a SurrealQL result as CSV, JSON, SQL, XLSX, Markdown, HTML and XML.

The iPhone and iPad app has no SurrealDB driver. SurrealDB connections synced from a Mac appear in its list but do not open.