Spekra Features, Limitations and Pilot Readiness

Implemented workflows

Selected database/host telemetry, supported OTLP JSON traces/metrics, submitted application logs, saved dashboards, tenant-aware workspace search and shared incident investigations are implemented. Public HTTP/TLS probes record actual check evidence.

IncidentOps supports on-call schedules, generic HTTPS paging, assigned-responder acknowledgement, opt-in escalation, signing/callbacks and evidence/endpoint verification runbooks. A customer-operated receiver handles downstream notification delivery.

• Database & Infrastructure, APM, LogStream and Synthetics.
• Incident response coordination and supported evidence runbooks.
• Saved organization dashboards and purchase-aware bounded search.
• Reviewed pilot requests, suite approval and single-use invitations.

Partial suites and unavailable capabilities

FinOps accepts normalized billing JSON and exact costs; native provider synchronization, invoice reconciliation and cloud mutation are unavailable. SecOps reviews imported Docker configuration; CVE/image scanning, native cloud posture and compliance certification are unavailable.

Read-only PostgreSQL/MySQL schema comparison is implemented with documented exclusions. Production AI diagnosis, automatic DDL/infrastructure remediation, DDL dry-run validation and fabricated plans/topology are unavailable. Experimental synthetic suite models are inactive; the opt-in reviewed learning workflow remains advisory.

Pilot setup and customer responsibilities

Agree on one staging application, supported database and success measure. An operator reviews the request and selected suites. The customer sets a password through a 48-hour single-use invitation delivered manually. There is no automatic mailbox verification, payment processing or access suspension on the pilot end date.

Verify network paths, least-privilege database permissions, upstream redaction and encryption needs. Database-link TLS is not fully wired through current polling collector configuration. API keys can read some existing tenant GET routes, and feature gates are not uniform across every legacy/ingress endpoint. Review these requirements explicitly before a deployment commitment.

What the current testing establishes

Retained controlled real-data acceptance used sample tenants, Docker databases, host observations, actual instrumented requests, probes and a custom receiver. Six suites passed their recorded matrices; FinOps, SecOps and AI/schema remain partial. Later focused checks cover search, pilots and local release controls.

Local HTTPS/WSS, backup restoration and bounded process/load tests do not certify public hosting, sustained ingestion, universal isolation, independent security review or an availability SLA. Validate actual-host certificates, offsite recovery, workload limits and operational monitoring before public use.

Value to evaluate, not a guaranteed saving

Measure time spent gathering request/database context, checking on-call coverage and comparing supported schema evidence. Include installation, hosting and maintenance effort in the evaluation.

There is no verified fixed MTTR reduction, zero-overhead guarantee, universal PII sanitization, complete replacement of other monitoring vendors or certified financial saving. We can describe implemented controls and support a focused pilot rather than promise an unmeasured outcome.

Frequently asked questions

Evaluate your own workflow

Start with supported sample or staging infrastructure and agree on a success measure. Contact the operator to arrange a pilot. This static website does not create accounts or send invitations automatically.