Kindling vs Metoro Kubernetes Profiling

Kindling is a free desktop writing app for fiction writers who plan their stories while drafting. Its writing view can show scene beats as expandable prompts, or switch to a full-page prose editor. Tagged characters and locations appear in a reference panel with descriptions, notes, and custom fields. Projects import from Plottr, Scrivener, yWriter, Obsidian Longform, novelWriter, and Markdown, then export to DOCX, EPUB, HTML, plain text, Markdown, Scrivener, Longform, and novelWriter. Editorial review uses a .kindling-review file containing tracked suggestions and threaded comments; feedback can be imported and changes accepted or rejected. Screenplay projects add slugline entry, page-count estimates, and one-page or five-page DOCX treatments. Data stays in local SQLite files, with no account, analytics, telemetry, or usage tracking required. Writing and review work offline. Kindling is open source under MIT, does not use AI to analyze writing, and runs on Windows 10+, macOS 12+, and x86_64 Linux.

Metoro Kubernetes Profiling continuously profiles Kubernetes workloads with an eBPF sampler running at the kernel level. It creates interactive flame graphs that can be grouped by service, pod, or container and filtered by cluster, namespace, deployment, or Kubernetes label. Metoro lists Go, Python, C++, C, Rust, Node.js, and Java support, with host-level frames for other runtimes. Profiling does not require SDKs, code changes, language agents, restarts, or rebuilds, and can cover third-party containers and vendor workloads. Profiles connect to Metoro APM traces, logs, metrics, pod state, and deployment context. Installation uses Helm, with Cloud, BYOC, and on-premises deployment options. The free Hobby plan includes one cluster, one user, and two nodes with 28-day retention. Scale costs $20 USD per node per month, plus $0.20 per GB above 100GB per node. Enterprise pricing is contract-based and offers custom retention and SLAs. eBPF requires Linux kernel 4.18 or newer.