OakMQ is a lean, hardened message broker supporting OpenWire and STOMP. OakMQ is not affiliated with Apache ActiveMQ.
NOTE: OakMQ is under development and is non-functional at this time. Use at your own risk.
Remove optional modules, protocols, examples, web consoles, and unused dependencies.
Provide reliable interoperability for existing OpenWire and STOMP clients.
Require authentication, disable unsafe defaults, minimize exposed services, and use modern TLS configuration.
Include only the components necessary to operate the broker.
Support hardened deployments, Iron Bank submission requirements, STIG-aligned configuration, and documented security controls.
Maintain a complete software bill of materials (SBOM), dependency inventory, license report, and vulnerability record.
Produce traceable artifacts from pinned source code and dependencies using a repeatable build process.
Publish a non-root OCI image containing only the runtime and required OakMQ components.
Run static analysis, dependency scanning, container scanning, secret detection, and automated tests in CI.
Preserve durable queues, topics, acknowledgements, transactions, persistence, redelivery, and dead-letter handling.
Make configuration, deployment, monitoring, backup, and upgrades straightforward.
Provide health checks, structured logs, metrics, and audit-relevant events without requiring a web console.
Avoid unnecessary protocol changes and clearly document compatibility with supported Apache ActiveMQ client versions.
Establish repeatable benchmarks for startup time, memory consumption, latency, and throughput.
Track Apache ActiveMQ security fixes, preserve license and attribution requirements, and contribute generally useful fixes upstream when practical.
Operate as an independent Apache-licensed project without implying endorsement by the Apache Software Foundation.
OakMQ is an independent project derived from Apache ActiveMQ. It is not affiliated with or endorsed by the Apache Software Foundation.