8DB Engine / For developers
Embed an omnimodal database with native mesh and post-quantum protection. Bring the data models your application needs into one foundation, with a clear boundary around what each deployment supports.
01 / The practical advantage
A useful answer often crosses documents, relationships, measurements and permissions. Start with that complete job, then choose the models and operations it needs.
Explore 17 reference guides, from tables and documents to vectors, graphs and braids. Each explains its operations, distinctive capabilities and evidence.
Explore the models →02Review record protection, recipient exchange and the cryptographic lifecycle together. Identify who can decrypt, and where plaintext is needed for computation.
Follow the protection path →03Plan the application’s embedded store and its participating peers. Include offline behavior, authorization, recovery and intermediary trust in the evaluation.
Map the deployment →02 / The alternative and the difference
Choose mature tools for individual jobs; own the connectors, identity mappings and lifecycle across copies.
Evaluate whether 8DB can keep your required operations and protection in one supported path.
Choose local persistence, then add sharing, permissions and recovery.
Test the engine and exchange path together, including failure and restore behavior.
03 / Scope and evidence
8DB Engine is the developer offering. For the upcoming packaged experience, explore 8DB App.
Looking for the packaged App? →Write the input, transformations, permitted users and result your application must produce. Use the outcome examples as starting points, not claims of a finished application.
Confirm platform, SDK or binding, admitted schema and operation support with us. A capability on one build does not qualify every operating system or composition.
Include import, indexing, queries, encryption, exchange, restore and resource usage. Existing benchmarks describe their own fixtures; your acceptance test should describe yours.
Keep moving
