Overview
FerroDruid is a Rust-native, Apache-Druid-spec-compatible real-time OLAP database. It speaks the Druid REST API, native query JSON, and Druid SQL, and it reads and writes Druid segment v9/v10 binary files - without a JVM, without ZooKeeper, and without a six-process control plane to operate. A classic Apache Druid cluster needs six or more JVM processes plus ZooKeeper plus an external metadata database, and 16 GB or more of RAM, before it serves a single query. FerroDruid's single-binary mode replaces all of that with one process that starts in under a second, uses under 200 MB of RAM, and ships as a self-contained AMI. What FerroDruid does today (v0.2.0): it serves all eight Druid native query types (timeseries, topN, groupBy, scan, search, segmentMetadata, dataSourceMetadata, timeBoundary); it runs Druid SQL with SELECT, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, more than 30 functions, EXPLAIN PLAN FOR, and an MSQ task endpoint (core SQL parity approximately 95 percent); it exposes more than 40 Druid-compatible REST endpoints; it reads and writes Druid segment v9/v10 (the supported single-binary path uses SQLite metadata plus local-filesystem deep storage); it ingests from Kafka and Kinesis supervisors and via native batch; and it enforces Basic authentication (Argon2id) with role-based access control on by default and TLS via rustls. Admin password security: on first boot the AMI generates a NEW RANDOM admin password UNIQUE to that instance (never a default or shared password) and writes it once to the instance system log. The admin account is flagged must-change, so EVERY API endpoint returns HTTP 403 until the operator rotates the password by POSTing a new one to /druid-ext/basic-security/authentication/db/basic/users/admin/credential; the rotated credential is persisted and survives restarts. This enforces a password change on first login. Engineering posture: every crate uses forbid(unsafe_code), clippy is clean at -D warnings, a CycloneDX SBOM and 18 fuzz targets run in CI. Live wire deep-match is 5 of 5 against Apache Druid 30.0.1 and 5 of 5 with an Apache Superset connector. Honest scope: live validation is against Apache Druid 30.0.1 and single-binary mode; Druid 31 through 36 is a spec-driven design target not yet cross-validated against a running cluster; multi-node topologies fail closed by default. This listing sells a hardened, scanned, supported distribution built from the Apache-2.0 source at a pinned release version; the code itself remains Apache-2.0. The AMI is metered automatically by AWS per running instance-hour, with no metering code in the product.
Highlights
- One binary, not six JVMs: FerroDruid needs no ZooKeeper and no external metadata database in single-binary mode, and it boots in under a second on under 200 MB of RAM.
- Druid wire-compatible: FerroDruid speaks the Druid REST API, native query JSON, and Druid SQL, and reads and writes segment v9/v10; it was live deep-matched 5 of 5 against Apache Druid 30.0.1 and 5 of 5 with an Apache Superset connector.
- Hardened and supported: forbid(unsafe_code) workspace-wide, clippy clean at -D warnings, a CycloneDX SBOM and 18 fuzz targets in CI, a random per-instance admin password that must be changed on first login, and a paid support SLA.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/hour |
|---|---|
c7g.xlarge Recommended | $0.10 |
t4g.medium | $0.03 |
c7g.4xlarge | $0.20 |
c7g.2xlarge | $0.15 |
m7g.xlarge | $0.10 |
t4g.large | $0.05 |
c7g.medium | $0.03 |
r7g.large | $0.05 |
m7g.large | $0.05 |
c7g.large | $0.05 |
Vendor refund policy
FerroDruid software charges are metered by AWS Marketplace; stop or terminate the EC2 instances running the AMI to stop all charges (you pay only for instance-hours run). Already-incurred usage is generally non-refundable. If billed in error or a defect prevented normal use, contact aws-support@abyo.net within 30 days and we will review; warranted refunds are processed through AWS Marketplace.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (Arm) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
FerroDruid v0.2.0. Rust-native, Apache-Druid-spec-compatible real-time OLAP. Single-binary mode runs one process - no JVM, no ZooKeeper, no external metadata database - that boots in under a second on under 200 MB of RAM. Speaks the Druid REST API, native query JSON, and Druid SQL, and reads/writes Druid segment v9/v10. 8/8 native query types; 40+ Druid-compatible REST endpoints; approximately 95 percent core Druid SQL parity; Kafka and Kinesis supervisors plus native batch; Basic auth (Argon2id) with RBAC on by default and TLS via rustls. Live wire deep-match 5/5 against Apache Druid 30.0.1 and 5/5 with an Apache Superset connector. Honest scope: live validation is against Druid 30.0.1 and single-binary mode; Druid 31-36 is a spec-driven design target not yet cross-validated against a running cluster; multi-node topologies fail closed by default. Metered automatically by AWS per instance-hour (no metering code).
Additional details
Usage instructions
Launch the self-contained FerroDruid AMI on EC2 (Graviton/arm64) with the provided CloudFormation template (marketplace/cloudformation/ami.yaml) behind an Application Load Balancer; terminate TLS at the ALB and do not expose the service port directly to the internet. The instance boots one process (single-binary mode) with SQLite metadata and local-filesystem deep storage; Basic auth (Argon2id) plus RBAC are on by default and a one-time admin password is written to the instance logs on first boot. Point your Druid clients (REST API, native query JSON, Druid SQL, or an Apache Superset connector) at the load balancer endpoint. The supported topology is single-binary single-node; multi-node configurations fail closed by default. See docs/KNOWN_LIMITATIONS.md.
Support
Vendor support
Support for FerroDruid is provided by abyo software LLC. Email aws-support@abyo.net for support; we respond under the published SLA.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.