Zero-Dependency • Zero-Port Log Vault • Node.js & Laravel 13
Star on GitHub

The Self-Hosted Telemetry & Log Vault with Zero Extra Ports & Zero Bloat

Real-time telemetry flight recorder, hardware AES-256-GCM encrypted log vault, embedded web console, and automatic SQLite-to-MySQL migration. Never lose terminal logs on restart, never open extra attack vectors.

Daily Downloads
Loading...
Live NPM Registry
Weekly Downloads
Loading...
Active Telemetry
Monthly Downloads
Loading...
Verified Production
NPM Package Version
Loading...
Dynamic Release
Quick Install • Standard Node.js & Express / Laravel
$ npm install tracernest-logger
Telemetry Console Simulator

Live Log Streaming & Payload Inspector

Experience the TracerNest dashboard directly in your browser. Filter real-time logs, execute regex queries, inspect HTTP request/response payloads, and test hardware AES-256-GCM decryption.

LIVE STREAMING
Total Logs: 0
Timestamp
Level
Status
Method / Route
Message & Telemetry
Inspect
Engineered for Performance & Privacy

Enterprise Architecture Built Into a Single Package

Every feature in TracerNest was engineered from the ground up to solve the real flaws of existing Node.js & Laravel logging tools.

Zero Extra Ports

Traditional tools force you to open separate ingress ports, exposing new attack surfaces and complicating Kubernetes deployments. TracerNest mounts directly onto your host router.

  • No firewall modifications required
  • Works behind existing SSL & domain reverse proxies
  • Mounts on Express, Koa, Fastify & Laravel 13

Zero Runtime Dependencies

Supply chain attacks via transitive dependencies are the #1 vulnerability vector in modern npm packages. TracerNest has exactly dependencies: {}.

  • 100% native Node.js standard library
  • No Dependabot or CVE audit alerts
  • Lightweight ~15MB footprint vs ~60MB+ bloat

AES-256-GCM Payload Encryption

Never store user passwords, authorization tokens, or sensitive medical/financial data in plaintext logs. Every payload is encrypted at rest using hardware-accelerated AES-256-GCM.

  • Master key never hardcoded in repository
  • Tamper-proof 128-bit authentication tag verification
  • HIPAA & GDPR compliance ready

SQLite to MySQL Auto-Migration

Start instantly in local development with embedded SQLite. When scaling to production, simply pass your MySQL connection string — TracerNest automatically migrates your schema and data.

  • Zero-downtime automated column schema drift DDL
  • Automatic safe cleanup of SQLite files
  • Strict preservation of your .master.key

Persistent Logs Until TTL Completion

Most embedded loggers lose in-memory logs whenever your server restarts or Docker spins up a fresh container. TracerNest writes directly to disk/DB with configurable TTL cleanup.

  • Logs survive unexpected container crashes
  • Configurable TTL (7, 14, 30, 90 days)
  • Zero memory leaks under high-throughput spikes

Laravel 13 PHP Bridge

TracerNest isn't restricted to Node.js. It features a native Laravel 13 PHP middleware and controller bridge, enabling unified telemetry across your entire polyglot backend stack.

  • Zero-port Laravel route integration
  • Captures PHP exceptions, request headers & DB queries
  • Unified single-pane-of-glass dashboard
Deep Technical Breakdown

Why TracerNest Outclasses Legacy Loggers

See how TracerNest compares side-by-side against Errsole, traditional logging libraries (Winston/Pino), and expensive cloud SaaS platforms (Datadog/Sentry).

Feature / Capability TracerNest Errsole Winston / Pino / Morgan Datadog / Sentry (SaaS)
External Monitoring Port Required? Zero Extra Ports (Host Mount) Yes (Separate TCP Port) N/A (No Web Console) Cloud Egress (Port 443 Outbound)
Runtime Dependencies 0 Dependencies (Empty Object) ~45+ Transitive Dependencies 5 – 15 Dependencies Heavy Agent Daemons
Hardware AES-256-GCM Encryption Built-in Hardware Encryption Plaintext Storage Only Plaintext Only Encrypted by Vendor (External Cloud)
SQLite to MySQL Auto-Migration Automatic Zero-Downtime Migration Manual Setup Required None Proprietary Cloud DB
Crash Telemetry & Flight Recorder Pre-Crash Context Capture Partial Logs Lost on Uncaught Crash Sentry Breadcrumbs
Persistent Across Restarts (TTL) Persistent in DB until TTL Partial (In-memory buffer risk) File log rotation only Cloud retention limits
Multi-Framework (Node & Laravel 13) Express, Koa, Fastify & Laravel Node.js Only Node.js Only Multiple SDKs required
Estimated Monthly Cost $0 / month (100% Free & Self-Hosted) $0 / month (Self-hosted) $0 / month (No UI) $250 – $2,500+ / month
Supply Chain Security Risk Zero (No external packages) Moderate (Express, SQLite3, etc.) Low to Moderate Closed Source Binary

Why Zero Extra Ports Matter

When running in Kubernetes, Docker Swarm, or AWS ECS, every exposed port requires another target group, security group ingress rule, ALB path routing rule, and firewall punch. TracerNest eliminates this complexity completely by attaching to your existing HTTP server handler.

True Zero-Dependency Security

Every additional npm dependency introduces attack vectors like malicious sub-dependency takeovers or silent CVEs. TracerNest's HTTP router, crypto suite, template engine, and storage adapters are written purely using Node.js built-ins, keeping your audit clean.

Zero Egress Cloud Data Privacy

Datadog and Sentry require streaming sensitive user data to external third-party cloud servers, posing significant compliance hurdles under GDPR, HIPAA, and SOC2. With TracerNest, your telemetry data never leaves your infrastructure.

Open Source Community

Project Contributors

TracerNest is maintained by Ankit Khandelwal and powered by open-source engineers around the world. Every commit, feature request, and storage driver refinement pushes self-hosted observability forward.

Ankit Khandelwal ★

Ankit Khandelwal

Creator & Lead Maintainer Lead Architect
@ankit-kumar-khandelwal
Open Source & Developer First

How to Contribute to TracerNest

We welcome contributions from engineers worldwide! Follow our four-step workflow to get started on bug fixes, UI enhancements, or new storage drivers.

01 PHASE 1

Fork & Clone Repository

Fork the repository on GitHub and clone your local copy:

git clone https://github.com/ankit-kumar-khandelwal/tracernest-logger.git
cd tracernest-logger
02 PHASE 2

Zero Dependency Policy

Crucial Rule: TracerNest maintains a strict dependencies: {} policy. Any PR introducing a runtime dependency in package.json will be automatically rejected. Use native Node.js standard libraries.

03 PHASE 3

Run Comprehensive Test Suite

Ensure that all 33+ unit and integration tests pass cleanly before submitting code:

npm test
npm run build
04 PHASE 4

Submit Your Pull Request

Create a descriptive feature branch (e.g. feat/postgres-adapter), commit your changes using conventional commits, and open a PR against main on GitHub.

Ready to build the future of zero-overhead observability?

Join the discussion, report issues, or star the project on GitHub.

Got Questions?

Frequently Asked Questions

How does TracerNest achieve zero extra ports?

TracerNest attaches directly to your application's existing HTTP request pipeline (Express, Koa, Fastify, or Laravel). When a request hits your configured dashboard path (e.g. /tracernest), TracerNest serves the embedded dashboard and API directly over the existing port, eliminating the need for firewall changes or port conflicts.

Is TracerNest truly zero-dependency?

Yes! Check package.json: the dependencies object is strictly empty ({}). All cryptography, HTTP routing, file operations, and database interactions use native Node.js standard libraries and built-in SQLite engines, protecting your applications from supply-chain attacks.

How are logs kept persistent across container restarts?

TracerNest writes logs straight to persistent database storage (SQLite files or MySQL tables) instead of keeping them purely in process RAM. Even if your server crashes or your container restarts, all logs remain intact until your configured TTL (Time-To-Live) cycle safely cleans them up.

How does the SQLite to MySQL migration work?

When you update your initialization configuration to target MySQL, TracerNest automatically inspects MySQL for required tables and columns. It applies missing column DDL via ALTER TABLE ... ADD COLUMN ..., migrates existing SQLite log records, and deletes obsolete SQLite files while strictly keeping your .master.key safe.

Get in Touch

Connect with the Maintainer

Have questions about enterprise deployment, custom storage adapters, or consulting? Reach out directly.