Non-Goals

This page documents what Logstyx is intentionally not trying to do.

These are not missing features or items on a future roadmap. They are deliberate design decisions that protect Logstyx’s focus, simplicity, and philosophy.

Understanding these non-goals will help you decide whether Logstyx is the right tool for your use case—and help contributors align with the project’s direction.

Logstyx Is Not a Full Observability Platform

Logstyx does not aim to be an all-in-one observability solution.

It does not try to replace:

• Datadog
• New Relic
• OpenTelemetry-based stacks
• Full APM platforms

Specifically, Logstyx does not provide:

• Distributed tracing
• Spans or trace graphs
• Service maps
• End-to-end request tracing

There are excellent tools dedicated to observability. Logstyx focuses on developer-accessible logging, not complete system introspection.

Logstyx Does Not Prioritize Fuzzy or Full-Text Search

Logstyx intentionally avoids:

• Partial string matching
• Fuzzy search
• Regex-heavy query engines

This is a conscious trade-off.

Logstyx uses hashed indexing to:

• Reduce exposure of raw log values
• Improve privacy guarantees
• Keep infrastructure and operational complexity low

Exact-match queries are a feature, not a limitation. If deep text analytics is your primary requirement, Logstyx is likely not the right tool.

Logstyx Is Not a Managed SaaS

Logstyx will not be offered as:

• A hosted SaaS platform
• A usage-based, per-GB service
• A closed-source managed product

Self-hosting is a core principle. Logstyx is designed for teams that want:

• Full data ownership
• Control over infrastructure and access
• Predictable costs

If you prefer zero-maintenance managed services, a SaaS logging provider may be a better fit.

Logstyx Is Not Cloud-Provider-Native

Logstyx intentionally avoids tight coupling with any cloud provider.

It does not depend on:

• AWS CloudWatch or AWS Secrets Manager
• Google Cloud Logging
• Azure Monitor
• Cloud-specific IAM or dashboards

Instead, Logstyx uses portable, open-source components that behave the same everywhere Docker runs.

This design favors portability and long-term flexibility over deep cloud-native integrations.

Logstyx Is Not Kubernetes-First

While Logstyx can run in Kubernetes, it is not built exclusively for Kubernetes environments.

It does not assume:

• Kubernetes-native logging pipelines
• Cluster-level agents
• Kubernetes-specific metadata as a requirement

Logstyx is designed to work just as well on:

• Virtual machines
• VPS providers
• Bare metal servers
• Hybrid or mixed environments

Logstyx Does Not Aim to Replace ELK Feature-for-Feature

Logstyx is not a lighter reimplementation of ELK.

It does not attempt to match:

• Elasticsearch’s full-text capabilities
• Complex aggregation DSLs
• Large-scale analytics workloads

Instead, Logstyx prioritizes:

• Simplicity
• Lower operational overhead
• Clear mental models for developers

Logstyx Does Not Perform AI or ML Log Analysis

Logstyx does not include:

• Anomaly detection
• Machine learning-based insights
• AI-driven log summarization
• Automated root-cause analysis

These features add significant complexity, opaque behavior, and often require external data processing.

Logstyx favors transparency and predictability over automation-heavy analytics.

Metrics Are Intentionally Separate

Metrics collection is not part of Logstyx’s core responsibility.

The related project Probestyx exists as:

• An optional
• Experimental
• Standalone metrics-gathering agent

Logstyx does not require metrics to function, and metrics are not a prerequisite for using the platform.

This separation is intentional to keep Logstyx focused on logging and developer access.

A Focused Tool by Design

Logstyx exists to solve a specific problem:

Allow developers to safely and easily view logs from deployed applications—without SSH access, cloud dashboard sharing, or SaaS lock-in.

Anything that compromises this goal—by increasing operational burden, cost, or cognitive load—is intentionally out of scope.

If these non-goals align with your expectations, Logstyx is likely a good fit. If not, there are many excellent tools built for broader or different use cases.