Disclaimer

Last updated: 2026

SpectraGQL is an open-source, community-driven wire-speed API gateway and event-driven appliance distributed free of charge under the permissive MIT License.

1. Zero Liability & “As Is” Warranty Disclaimer

SpectraGQL, including all associated binaries, documentation, benchmarks, CLI utilities, and architectural blueprints, is provided on an “AS IS” and “AS AVAILABLE” basis without warranty of any kind, whether express, implied, statutory, or otherwise.

To the maximum extent permitted under applicable law:

• Zero Financial or Legal Liability: In no event shall the authors, maintainers, contributors, or copyright holders be liable for any direct, indirect, incidental, special, exemplary, punitive, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption).
• Theory of Liability: This limitation applies regardless of the cause of action, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use, deployment, or inability to use this software, even if advised of the possibility of such damage.

2. Distributed Architecture & Operational Responsibility

SpectraGQL operates as a dual-path CQRS edge appliance, terminating GraphQL mutations and dispatching un-materialized command envelopes directly into streaming event brokers (e.g. NATS JetStream, Apache Kafka, Apache Iggy, SierraDB, and Valkey Streams).

When deploying SpectraGQL into production environments:

• Infrastructure Sizing & Partitioning: Operators assume sole and complete responsibility for properly configuring broker cluster topologies, partition keys, compaction policies, consumer group subscriptions, and persistence limits.
• Consumer Lag & Dead-Letter Handling: Downstream mutation write workers (BYOW) consume events asynchronously. Operators are responsible for monitoring broker queue depth, worker dead-letter queues (DLQ), idempotency keys, and reconciliation pipelines.
• Network Partitions & Split-Brain: The authors make no representations regarding cluster behavior during physical network partitions, cloud provider regional outages, or upstream socket exhaustion.

3. Security, Authentication & Deployment Governance

SpectraGQL includes built-in security interceptors (such as DeployAuthInterceptor, token guards, CEL policy filters, and SSRF loopback protections). However:

• Network Edge Isolation: Operators are solely responsible for enforcing network perimeter security, TLS termination, API gateway rate limits, and egress firewall rules.
• Secret Management: Operators must securely manage deployment tokens (SPECTRA_DEPLOY_TOKEN), broker credentials, and cluster certificates adhering to 12-factor infrastructure standards.
• Vulnerability Reporting: If you discover a potential security flaw, please review the security guidelines in the SpectraGQL GitHub repository.

4. No Professional Support Commitment

SpectraGQL is maintained by open-source contributors. Publication of the code does not constitute a commitment to provide technical support, service-level agreements (SLAs), backward compatibility guarantees, or real-time hotfix distribution.