Question 1

What exactly is QoreDB?

Accepted Answer

QoreDB is a modern, open-source, local-first database client, designed for developers who want to work efficiently with SQL and NoSQL databases, without depending on an imposed cloud. It focuses on: performance, security, a polished developer experience, and a long-term vision more ambitious than traditional tools.

Question 2

How is QoreDB different from DBeaver or existing tools?

Accepted Answer

QoreDB does not seek to be a "feature-by-feature" alternative. Key differences: Local-first architecture (no data sent by default) Built-in security and guardrails (environments, read-only, production rules) User experience designed for speed and clarity Unified SQL + NoSQL vision Modern, extensible, long-term oriented codebase QoreDB is designed as a daily work tool, not an "aging Swiss Army knife".

Question 3

Is QoreDB really open-source?

Accepted Answer

Yes. The core of QoreDB is open-source, readable, auditable, and modifiable. Transparency is part of the project's DNA. Eventually, some advanced features may exist as a paid offering, without ever removing essential capabilities from the open-source version.

Question 4

Is QoreDB free?

Accepted Answer

Yes. QoreDB is free to download and use, on macOS, Windows, and Linux. A paid offer may exist in the future for advanced or professional uses, but the core of the product will remain free and usable without cost.

Question 5

Is my data sent anywhere?

Accepted Answer

No. By default: Connections, queries, and data remain strictly local. No database is proxied or stored on a remote server. Measurement tools (analytics) are: disabled by default anonymous explicit opt-in QoreDB adopts a privacy-first philosophy.

Question 6

Do you use analytics tools?

Accepted Answer

Yes, but with strict rules. Analytics serve only to: understand feature adoption, improve user experience, prioritize developments. They never collect: database data, complete SQL queries, credentials, sensitive content. Activation is always voluntary.

Question 7

Is QoreDB suitable for production use?

Accepted Answer

Yes, with guardrails. QoreDB integrates: environments (dev / staging / prod), a read-only mode, protections against dangerous queries, cancellation and timeout mechanisms. The goal is to reduce human errors, without slowing down developers.

Question 8

Which databases are supported?

Accepted Answer

QoreDB currently supports 15 native drivers: PostgreSQL Supabase, Neon, TimescaleDB (PostgreSQL family) MySQL / MariaDB SQL Server (incl. Windows authentication: NTLM and Kerberos) SQLite DuckDB MongoDB (with editor autocomplete and aggregation linting) Redis (with full key management) CockroachDB ClickHouse (HTTP/HTTPS, AST safety classification) Elasticsearch (multiple auth modes, dedicated search editor, SQL mode) OpenSearch (multiple auth modes, dedicated search editor, SQL mode) More engines are planned as the architecture evolves.

Question 9

Does it work with remote connections and SSH?

Accepted Answer

Yes. QoreDB supports: classic remote connections, SSH tunnels, different authentication modes depending on the databases. Connection security is a priority.

Question 10

On which systems is QoreDB available?

Accepted Answer

QoreDB is available on: macOS Windows Linux Builds are updated regularly.

Question 11

Is the project actively maintained?

Accepted Answer

Yes. QoreDB is in active development, with: frequent releases, structural refactors, a public roadmap, gradual opening to the community. The project has already passed its POC stage.

Question 12

Can I contribute to the project?

Accepted Answer

Yes, and it is encouraged. Possible contributions: user feedback, GitHub issues and discussions, improvement proposals, code and documentation. A community GitHub is being structured.

Question 13

How will the project be funded?

Accepted Answer

The targeted model is: sustainable open-source, self-funded, without dependence on a mandatory centralized cloud. Details will evolve with product adoption.

Question 14

Can I use QoreDB in a professional setting?

Accepted Answer

Yes. QoreDB is designed to be used: by solo developers, early startups, technical teams. Security, stability, and maintenance aspects are taken seriously.

Question 15

Where can I follow the project's evolution?

Accepted Answer

On the official website Via the public roadmap On LinkedIn (regular sharing of project progress) On GitHub

Question 16

How to join the beta or test QoreDB?

Accepted Answer

QoreDB is already available for download. You can: install it directly, join the beta via the site, share your feedback to influence the future of the project.

Question 17

Can I trust QoreDB in the long term?

Accepted Answer

QoreDB is designed as a long-term project, not an experiment. Technical, product, and open-source choices go in the direction of: sustainability, transparency, developer trust.

FAQ - QoreDB