Supporting methodology and editorial history

Article: 8DB protected storage | Post-quantum keys. The same compact records.

Retained October 9, 2026 from the article at source c04aea4. These passages preserve the original scope, methodology and revision history behind the commercial summary. They are not new test results. Original source references remain in the article.

An application may need a record, its relationships, a time series and a similarity search. 8DB's native modalities create an opportunity to use a common engine and protection architecture across those needs. The reviewed integrated message-exchange profile currently covers canonical lexical records; broader application schemas need integration and qualification.

Content recovery succeeded in all four runs. Availability was a separate test: three runs missed some one-second read deadlines; one met all 689 eligible deadlines. The passing run's p99 was 739 ms. That is a completed, bounded result, with the earlier failures retained. Different revisions and shared-host conditions mean it does not yet prove a repeatable zero-downtime migration.

Vendor-run engineering evidence, with source and original-output links in the public packages. The paired record tests use source 4efb7653; profile-cost tests use cc994fc6; migration runs retain their individual revisions and audit results. The corpus size in a benchmark heading does not make every timed operation a complete database workload. No matched competitor speed ranking, module-validation certificate or universal deployment qualification is implied.

Other architectures can also share key-establishment work and signatures. The value to evaluate in 8DB is how much of the required workflow is already connected inside the engine. We have not measured a complete, equivalent protected workflow against every product in this chart.