WEBVTT

00:00.560 --> 00:02.536
You update a record.

00:02.690 --> 00:04.341
The old value is gone.

00:05.740 --> 00:08.584
SirixDB keeps every version.

00:08.690 --> 00:10.990
Each commit writes only what changed

00:11.050 --> 00:12.450
and shares the rest,

00:12.670 --> 00:14.736
so storage grows with the change,

00:14.758 --> 00:15.965
not the history.

00:17.150 --> 00:19.693
Any revision opens directly:

00:19.820 --> 00:21.130
by number,

00:21.560 --> 00:23.110
by timestamp,

00:23.520 --> 00:25.310
or bitemporally.

00:25.768 --> 00:27.357
Nothing to replay:

00:27.514 --> 00:30.017
revision one reads like the latest.

00:31.250 --> 00:34.803
Every field keeps its identity across revisions.

00:34.976 --> 00:36.846
Follow one value through time,

00:36.868 --> 00:39.156
or diff any two revisions:

00:39.250 --> 00:42.594
exact inserts, updates and deletes.

00:43.820 --> 00:45.338
And it's bitemporal:

00:45.360 --> 00:48.027
SirixDB knows when a fact was recorded

00:48.049 --> 00:49.865
and when it was true,

00:49.968 --> 00:53.619
so a correction never erases what you knew.

00:55.410 --> 00:57.939
Its indexes are versioned too,

00:57.960 --> 01:00.000
including columnar projections

01:00.040 --> 01:02.940
for fast analytics on any revision.

01:04.040 --> 01:06.571
Embed it as a Java library,

01:06.683 --> 01:08.395
run the REST server,

01:08.462 --> 01:09.855
use the shell,

01:10.007 --> 01:13.805
or let AI agents edit safely over MCP.

01:14.990 --> 01:16.727
SirixDB.

01:16.900 --> 01:18.700
Every version of your data,

01:18.730 --> 01:22.200
kept and queryable as fast as the present.

01:22.560 --> 01:25.280
Append-only, bitemporal,

01:25.360 --> 01:28.010
embeddable, and open source.
