HeliosDB Full is an enterprise database server that serves PostgreSQL, MySQL, Oracle and Redis clients plus an HTTP gateway in one process; MongoDB, Cassandra and SQL Server compatibility is planned. Its HTTP gateway serves vector stores with hybrid search, embeddings and agent memory; in-database model training, Raft clustering, multi-region replication and sharding are planned. Licensed SSPL-1.0 and provided to licensed customers during onboarding; current source release v8.3.0.
Last updated
HeliosDB Full unifies transactional databases (PostgreSQL, MySQL, Oracle 23ai with 20 DBMS_* packages, SQL Server, IBM Db2), caching and queues (Redis with Lua 5.1 & BullMQ), wide-column and document stores (Cassandra, MongoDB), analytical warehouses (ClickHouse, Snowflake, Databricks Iceberg/Delta), and vector search (Pinecone, REST, GraphQL) in one self-healing engine.
Explore how Autonomous Self-Healing Storage, CKKS Homomorphic Encryption, 50-100x Tenant Hibernation, 14-Protocol Wire Multiplexing, and Merkle Audit Lineage work interactively.
The HeliosDB edition for enterprise workloads. HeliosDB Full serves the PostgreSQL wire protocol and an HTTP gateway on the shared HeliosDB SQL core, with opt-in MySQL, Oracle and Redis listeners (MongoDB, Cassandra and SQL Server compatibility is planned); the gateway serves vector stores with hybrid search, embeddings, chat completions and agent memory. In-database model training and quantum-inspired optimization are planned. HeliosDB Full runs as a single server today: Raft clustering, multi-region replication and sharding are planned, and GPU acceleration (NVIDIA CUDA) is available in HeliosDB Full builds on request and is not enabled in the public release build.
-- Multi-protocol: PostgreSQL, MySQL,
-- Oracle, Redis + HTTP;
-- Mongo, Cassandra, SQL Server: planned
-- PostgreSQL, MySQL, Oracle and HTTP
-- read and write the same tables
SELECT region, SUM(revenue)
FROM sales
GROUP BY region;Ships an AGENTS.md aggregate plus a .claude/skills/ catalogue. Every CLI flag, REPL meta-command and public API indexed for LLM coding agents. Read the guide →
# source provided during onboarding
cargo install --path ./heliosdb-full
bash scripts/install-skills.shHeliosDB Full offers hybrid search through its HTTP vector-store API. In-database machine learning, graph traversal and hybrid search as SQL functions, Graph-RAG, Code-Graph and a native MCP server are planned for Full; Code-Graph, Graph-RAG and the MCP server ship in HeliosDB Nano today.
Combine full-text and vector search with POST /api/v1/vectors/stores/{store}/search/hybrid on the HTTP gateway.
graph_traverse()Graph traversal and shortest-path search as SQL table functions, and hybrid search as a SQL function, are planned.
A native MCP server for HeliosDB Full is planned. HeliosDB Nano ships one today as a build-from-source feature.
Model training in SQL, anomaly detection, time-series forecasting and a model registry are planned for HeliosDB Full. The HTTP gateway serves embeddings, chat completions and agent memory today.
Full adds MySQL, Oracle and Redis listeners next to PostgreSQL and an HTTP gateway with vector stores, embeddings and agent memory; MongoDB, Cassandra and SQL Server compatibility is planned. HeliosDB Full runs as a single server today; Raft clustering, multi-region replication and sharding are planned, and GPU acceleration (NVIDIA CUDA) is available in HeliosDB Full builds on request and is not enabled in the public release build. Nano and Lite run time-travel queries (AS OF) and Git-like branches; for HeliosDB Full both are planned (the current release accepts the syntax but does not read historical snapshots or create branches), and so are in-database model training, SSO, LDAP and attribute-based access control (edition comparison).
HeliosDB Full serves PostgreSQL, MySQL, Oracle and Redis clients plus an HTTP gateway. The PostgreSQL listener and the HTTP gateway are on by default; the others are switched on with a startup flag (protocol hub). Each database engine below carries its status in the Release and Capability Matrix: Available, Available with limitations, In preview (included in the edition and usable for evaluation, but not yet verified by HeliosDB on any version, and not supported) or Planned. Each status is the best result that HeliosDB's tests or its own production use show on any version or build of HeliosDB Full, so it names no release and does not mean that every version was tested (status summary); the statuses come from a draft of the matrix, which is informational until HeliosDB publishes a frozen version (Release and Capability Matrix terms, clause 7.1). Driver compatibility does not imply complete feature parity with the original database engine, or compatibility with every application, extension or administrative tool.
POST /api/v1/query) today# PostgreSQL and the HTTP gateway are on by default;
# the other listeners are opt-in at startup
# (listeners bind 127.0.0.1 unless told otherwise)
heliosdb-full --data-dir /var/lib/heliosdb \
--bind-addr 10.0.0.12 --allow-external \
--enable-mysql --enable-oracle --enable-redis
# Connect via PostgreSQL
psql -h 10.0.0.12 -p 5432 -d mydb
# Connect via MySQL
mysql -h 10.0.0.12 -P 3306 -u postgres
# Connect via Redis (AUTH with a role name;
# the password is not verified yet)
redis-cli -h 10.0.0.12 -p 6379 --user app --pass unused
# PostgreSQL and MySQL read and write the same tablesNot in the current release. HeliosDB Full runs as a single server today; Raft clustering, multi-region replication and sharding are planned.
Not in the current release. HeliosDB Full serves vector stores with hybrid search, embeddings, chat completions and agent memory over its HTTP gateway; in-database model training in SQL, the neural query planner, anomaly detection and forecasting, NL-to-SQL, quantum-inspired optimization, and SQL vector indexes with Product Quantization are planned.
Quantum-inspired query optimization (QAOA, VQE and Grover-inspired search) is a research item for HeliosDB Full. It is planned and not part of the current release build.
GPU acceleration (NVIDIA CUDA) is available in HeliosDB Full builds on request and is not enabled in the public release build; contact HeliosDB sales. The CUDA work covers hash joins, group-by aggregation, sorting and vector similarity search. AMD ROCm support is planned.
Pattern recognition and anomaly detection with spiking neural networks on Intel Loihi 2 neuromorphic processors is a research item for HeliosDB Full. It is planned and not part of the current release build.
HeliosDB Full authenticates PostgreSQL clients with SCRAM-SHA-256; SQL GRANT/REVOKE enforcement, row-level security, encryption at rest with key rotation and cloud KMS, ABAC, SAML/OIDC single sign-on and LDAP are planned. A compliance framework for SOC 2, HIPAA, GDPR and PCI-DSS, blockchain-backed audit trails and post-quantum cryptography are planned too. HeliosDB Full listeners do not terminate TLS yet; put a TLS-terminating proxy in front, and native PostgreSQL TLS (with post-quantum key exchange preferred) is planned for the next release.
Yes. Licensed customers build HeliosDB Full from source with compile-time features (73 in the current server), leaving out components they do not use or adding research features. Custom binary sizes range from about 60 MB to 200 MB (internal builds, approx.).
Genomics sequence storage and alignment, blockchain-CRDT synchronization, holographic 3D visualization and multimodal storage for text, images, audio and video are research items for HeliosDB Full. They are planned and not part of the current release build. Graph-RAG is planned for Full too; it ships in HeliosDB Nano today.
HeliosDB Full is an enterprise database server that serves several database wire protocols, plus an HTTP gateway with vector stores, embeddings and agent memory, from one engine. HeliosDB Full runs as a single server today; Raft clustering, multi-region replication and sharding are planned, and so are in-database model training and enterprise access control (SSO, LDAP, ABAC). It is licensed SSPL-1.0 and provided to licensed customers during onboarding (edition comparison).
One HeliosDB Full server serves PostgreSQL, MySQL, Oracle and Redis clients plus an HTTP gateway; PostgreSQL and the HTTP gateway are on by default and the others are enabled with startup flags. In the Release and Capability Matrix, where each status is the best result on any version of HeliosDB Full, PostgreSQL, MySQL and Oracle are Available with limitations, Redis is In preview, and MongoDB, Cassandra and SQL Server are Planned. The PostgreSQL, MySQL and Oracle listeners and the HTTP gateway read and write the shared tables (protocol hub).
Use a PostgreSQL driver such as psycopg, pgx, node-postgres, JDBC or libpq: the PostgreSQL wire protocol is the primary interface. HeliosDB Full listeners do not terminate TLS yet, so put a TLS-terminating proxy in front; native PostgreSQL TLS is planned for the next release. Full has no gRPC client API, and the REST clients in the HeliosDB SDKs target Nano and Lite, not Full (FAQ).
No, not yet. MongoDB compatibility for HeliosDB Full is Planned in the Release and Capability Matrix: reading and writing HeliosDB tables over the MongoDB protocol, GridFS and capped collections are on the roadmap. Use the PostgreSQL interface for data access today (compatibility notes).
Yes, by default. A write is fsync-durable when the client receives the acknowledgement, and concurrent writers share one flush through group commit. An opt-in fast mode acknowledges before the flush and bounds the possible loss to the write-ahead log flush interval (release notes).
No. HeliosDB Full runs as a single server today and serves clients directly; its own clustering and failover are planned. You can put HeliosProxy, the separate Apache 2.0 proxy, in front of Full when you want its pooling, failover, policy or observability features.
HeliosDB Full is source-available under SSPL-1.0, with a commercial license for terms other than SSPL. Pricing is custom on an annual contract through HeliosDB sales, and binaries, container images and Helm charts are provided during onboarding rather than through public registries (pricing).
HeliosDB Full authenticates PostgreSQL clients with SCRAM-SHA-256; SQL GRANT/REVOKE enforcement, row-level security, encryption at rest with key rotation and cloud KMS, ABAC, SAML/OIDC single sign-on and LDAP are planned. HeliosDB Full listeners do not terminate TLS yet, and native PostgreSQL TLS is planned for the next release. The MySQL and Redis listeners do not verify passwords yet.
Use HeliosDB Full when one licensed server must serve several database protocols; enterprise access control (SSO, LDAP, ABAC), multi-region replication and Raft clustering are planned.
PostgreSQL, MySQL, Oracle and Redis clients plus an HTTP gateway in one server. ABAC, SSO, LDAP and a SOC 2/HIPAA/GDPR compliance framework are planned.
Raft clustering across regions with configurable consistency levels, automatic failover and geo-aware routing is planned; HeliosDB Full runs as a single server today.
Compliance automation, blockchain-backed audit trails, data-sovereignty controls and post-quantum cryptography for healthcare, finance and government are planned for HeliosDB Full.
GPU acceleration (NVIDIA CUDA) in HeliosDB Full builds on request; quantum-inspired optimization, genomics, holographic visualization and neuromorphic computing are research items on the roadmap.
Contact our sales team to discuss enterprise licensing and deployment for HeliosDB Full.
Commercial licences of HeliosDB Full are granted under the Customer Terms, which include the Transaction Durability Commitment: an acknowledged commit is not lost because HeliosProxy is in the path, whether or not you configured it, or because of the HeliosDB Full version in use, including documented upgrades, from the first Generally Released HeliosDB Full version designated in the Release and Capability Matrix (none is designated yet), with the durability settings the documentation will state. Support is best effort under the Support Policy.