Logmarq by Dekglas
SBOM + VEX and release coordination for software delivery.
Know what shipped. Explain what changed.
Answer release, support, and security questions from a maintained record of code, artifacts, changes, and vulnerability decisions. Your existing CI/CD pipeline still builds and deploys; Logmarq keeps the context you need afterward.
Free editions and trialsLogmarq is in development. No release date has been announced.
See the workflow
Planned walkthrough: Use a release record to answer what shipped, what changed, and which artifact and vulnerability decisions belong to that version.
Video not published yet. This placeholder is not a product screenshot or a playable demo.
What Logmarq does
For software vendors maintaining several supported versions, products, or customer deployments, and the release, support, or security owner responsible for explaining them.
Pin the release, not a moving branch
Record the source commit and declared artifacts for a version, including products that span repositories. Resolved artifact identities and unresolved references remain explicit, so a missing digest is not mistaken for verified provenance.
Turn changes into useful notes
Connect commits, pull requests, and tracker issues to the release diff. Prepare editable, versioned internal notes and a curated customer subset, manually or with optional model-assisted drafting.
Keep supply-chain decisions with the version
Generate or upload a software bill of materials (SBOM), scan for vulnerabilities, and record VEX decisions explaining whether a finding affects a component. Compare releases and export CycloneDX and OpenVEX records.
Keep the handoff visible
Track validation status and recorded deployments, export notes as Markdown or HTML, and optionally publish customer notes or a read-only release page. Deployment records report what was recorded; Logmarq does not deploy software.
How it works
Step 1
Describe one product
Connect your code host and issue tracker, then register the repositories and artifacts that make up a version. Keep the declaration alongside your code.
Step 2
Record after the build
Let CI, a supported webhook, or an explicit action record the version. Logmarq pins the source and resolves declared artifacts without creating the release itself.
Step 3
Review changes and findings
Compare the release with its predecessor, curate notes, and review SBOMs, vulnerability findings, and VEX decisions against the recorded artifacts.
Step 4
Answer the version question
Use the retained release context, export the appropriate outputs, and record deployment assertions with their source. Publishing a note or recording a deployment is not proof of live runtime state.
Where it runs and what to expect
Self-hosted as one application image, with an embedded SQLite database or your own PostgreSQL. Supported code-host and issue-tracker adapters connect the existing workflow; live acceptance varies by integration. An operated Cloud service is not part of the current offer.
Logmarq is a release ledger, not a CI runner, deployment engine, or issue tracker. It does not create or edit tickets. Source reads are distinct from explicitly enabled publication or branch-freeze actions. SBOM, scanning, and VEX workflows exist in the development build; supported-release and integration validation are still in progress.
Free editions, trials, and paid plans
Best for vendors maintaining multiple versions, products, or customer deployments. A single continuously deployed service may already have enough context in its code host and CI. Logmarq records releases; it does not run your deployment pipeline.
Community: one active product planned
The planned free edition covers one active product, which can include multiple repositories and artifact types. The release record, notes, and exports remain useful; repository count is not the proposed licensing unit.
Business: portfolio use planned
The planned paid edition covers up to five active products and adds release-portfolio coordination as those workflows become available. Final prices and commercial availability are TBD; no checkout is open for Logmarq.
Business evaluation: terms to be confirmed
A bounded evaluation of paid capabilities is planned. Its duration and eligibility are not finalized. Community is a separate free edition, not an expiring Business trial. Trial activation is not available on this page.
Start with one useful result
Evaluate one product and record a real release in an approved setup. Use the record to answer a release, support, or security question you would otherwise reconstruct across tools. A generated changelog alone is not the goal.
Why early feedback matters
Early-adopter rates, when offered, are a way to learn from real workflows. We want useful feedback and hope to earn paying customers as the products prove their value.
A free edition is a valid long-term choice where one is offered. Feedback is welcome, including what did not work; it is not a commitment to buy or provide a testimonial.
Any early-adopter offer will state its price, duration, and renewal terms before you choose it. No future discount or price lock is implied by sending feedback.
Share feedback or ask a questionNo sales call required. Please leave credentials and confidential customer data out of your message.
Plans and pricing
Community and Business describe the planned edition split, not an active commercial offer. Final prices and evaluation terms remain TBD. A supported release and tested commercial activation are required before purchasing is enabled.
Community
Free
Planned ongoing use for one active product, not one repository.
- A product can include multiple repositories and artifact types
- Release records, notes, and exports
- No per-release charge
- Edition availability is still in development
Business
TBD
Planned portfolio use for up to five active products.
- Cross-product coordination as its workflows become available
- Viewers are not separately charged
- Evaluation duration and final commercial terms: TBD
- No purchase or trial activation is open yet
What is planned next
Coordinate maintained releases
Planned: maintained-version views, sourced customer and environment deployment maps, and reviewed customer-response packages. These build on the existing release record rather than replacing your deployment system.
Make the edition boundary practical
Planned: one-active-product Community and up-to-five-active-product Business packaging, with a bounded paid-capability evaluation. Commercial terms and activation are not available yet. Historical access and exports remain part of the intended downgrade boundary.
Optional local inference with SeaKrait
Run SeaKrait as a separate container and configure its HTTP endpoint and selected model as a drafting source in Logmarq. Logmarq would collect and batch the release context, request internal or customer-facing wording, and retain provenance, editing, approval, and publication. SeaKrait supplies the model response; it does not collect release data or publish notes. Release-note factuality, coverage, and wording must be validated independently of chat compatibility.
This integration is planned, not a supported setup today. No SeaKrait model edition is qualified for this workflow yet. SeaKrait is optional; it does not replace Logmarq or require you to stop using other model providers.
Explore SeaKraitDocumentation and availability
Logmarq is not yet available as a supported public release. Product details describe work in development, not a release commitment. Documentation is not yet published.