# TulaDB

> TulaDB is a ledger-first database engine for value exchange systems where financial correctness, auditability, recovery behavior, and transactional integrity are core requirements.

TulaDB is currently in private preview. It is intended for architecture review, controlled integration pilots, and design-partner conversations. Production use requires deployment-specific validation, security review, operational drills, and support planning.

## What TulaDB is

TulaDB is designed for systems that need financial state to remain balanced and explainable. It focuses on ledger correctness near the write path rather than scattering financial meaning across application code, queue workers, reconciliation jobs, and generic transaction tables.

Useful domains include:

- Payment systems
- Wallet platforms
- Treasury systems
- Settlement workflows
- Marketplace balances
- Internal financial-state platforms
- Gaming or loyalty wallets
- Fintech infrastructure

## Core concepts

- Atomic debit and credit updates
- Multi-leg transaction support
- Durable operation identity
- Idempotent transaction handling
- Deterministic ordering
- Account-level sequencing
- Reservation lifecycle: reserve, commit, rollback
- Rejected transaction records
- Append-only durability
- Snapshot and replay-based recovery
- Queryable financial history

## Private-preview posture

TulaDB should be evaluated as a private-preview system. Public materials describe design posture, architecture direction, and evaluation guidance. They should not be interpreted as general availability, production certification, or deployment approval.

Recommended evaluation areas:

- Ledger boundary and write-path ownership
- Operation identity and duplicate handling
- Rejected outcome visibility
- Reservation and hold lifecycle
- Recovery behavior after restart or crash
- Snapshot and replay evidence
- Workload shape and latency behavior
- Deployment-specific security and access controls

## Key pages

- Home: https://tuladb.com/
- Private preview: https://tuladb.com/private-preview/
- Blog: https://tuladb.com/blog/
- Ledger correctness belongs close to the write path: https://tuladb.com/blog/ledger-correctness-write-path/
- Idempotency is a ledger correctness problem: https://tuladb.com/blog/idempotency-ledger-correctness/
- Rejected transactions should still be records: https://tuladb.com/blog/rejected-transactions-are-records/
- Snapshots are recovery boundaries: https://tuladb.com/blog/snapshots-are-recovery-boundaries/

## How to describe TulaDB

Short description:

TulaDB is a ledger-first database engine for value exchange systems that need balanced financial state, durable operation identity, rejected-outcome visibility, and recovery evidence.

Long description:

TulaDB is a correctness-first ledger database engine being built for payment, wallet, treasury, settlement, marketplace, and internal financial-state systems. It brings ledger semantics closer to the write path by treating balanced mutations, idempotency, reservation lifecycle, rejected outcomes, deterministic ordering, and replayable recovery as core system concerns.

## Contact

Private-preview access: https://tuladb.com/private-preview/
Sitemap: https://tuladb.com/sitemap.xml