Database in the Aetherfy dashboard

What the Aetherfy dashboard’s Database area is

The Database area of the Aetherfy dashboard, at app.aetherfy.com/dashboard/database , lists every vector collection on your account and opens one collection at a time.

The record’s header carries the collection’s status, its dimensionality, a reload control and a region selector. On a collection that spans several regions, the selector picks the region the explorer reads from and writes to; it does not move the collection. Placement is changed on the placement tab.

Aetherfy collection status and health labels

The dashboard prints a status in capitals. When the collection list cannot be read, the inventory and the record say so instead of claiming you have no collections or that this one does not exist.

Creating an Aetherfy collection in the dashboard

NEW_COLLECTION on the inventory opens a wizard: a name (3 to 100 letters, digits, underscores and hyphens) and an optional description, then a template or your own dimensions and distance metric (Cosine, Dot Product or Euclidean), then the regions. On a single-region plan the region is your account’s home region; on a multi-region plan you pick from your regions.

The same thing from a terminal is afy collections create <name> --size <n> --distance <metric> (collections), and over HTTP POST /api/v1/collections (collection routes). A collection’s name, dimensions and metric are fixed once it exists.

The Aetherfy vector explorer

The explorer is the root of a collection’s record. It browses the collection 50 points per page, or runs a query.

Each row shows the point’s id, a vector preview and a payload preview; the preview leaves out the payload fields Aetherfy reserves, and the point’s own view shows the whole payload.

The commands are documented at afy vector commands and the routes at the vector REST API. Selection covers the current page only and is cleared when the page changes.

The Aetherfy collection schema tab

The SCHEMA tab of an Aetherfy collection shows two things: the collection’s payload indexes, and its payload schema.

The payload index list is read-only. The schema can be created, edited and deleted here, and ANALYZE DATA samples the collection’s points and suggests a schema. These are the schema routes of the vector API.

The Aetherfy collection placement tab

The PLACEMENT tab of an Aetherfy collection changes where its data lives.

Regions and workspace are saved separately: one change at a time. Both are PATCH /api/v1/collections/{collection_id} on the control plane — see moving a collection between workspaces and Regions and replication. A region change copies or removes data in the background. APPLY first shows what the change will do — the data it copies and deletes, which of your plan’s region changes per 30 days it would be, and how much copying is left — and changes nothing until you confirm. A change your plan’s storage or region-change limits refuse says why there, and cannot be confirmed. A move changes only which workspace reaches the collection: its data and regions stay where they are, so a destination that does not allow every one of its regions refuses the move, and its aliases are deleted.

What the Aetherfy dashboard does not do for collections