Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Common Lisp
  3. endatabas

endatabas

AGPL-3.0Common Lispv0.2.0-beta.1

A SQL document database with full history, enabling time-travel queries and immutable data.

Visit WebsiteGitHubGitHub
279 stars10 forks0 contributors

What is endatabas?

Endatabas (Endb) is a SQL document database that maintains a complete, immutable history of all data changes, enabling time-travel queries to retrieve data as it existed at any point. It combines the flexibility of document storage for semi-structured JSON-like data with the power of standard SQL and built-in versioning. This solves the problem of tracking data evolution and auditing changes without requiring external logging or complex application logic.

Target Audience

Developers building applications that require inherent auditability, temporal data analysis, or the ability to query historical states, such as in financial systems, regulatory compliance platforms, or versioned content management. Database engineers seeking a document model with relational query capabilities and immutable data storage.

Value Proposition

Developers choose Endatabas over alternatives because it uniquely integrates full historical versioning directly into the database with SQL support, eliminating the need for separate audit logs or custom temporal solutions. Its combination of document flexibility, SQL interface, and immutable change history provides built-in reliability and query capabilities for data evolution.

Overview

SQL document database with full history.

Use Cases

Best For

  • Building applications with strict audit trail and compliance requirements, such as financial transaction systems or healthcare records.
  • Implementing time-travel features to query past data states, like versioned content management or historical analytics dashboards.
  • Developing systems that need to track data evolution over time without overwriting records, such as collaborative editing platforms or configuration management.
  • Storing and querying semi-structured JSON documents while maintaining a complete change history using standard SQL.
  • Creating immutable data logs for debugging or forensic analysis in production environments.
  • Integrating document storage with relational query capabilities where historical data integrity is critical, such as in legal or regulatory platforms.

Not Ideal For

  • Production environments requiring stable, mature database software with long-term vendor support
  • High-throughput OLTP applications where immutable data storage could impose performance overhead
  • Teams needing extensive third-party tooling (e.g., ORMs, GUI clients) or a large community ecosystem
  • Projects with simple CRUD requirements and no need for audit trails or historical querying

Pros & Cons

Pros

Full Historical Versioning

Every data change is preserved immutably, enabling time-travel queries to retrieve past states directly, as highlighted in the key features for auditability and temporal analysis.

SQL Document Flexibility

Combines semi-structured JSON document storage with standard SQL querying, allowing relational operations on flexible data without sacrificing query power, per the project description.

Built-in Audit Trail

Data is never overwritten by design, providing an inherent and reliable change log for compliance and debugging, eliminating the need for external logging systems.

Multi-language Client Support

Offers official client libraries for JavaScript/TypeScript and Python, as shown by the NPM and PyPI badges, simplifying integration into diverse tech stacks.

Cons

Beta Stability Risks

The project is explicitly marked as experimental and in Beta, meaning it may have bugs, breaking changes, or lack production-ready reliability, as noted in the status section.

Complex Development Setup

Building from source requires installing specific versions of SBCL and Rust, and initializing submodules, which can be cumbersome and error-prone for developers.

Limited Ecosystem Maturity

As a new database, it likely lacks extensive documentation, community support, and third-party tools compared to established alternatives like PostgreSQL or MongoDB.

Frequently Asked Questions

Quick Stats

Stars279
Forks10
Contributors0
Open Issues0
Last commit1 year ago
CreatedSince 2023

Tags

#database#document-database#time-travel#sql-database#immutable-data#audit-log#docker#immutable#rust#common-lisp#versioning#sql

Built With

S
SBCL
R
Rust
P
Podman
C
Common Lisp
D
Docker

Links & Resources

Website

Included in

Common Lisp2.9k
Auto-fetched 1 day ago

Related Projects

lispclispc

"Lispsy" Lisp(ish) to C Converter (designed for CLISP)

Stars547
Forks38
Last commit4 years ago
C-meraC-mera

Next-level syntax for C-like languages :)

Stars445
Forks22
Last commit2 months ago
composable query buildercomposable query builder

An SQL generator for Common Lisp.

Stars418
Forks36
Last commit5 months ago
cl-dbicl-dbi

Database independent interface for Common Lisp

Stars230
Forks30
Last commit3 months ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub