Safety posture is explicit
Evaluation separates a conservative operating posture from performance-oriented modes, so you always know which trade-offs are in effect during a test.
Security & trust
Evidence you can take to a review board.
A ledger is only as trustworthy as what it can prove. TulaDB's private-preview posture is built around explicit safety modes, an explicit security envelope, and recovery you can observe — not claims you have to take on faith.
Preview posture: public materials describe design posture, architecture direction, and evaluation guidance. They are not a statement of general availability, production certification, or deployment approval.
Security envelope is explicit
TLS/mTLS support is part of the private-preview security envelope. Production deployments still validate authentication policy, rate limits, audit logging, and network boundaries for their environment.
Recovery has artifacts
Durability, recovery, and replay behavior are evaluated through concrete runtime artifacts and controlled drills — restart equivalence you can watch, not assume.
Operator visibility
Evaluators can review operational surfaces for account state, transfers, reservations, rejected outcomes, and live runtime status.
Verification targets
What the evaluation package is designed to prove.
These targets exist to produce evidence for correctness, recovery, and operational review — without exposing implementation detail on the public site.
Core correctnessBalanced mutation, durable outcomes, reservation lifecycle, and failure handling.
Model validationDeterministic correctness gates, restart equivalence, and replay checks.
Recovery evidenceCrash/restart and replay behavior under controlled validation.
Replication reviewLeader/follower behavior, quorum progression, and recovery review.
Runtime checksMemory and undefined-behavior checks used as release evidence.
Store verificationOffline consistency probes for review workflows.
Shared responsibility
Clear lines between what the engine provides and what your deployment owns.
Honesty about boundaries is part of trust. TulaDB is precise about the guarantees it makes in preview and the controls that remain the deploying organization's responsibility.
TulaDB provides
Deterministic financial state
Balanced mutation, durable identity, reservation lifecycle, rejected-outcome records, recovery artifacts, and an explicit TLS/mTLS security envelope in preview.
Your deployment owns
Environment controls
Authentication policy, authorization model, rate limiting, audit-log retention, key management, network boundaries, and operational drills for your environment.
Before production
A review checklist, stated plainly.
Preview readiness is for architecture review, performance review, and controlled pilots. Production use should follow deployment-specific work.
Private preview
Put the trust posture in front of your reviewers.
We'll scope an evaluation that produces the evidence your architecture and security teams need to make a decision.