Pricing
We are onboarding early customers.
Primcoat is not yet generally available. Rather than publish a price list we would have to revise, we are setting pricing alongside the first teams using it. Tell us what you are building and we will get you in.
Request access
Tell us which operating systems you build, which compliance regime you answer to, and where you publish. That is enough for us to know whether Primcoat helps you today or in three months — and we will tell you honestly which one it is.
Included for every customer
- CIS Level 1, CIS Level 2, and DISA STIG hardening profiles
- CVE scanning on every build, with fail-closed thresholds
- CycloneDX and SPDX software bills of materials
- Cosign signatures and SLSA build provenance
- The full certified software catalog — EDR, monitoring, identity, cloud agents
- Publishing to AWS, Azure, Google Cloud, VMware, OpenShift, and air-gapped targets
- The complete REST API, OpenAPI spec, and webhooks
You're on the list.
We read every one of these ourselves. We will come back to you about whether Primcoat helps you today or in three months — and if it is the latter, we will say so.
Questions
- Why is there no price on this page?
- Because we would rather publish a number we can stand behind than one we have to walk back. Primcoat is onboarding early customers now, and pricing is being set with them. Join the waitlist and we will talk about what your usage actually looks like.
- Which operating systems are supported?
- Ubuntu 22.04, 24.04 and 26.04; Debian 12; AlmaLinux 9 and Rocky Linux 9; RHEL 9; and Windows Server 2022 and 2025. Support for RHEL requires a Red Hat subscription — either ours or, where licensing permits, credentials you supply.
- Do I have to migrate to a different base OS?
- No. That is the point. Primcoat hardens the operating systems you already run and already support. It does not ask you to adopt a proprietary distribution to get a hardened image.
- How long does a build take?
- A Linux image built from an official cloud image typically takes 15 to 30 minutes. A Windows Server image built from an ISO takes 60 to 120 minutes. Conversion and upload add 5 to 20 minutes per destination. Every build shows its queue position and an estimated completion time.