SapixDB is the world's first agent-native database. It treats every record as a cryptographically signed nucleotide, hash-linked into an immutable strand — giving you built-in audit trails, time travel queries, and schema evolution without migrations.

How is SapixDB different from PostgreSQL or MongoDB?

Traditional databases store mutable rows with no built-in history. SapixDB is append-only by design: every write is cryptographically signed and linked to its predecessor. You get immutable audit trails, time travel, and agent-owned data ownership without external tooling.

Does SapixDB require schema migrations?

No. SapixDB uses Mutant-governed schema evolution — the schema evolves in place via versioned nucleotide types, never requiring ALTER TABLE or migration scripts.

Is SapixDB HIPAA and SOX compliant?

Yes. Because every record is cryptographically signed and immutably linked, SapixDB produces a tamper-evident audit trail natively. HIPAA data lineage and SOX financial audit requirements are satisfied at the storage layer without external compliance tooling.

How do I get started with SapixDB?

SapixDB is available as a Docker image. Run `docker compose up -d` and the agent starts on port 7475. Community is free forever. A 30-day Enterprise trial is available at sapixdb.com/trial — no credit card required.

Is there a free plan?

Yes. The Community plan is free forever with no expiry — up to 5 agents and 10 GB storage, including all core features: cryptographic strands, SaQL queries, time travel, HIPAA, SOX, graph, and blobs. Paid plans unlock higher limits and replication.

Community · SaQL

Sort Order

Control whether scan results are returned oldest-first or newest-first using the order field in any SaQL scan query.

Endpoint

Method	Path	Relevant field	Values
`POST`	`/v1/agents/:id/query`	`order`	`"asc"` \| `"desc"`

Default Order

When order is omitted, SapixDB returns records in ascending strand order — oldest record first, newest last. This mirrors the physical write order inside the strand.

SaQL — ascending (default)

POST /v1/agents/events/query
Authorization: Bearer spx_root_YOUR_ROOT_KEY
Content-Type: application/json

{
  "type": "scan",
  "limit": 5
}

SaQL — ascending explicit

{
  "type":  "scan",
  "limit": 5,
  "order": "asc"
}

ℹ Strand orderRecords are stored in HLC (Hybrid Logical Clock) sequence. Ascending order is therefore strictly causal — you always read history in the order events actually happened, even across nodes.

Descending Order

Set "order": "desc"to flip the result set so the most-recent record appears first. This is useful for dashboards, activity feeds, and "latest N events" queries.

SaQL — newest first

{
  "type":  "scan",
  "limit": 5,
  "order": "desc"
}

curl

curl -s -X POST http://localhost:7475/v1/agents/events/query \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer spx_root_YOUR_ROOT_KEY" \
  -d '{"type": "scan", "limit": 5, "order": "desc"}' \
  | python3 -m json.tool

Filters and Sort Order

Filtering always happens before the sort direction is applied. SapixDB collects all records that satisfy the filter predicate, then reverses the result set when order is "desc". The limit is applied after filtering and after reversal.

SaQL — filter then sort descending

{
  "type":   "scan",
  "limit":  10,
  "order":  "desc",
  "filter": {
    "field": "type",
    "op":    "eq",
    "value": "purchase"
  }
}

⚠ Filter-before-sort semanticsThe engine never skips a matching record because of sort order. Predicates are evaluated on the full strand first; only the matching subset is sorted and truncated to limit.

Field Reference

Field	Type	Default	Description
`order`	`"asc"` \| `"desc"`	`"asc"`	Sort direction for the returned records. `asc` = oldest first (strand order); `desc` = newest first.
`limit`	integer	—	Maximum number of records to return. Applied after filtering and after sort direction.
`filter`	object	none	Predicate applied before sorting. See the SaQL reference for filter syntax.

Python SDK Example

The Python SDK passes the full SaQL body as a dictionary. Sorting is controlled by the same order key.

Python

import requests

BASE = "http://localhost:7475"
AGENT = "events"
HEADERS = {
    "Content-Type": "application/json",
    "Authorization": "Bearer spx_root_YOUR_ROOT_KEY",
}

# Newest 20 purchase events
payload = {
    "type":   "scan",
    "limit":  20,
    "order":  "desc",
    "filter": {"field": "type", "op": "eq", "value": "purchase"},
}

resp = requests.post(
    f"{BASE}/v1/agents/{AGENT}/query",
    json=payload,
    headers=HEADERS,
)
resp.raise_for_status()

for record in resp.json()["records"]:
    print(record["timestamp_hlc"], record["data"])

✓ Tip: combine order with cursor paginationTo page through results newest-first, set "order": "desc" and use after_hlc with the timestamp_hlc of the last record on each page. See Cursor Pagination.