Fig. 1 — Operating model
Cadres started with one patching problem: 30 to 60 minutes of human verification per server that added nothing but risk cover. Solving it properly meant building the rest of the stack the same way. Every product stands alone. Each ships with its own vendor integrations and does its job without the others. The bridges between them are optional. They are just better together.
Patching that captures state, acts, compares, and rolls back on drift. Monitoring, PAM, discovery, and security detection on one endpoint model, from datacenter servers to the ruggedized devices on the warehouse floor.
Incident, request, change, and problem on one ticket model. SLAs that do real calendar math, deterministic journey automations, chat-first intake, and change governance with CAB and freeze windows.
One normalized view of the network, multi-vendor by design, scored against standards your tenant defines. The plugin bridge means a new vendor is an integration, not a project. KEV and NVD vulnerability matching, health scoring, and traffic visibility.
Enterprise IdP and IGA. Passkey-first authentication with SAML and OIDC federation, access requests that execute downstream, JML lifecycle from HR events, and SOX-ready user access reviews with enforced separation of duties.
24 frameworks, deterministic control intelligence, SOX ICFR, internal audit, and vendor risk. AI drafts words here. It never issues verdicts. Auditors get a scoped portal, not a shared folder.
A SaaS-focused CRM and sales accelerator with finance on the same ledger, built so a single founder can run pipeline, billing, and close without an ops team. An 11-step close engine posts real adjusting entries, and payments integrate with your banks and payment vendors.
Sect. B — Doctrine
Twenty years running global infrastructure, on the receiving end of tools that never had to prove anything. These are the rules every Cadres product is built to.
Every automated action captures state before, acts, captures state after, and compares. Patching rolls back on drift. Close runs block on an unbalanced sheet. Nothing reports success it cannot show.
If a person does something repeatedly that a policy could handle, that is a design failure. People make decisions. Machines run checklists.
Control scoring, journey automations, and compliance evaluation run on fixed rules you can read. AI drafts and classifies where that helps. It never holds authority.
Tickets know about devices. Evidence draws from the systems that did the work. Nothing is reconciled by hand that the products can keep aligned themselves.
Yes. Start with the product that solves the immediate problem. Each one operates alone; the bridges between them are optional and can be enabled later.
No. Cadres is six distinct products with clear roles. Some teams will want more than one, and the products already know how to work together when that happens.
No. Portal is included as the identity layer for the other Cadres products. Wider IdP or IGA rollout is where Portal becomes its own product decision.
A focused setup around your environment, access model, and product fit. Trials are long-running by design; operational systems prove themselves over months of operation, not in a demo. You start with a Portal tenant and activate the products your evaluation needs.
Sect. D — Start Trial
Each trial includes Portal as the identity layer. From there, additional products can be enabled on the same tenant as your evaluation expands.
Start with a Portal tenant, then activate Relay, Beacon, Synapse, Meridian, or Keystone as the evaluation broadens.
Trial participants work directly with the people building the product.