How It Works

Logstyx is a self-hosted logging platform that collects, stores, and displays logs from your applications.

Basic Flow

Your App (with SDK) → Logstyx Server → Database → Dashboard

1. Your Application Sends Logs

Install an SDK in your app and send logs:

logger.info({ message: 'User logged in', userId: '123' });
logger.error({ message: 'Payment failed', error: err.message });

2. Logstyx Receives & Stores

The server:

• Authenticates your request via API key
• Encrypts sensitive data
• Stores the log in MongoDB
• Caches recent logs in Redis for fast access

3. View in Dashboard

Access the web dashboard to:

• Search and filter logs
• View log details
• Monitor your applications

Key Features

Encryption

All sensitive log data is encrypted before storage using AES-256. Only you can decrypt your logs with your encryption key.

Hashed Indexing

Log indices are hashed (SHA-256) for:

• Fast exact-match queries
• Privacy protection
• Consistent performance

Trade-off: No partial text search or fuzzy matching. You need exact values to search.

Self-Hosted

You run Logstyx on your infrastructure:

• Full control over your data
• No third-party access
• No per-GB pricing
• Deploy anywhere (Docker, VPS, cloud)

Architecture Overview

Logstyx uses a microservices architecture:

• Gateway - Entry point for all requests
• Auth Service - Handles authentication
• Core Service - Processes and stores logs
• Cache Service - Fast access to recent logs
• Utility Service - Webhooks, alert & scheduling
• Frontend - Web dashboard

All services communicate internally and are deployed together via Docker Compose.

Data Storage

MongoDB - Primary database for all logs

Redis - Cache layer for:

• Cached Data

RabbitMQ - Message queue for:

• Async processing
• Service communication

Security

• At Rest: AES-256 encryption for sensitive data
• In Transit: TLS for all external connections
• Authentication: HMAC signatures (server) or JWT (dasboard)
• Keys: You control all encryption keys

What Makes It Different

Privacy First

• Your data never leaves your infrastructure
• Encryption at rest by default
• Hashed indexing enables full search and custom reporting while keeping sensitive values protected

Cost Effective

• No per-GB pricing or vendor lock-in
• Predictable costs with self-hosted deployment
• Scale horizontally on your own terms

Simple to Deploy

• One-command installation via install.sh
• Docker Compose handles all the infrastructure
• Connect to external MongoDB/Redis or use bundled services

Limitations

No Partial Search

Due to hashed indexing, you cannot:

• Search for partial text matches
• Use wildcards in queries
• Do fuzzy matching

You need exact values to search.

Example:

// ✅ Works
search: { userId: "user-123" }

// ❌ Doesn't work  
search: { userId: "user-*" }
search: { message: "contains:error" }

When to Use Logstyx:

• Privacy is critical
• Exact match queries are sufficient
• You want self-hosted solution
• Cost control matters

When to Consider Alternatives:

• You need full-text search
• Fuzzy matching is required
• You prefer managed services
• You need advanced APM features