Architecture: An Overview of QoreDB's Architecture

An overview of QoreDB's architecture

The database client landscape today is dominated by tools that are often seen as heavy, complex, or aging.
Many were designed at a time when usage patterns, security constraints, and expectations around developer experience were very different.

QoreDB was born from a clear vision: to build a desktop, local-first database client that is fast and pleasant to use every day, and able to reconcile the SQL and NoSQL worlds within a single, coherent interface.

That vision is reflected directly in its architecture.

A modern, high-performance technology foundation

To deliver the performance and security of a native application while keeping the flexibility of a modern interface, QoreDB is built on a deliberately demanding hybrid stack.

The application core is built around Tauri 2.0 with a backend written in Rust.
This choice brings:

• high performance
• safe memory management
• fine-grained control over local resources

The user interface is built with React 19.1 and TypeScript 5.8, to deliver a smooth, responsive, and strongly typed experience.
This combination keeps the interface modern without compromising the stability of the application.

Communication between the different layers relies on asynchronous mechanisms, using Tokio on the Rust side. This ensures excellent responsiveness, even when running complex queries or remote connections.

The pillars of the architecture

QoreDB's architecture isn't the result of piling technologies on top of one another.
It rests on strict principles, defined from the outset to ensure the project's consistency and longevity.

Local-first and offline-capable

QoreDB is a locally installed application that works with no mandatory dependency on a SaaS service or cloud infrastructure.
Data, connections, and configuration stay under the developer's control.

Modularity and extensibility

The core of the application is deliberately kept lightweight.
The architecture is designed to accommodate, over time, new drivers, features, or extensions in the form of modules or plugins, without weighing down the whole system.

Determinism and testability

Every architectural choice aims to encourage predictable behavior.
This makes the system easier to understand, simplifies error handling, and supports the automated testing that's essential for a tool meant for daily use.

A unified experience for SQL and NoSQL

One of QoreDB's biggest challenges is offering a consistent experience across fundamentally different technologies, such as PostgreSQL, MySQL, and MongoDB.

Rather than hiding those differences behind excessive abstractions, QoreDB's architecture aims to:

• unify interactions
• preserve the essential specifics of each engine
• offer shared, cross-cutting features

Among the key elements of this approach:

• A secure connection manager
  Credentials are stored via the operating system's native keychains, to comply with each platform's security standards.
• SSH tunneling support
  To secure access to remote databases without needlessly complicating configuration.
• A multi-tab interface
  Allowing you to work on several queries, tables, or databases at once, while keeping a clear view of the current state.

This approach lets you work efficiently across several data paradigms without constantly switching tools or mental models.

Conclusion

QoreDB's architecture favors clarity and control over over-engineering or superfluous SaaS dependencies.

The goal is simple: to build a tool that works with the developer, not against them.
QoreDB is a data platform designed by a developer, for developers, with an architecture built to evolve without losing its coherence.

Upcoming articles will go into more detail on:

• security and the handling of local data
• the technical choices behind the SQL / NoSQL unification
• the trade-offs we've deliberately accepted in certain parts of the system