Identity, compliance, CRM/finance, and service/operations stay closer together than they do in a conventional stitched-together stack.
Native Business Operations Suite
Operational systems built to work together.
Cadres is a business operations suite covering the systems most companies end up managing separately: identity and IGA, audit and compliance, CRM and finance, and IT operations management. Portal handles workforce access, provisioning, and lifecycle. Meridian keeps multi-framework GRC and SOX evidence in a real system instead of a spreadsheet. Keystone runs the full commercial lifecycle — CRM through year-end close, with product-authenticated billing and a nine-step close engine. RMM covers endpoint operations, ring patching, zero-knowledge PAM, and session accountability. Start with the product that solves the immediate problem and bring in more as the operating model calls for them.
Each trial includes Portal as the identity layer. Broader IdP or IGA rollout is a separate Portal decision, but the other products start there by default.
Downstream connectors
Portal ships nine downstream connector plugins covering M365, Google Workspace, Salesforce, GitHub Enterprise, ServiceNow, Atlassian, Slack, AWS IAM Identity Center, and Zoho Mail.
GRC frameworks
Meridian seeds SOC 2, ISO 27001, HIPAA, NIST CSF 2.0, GDPR, CCPA, COSO, and TISAX with ~100 cross-mappings. Add a framework and the system calculates how much your existing controls already cover.
Close engine steps
Keystone's close engine executes nine sequential steps in a single transaction — depreciation, accruals, FX revaluation, tax provision, deferred tax adjustments, bad debt estimation, and more — before snapshotting statements.
Business Operations
The systems most teams end up needing.
Identity, compliance, and CRM/finance show up quickly. Companies that run internal IT also need a service and operations platform. Cadres keeps those systems closer together under one model instead of scattering them across disconnected tools.
Identity
Cadres Portal
Portal is an enterprise-grade IdP and IGA platform with passkey-first authentication, SCIM provisioning, identity profiles with per-attribute provenance, an access graph with trust classification, nine downstream connector plugins, and JML lifecycle automation from HR events.
- Passkeys as a first-factor path; SAML and OIDC federation; auth policy with a preview-before-save step that surfaces readiness blockers before anything takes effect.
- IGA executes against Portal-native targets directly and against nine downstream systems through connector plugins.
- Migration tooling for Okta and Entra in two modes — first-run adoption and merge-into-existing — with compatibility assessment, TOTP transfer, and post-cutover evidence.
Explore Portal
Portal pairs cleanly with Meridian and Keystone when access governance, identity evidence, and billing authority need to stay aligned.
Audit & Compliance
Cadres Meridian
Meridian is a compliance and audit platform with multi-framework GRC, a deterministic Control Intelligence engine that scores fit and detects gaps across eight seeded frameworks, SOX ICFR with enforced separation of duties, and an external auditor portal backed by SHA-256 evidence verification.
- SOC 2, ISO 27001, HIPAA, NIST CSF 2.0, GDPR, CCPA, COSO, and TISAX with ~100 cross-mappings; adding a framework shows how much your existing controls already cover.
- External auditors access a read-only portal scoped to one cycle via OTP — every evidence download is SHA-256 verified and every page view is audit-logged with actor, path, and timestamp.
- When a finding is finalized or a control test fails, the remediation bridge opens a Jira ticket automatically; MAP items auto-advance when Jira marks a ticket done.
Explore Meridian
Meridian pairs naturally with Portal and Keystone when identity posture and financial operations need to be inside the same evidence model.
Finance & CRM
Cadres Keystone
Keystone is finance and CRM on one ledger: pipeline through closed-won, product-authenticated Stripe billing that keeps contract authority in Keystone, invoicing with GL posting, and a close engine that runs nine sequential accounting steps and posts real adjusting entries before snapshotting statements.
- CRM with finance-native context: customer workspaces show every product subscription with sold-contract details; deal conversion creates the subscription and emits product_contract.changed; churn risk alerts dispatch when health scores cross the threshold.
- Downstream products redirect to Keystone-hosted Stripe checkout without receiving Stripe credentials, price IDs, or subscription authority; plan changes require a durable contract change request before any mutation.
- Three-way PO matching, bank reconciliation, multi-entity consolidated statements with intercompany eliminations, quarterly tax estimates from live GL data, and an annual reporting package with 1099 candidates and K-1 summaries.
Explore Keystone
Keystone pairs naturally with Portal and Meridian when identity-linked billing, access governance, and audit evidence need to share the same commercial truth.
Cadres Model
Different products. Shared discipline.
Cadres is not trying to pretend four separate categories are really one SKU. The point is simpler: buy the product you need, or use more than one and keep more of the business stack under a shared operating discipline.
01
Operate the environment.
RMM handles ring patching with drift-triggered rollback, zero-knowledge PAM where nobody — not even the operator — knows the credential, workflow automation with approval gates, and full session recording so every privileged action has an answer.
02
Control access and compliance.
Portal maintains an access graph with provenance and trust classification across every edge — direct roles, IGA grants, group membership, guest access. Meridian keeps control evidence in a real system: deterministic scoring, enforced separation of duties, and auditor access scoped to what they need without email and shared folders.
03
Keep commercial and audit truth aligned.
Keystone keeps CRM, billing, and the general ledger on the same data — invoices post to the GL immediately, the close engine posts real adjusting entries, and contract authority stays in one place rather than splitting between a billing tool and a spreadsheet. Meridian evidence draws from the same operating record rather than a manual screenshot layer.
Clear product roles
Shared operating discipline
Operator-safe tenancy
Native integration
Leadership Fit
Built for the people who have to own the answer.
The message has to land with executives and still survive technical scrutiny. That means clear scope, honest rollout staging, and products that map to accountable leadership functions.
CIO / CTO
One architecture instead of stacked exceptions.
Cadres connects operational execution, identity, finance/CRM, and auditability without integrations that break silently. RMM feeds operational evidence into Meridian. Portal access state drives what Keystone can activate. The operating model is consistent across all four products rather than negotiated tool by tool.
Security & Identity
Identity with governance that executes downstream.
Portal covers federation, SCIM provisioning, identity profiles with per-attribute provenance, JML lifecycle from HR events, access reviews with SoD enforcement, and nine connector plugins with real grant/revoke. The access graph is a live operational record, not a report generated before the audit.
GRC / Internal Audit
Evidence that can stand up to review.
Meridian's close engine for compliance is deterministic: five-signal control scoring, SOX ICFR with enforced separation of duties, SHA-256 evidence verification, and a §302 sub-certification process where only the named respondent can complete or decline. Auditors get a scoped read-only portal with a page-view trail — not a shared folder and an email thread.
CRO / Revenue Ops
Finance and CRM on one ledger.
Keystone connects pipeline, deal conversion, subscription provisioning, invoicing, and period close without syncing across separate tools. Contract authority stays in Keystone — downstream products hand off to Stripe-hosted checkout without ever holding credentials or subscription authority. Revenue recognition and deferred revenue schedules are tracked against sold-contract line items, not reconstructed at year end.
Full Portfolio
Four products. Clear buying paths.
Identity, audit/compliance, CRM/finance, and IT Service & Operations Management under one integrated operating model. Start with what solves the immediate problem and bring in more as needed.
Identity
Portal
Enterprise-grade IdP and IGA: passkey auth, SCIM provisioning, identity profiles, access graph, nine downstream connector plugins, JML lifecycle, and migration tooling for Okta and Entra.
Portal details
Audit & Compliance
Meridian
Multi-framework GRC with deterministic control intelligence, SOX ICFR, external auditor portal with SHA-256 evidence verification, risk register, access reviews, and Jira remediation bridge.
Meridian details
Finance & CRM
Keystone
CRM, billing with Stripe handoff, invoicing with GL posting, a nine-step close engine, three-way PO matching, multi-entity consolidation, and an annual reporting package.
Keystone details
IT Service & Operations Management
RMM
IT Service & Operations Management for patching, workflows, service desk, discovery, PAM, monitoring, and endpoint operations.
RMM detailsFAQ
What an evaluation should make clear.
Can we start with just one Cadres product?
Yes. Start with the product that solves the immediate problem. The point of Cadres is not to force a bundle before the first buying decision makes sense.
Is Cadres one platform with four modules?
No. Cadres is four distinct products with a shared operating discipline. Some teams may want more than one, but the products are designed to keep clear roles.
Where does RMM fit?
RMM covers the IT Service & Operations Management layer: patching, automation, service desk, discovery, monitoring, and privileged operations. It remains central to the Cadres story.
Why group Portal, Meridian, and Keystone together at all?
Identity, compliance, and CRM/finance are foundational systems that often end up fragmented. Cadres keeps them under one operating model instead of scattering them across disconnected tools.
Is Portal always a separate paid product?
No. Portal is included as the identity layer for the other Cadres products. Wider IdP or IGA rollout is where Portal becomes its own paid product decision.
Are Portal, Meridian, and Keystone only for startups?
No. Together they are especially useful for teams that want stronger operating maturity early. Separately, each product solves a broader business problem in its own category.
What does a trial look like?
It should be a focused setup around your environment, access model, workflow priorities, rollout timing, and product fit. The goal is to get the right tenant and the right starting product in front of you quickly.
Start Trial
Start a self-service trial.
Each trial includes Portal as the identity layer. From there, additional products can be enabled on the same tenant as your evaluation expands. The goal is to let teams explore the suite directly before they need a long buying motion.
Trial path
Start with a Portal tenant, then activate Meridian, Keystone, or RMM as the evaluation broadens.
Portal scope
Portal is included as the identity layer for the other products. If you want broader IdP or IGA rollout, say that directly and we will scope Portal on its own terms.