Skip to content
Dekglas

Logmarq

Release and supply-chain records

Tie code commits, artifacts, SBOMs, and VEX decisions to each release. Trace a CVE across maintained versions and recorded customer deployments without rebuilding the story from CI logs.

What Logmarq does

Record each release

Keep source commits, artifact digests, and changes together across repositories.

Track supply-chain evidence

Generate or upload SBOMs, scan vulnerabilities, and record VEX decisions. Export CycloneDX and OpenVEX.

Follow supported versions

Connect LTS release lines, deployment reports, and customer-response packages.

Prepare release notes

Draft internal notes from changes and curate a customer-facing version. Model-assisted drafting is optional.

One self-hosted image with SQLite or PostgreSQL. Run it on a release engineer’s laptop with persistent storage or as a shared service. Logmarq records reported deployments; it does not inspect runtime state, run CI, or replace your issue tracker.

Editions

Community

Start here for a single-app SaaS or lightweight local release ledger.

  • Planned for one active product, not one repository
  • Release records, notes, supply-chain evidence, and exports
  • Local use needs no public webhook endpoint

Business

Planned for up to five active products and richer LTS and customer coordination.

  • Maintained-release and deployment-map workflows
  • Customer-response coordination
  • Evaluation terms to be confirmed

The edition split is planned; no active-product limit is currently enforced. Paid prices and trials are not yet available.

Documentation and availability

Documentation covers the development build; check the release notes for your version.

Public downloads are not available yet. No release date has been announced.

Roadmap

  • Next: Simpler first-release setup and integration validation.
  • Before release: Validate LTS and customer-response workflows; finalize edition and trial terms.

Share a workflow, feature request, or product question. Your feedback helps us prioritize improvements.

Feedback

Please leave credentials, state files, and confidential customer data out of your message.