Graph

ArangoDB

ArangoDB runs live AQL through an authenticated TLS-capable HTTP client, consumes bounded cursor batches, and cleans server cursors on completion or failure.

Available for HTTP and AQL queries12 minDesktop

Prerequisites

Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
Have the endpoint, database file, or cloud account details for a ArangoDB datastore you are authorized to use. Start with least-privileged, read-only access.
Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

1
Create the connection
Open Library, choose Create connection, and select ArangoDB and a supported Connection method tab.
2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.
ArangoDB connection setup. The ArangoDB connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the ArangoDB Explorer where supported.
4
Select a scope
Select the graph / database scope that should be attached to the new tab.
5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.
ArangoDB native workflow. A representative ArangoDB explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

Field	Required	Purpose	Safe example
Name	Yes	A clear profile name, without credentials.	ArangoDB development
Connection method	Yes	Choose a supported tab. The fields below apply only to the selected method and deployment.	Connection fields / Connection string
Environment	No	Attach the intended variable and safety context.	Local development
Read-only connection	No	Enable for initial exploration. This does not make pre-release software safe for production workloads.	Enabled
Host / Port	No	Endpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.	localhost / engine default
Database / default scope	No	Initial scope for browsing, where supported.	catalog
Complete connection string	Yes	Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.	Paste your complete provider string; do not share it
Username	No	Authentication identity for the selected method.	catalog_reader
Password	No	Required only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.	Stored in the desktop OS vault
Protocol	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	arango-http
Endpoint	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Database / graph	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Path prefix	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Use TLS	No	TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Verify certificates	No	TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
CA certificate	No	TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Client certificate	No	TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Client key	No	TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Connect timeout (ms)	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Query timeout (ms)	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default

Run the sample query

ArangoDB read-only example

FOR product IN products
  FILTER product.active == true
  SORT product.name
  LIMIT 25
  RETURN { name: product.name, category: product.category }

Explore and inspect

Browse databases, collections, graphs, vertex and edge collections, analyzers where available, indexes, constraints-like rules, access, metrics, and diagnostics.
Inspect document rows, graph paths, vertices, edges, raw JSON, profile payloads, collection metadata, and metrics panels.

Diagnose, administer, and transfer

Review metrics, permissions, collection/index posture, graph definitions, query profile payloads, access warnings, and endpoint health.
Preview index changes, graph/collection operations, access changes, metrics review, import/export, and destructive graph or collection plans.
Import — Live. ArangoDB streams collection exports through paged AQL cursors and imports through the complete, duplicate-safe Import API. _key and edge endpoints are preserved; server-owned revisions are regenerated. Formats: JSON (portable), NDJSON (portable). Destinations: local file.
Export — Live. ArangoDB streams collection exports through paged AQL cursors and imports through the complete, duplicate-safe Import API. _key and edge endpoints are preserved; server-owned revisions are regenerated. Formats: JSON (portable), NDJSON (portable). Destinations: local file.
Backup — Plan only. ArangoDB Hot Backup is available when the server edition supports it. Formats: Native managed backup (native). Destinations: repository. ArangoDB Hot Backup execution requires an Enterprise server exposing the Hot Backup API, sufficient permissions, and opt-in real-service validation.
Restore — Plan only. ArangoDB Hot Backup is available when the server edition supports it. Formats: Native managed backup (native). Destinations: repository. ArangoDB Hot Backup execution requires an Enterprise server exposing the Hot Backup API, sufficient permissions, and opt-in real-service validation.

Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. — **Transfers Center.** Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

Capability	Status	Notes
Native explorer	Available	Browse databases, collections, graphs, vertex and edge collections, analyzers where available, indexes, constraints-like rules, access, metrics, and diagnostics.
Read queries	Available	Run AQL reads and guarded writes with live collection/graph metadata, deterministic AQL IntelliSense, bounded traversals, cursor cleanup, and profile requests.
Inline editing	Unavailable	Use a reviewed statement or the engine-native tool instead.
Diagnostics / administration	Guarded	Preview index changes, graph/collection operations, access changes, metrics review, import/export, and destructive graph or collection plans.
Import / export / transfer	Guarded	Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

Symptom	Resolution
Test connection fails or times out	Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabled	Confirm the selected graph / database, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabled	Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columns	Replace the example names with objects from your ArangoDB datastore, confirm the selected graph / database, and keep the query bounded while you validate the result.

Prerequisites

Create the connection

Test and save

Open the native explorer

Select a scope

Run a bounded read

Inspect the result

Export when needed

Open diagnostics or transfers