Start with the product or products you need now, then add more when the next operating problem is worth solving.
Architecture
Clear system ownership. Native product handoffs.
Cadres is built as products that integrate natively without collapsing into one ambiguous admin surface. Identity, audit and compliance, finance and CRM, and IT service and operations stay distinct so teams know which system owns what while operational context can still move cleanly between them.
Every trial starts with Portal as the identity layer, then extends into Meridian, Keystone, or RMM as needed.
System Ownership
Each product has a clean boundary.
The architecture is easier to understand when each product is judged by what it owns, what it consumes, and what it hands off to the rest of the suite.
Identity
Portal owns access, federation, and identity policy.
Portal is the identity control plane for authentication, lifecycle, and governed access across the Cadres suite.
- Owns tenant sign-in, upstream federation, provisioning, and lifecycle controls.
- Provides the shared identity layer used by every Cadres trial.
- Can extend into broader IdP and IGA coverage when teams need it.
Audit & Compliance
Meridian owns evidence, posture, and audit follow-through.
Meridian is where compliance programs, controls, evidence, reporting, auditor workflows, and SOX activity stay legible.
- Owns programs, frameworks, controls, evidence, reporting, and auditor collaboration.
- Consumes identity and operating context instead of relying on detached screenshots and spreadsheets.
- Produces remediation work that can stay tied to real operators and real systems.
Finance & CRM
Keystone owns commercial, customer, and financial truth.
Keystone keeps customer records, contracts, subscriptions, billing, accounting, and finance workflows in one operating system.
- Owns CRM, company, contract, subscription, billing, accounting, and finance state.
- Keeps commercial operations closer to product and customer reality.
- Gives growing teams a cleaner path from startup operations to larger revenue scale.
IT Service & Operations Management
RMM owns operational execution when IT is in scope.
RMM extends Cadres into service work, endpoint control, patching, automation, discovery, monitoring, and privileged operations.
- Owns service workflows, jobs, scripts, patching, discovery, monitoring, and PAM.
- Fits naturally when the business needs operational control over infrastructure and devices.
- Feeds operational state back into the rest of the Cadres operating model when required.
Cross-Product Handoffs
What moves across systems.
The architecture matters most at the handoff points. Cadres is designed so identity, commercial state, evidence, and operational actions do not become separate reconciliation exercises.
01
Tenant setup and access control
Portal establishes the tenant, the sign-in model, the governed access path, and the user context. Other products inherit that foundation instead of re-solving identity separately.
02
Customer, contract, and billing lifecycle
Keystone keeps commercial and financial state together so customer operations, subscriptions, contracts, and billing do not drift across disconnected systems.
03
Evidence, controls, and audits
Meridian turns administrative and operating state into evidence, review workflows, reporting, and remediation tracking without pushing teams back into screenshot-and-spreadsheet mode.
04
Operational execution and service work
RMM adds the IT execution surface when teams need service workflows, endpoint control, patching, discovery, monitoring, or privileged operations.
Rollout Paths
Where teams usually start.
The right starting point is usually determined by whichever operating system is already creating drag, risk, or unnecessary manual work.
Portal + Meridian
A practical early path when access control, audit readiness, and compliance pressure matter first. Portal handles identity, and Meridian turns that state into evidence and oversight.
Portal + Keystone
A cleaner path when contracts, subscriptions, billing, finance, and customer operations need to live closer together than a stitched CRM plus accounting stack allows.
Portal + Meridian + Keystone
Together, the three products cover identity, compliance, CRM, and finance in one connected operating base while keeping each system's boundary clear.
Add RMM when IT operations are real
RMM enters when the business also needs service management, endpoint control, patching, monitoring, or operational automation.
Documentation
Public manuals stay product-specific.
The architecture view explains ownership and handoffs. The manuals go deeper into deployment, administration, workflow coverage, and day-to-day operations for each product.
Portal Manual
Identity operations
Directory administration, federation operations, IGA, audit logs, deployment, migration tooling, and webhooks.
Meridian Manual
Audit and control operations
Programs, controls, evidence, audit workflow, trust center, reporting, remediation, connectors, and SOX coverage.
Keystone Manual
Commercial operations
CRM, company records, billing, accounting, finance, expenses, communications, banking, tax, and integration workflows.
RMM Manual
IT service and operations
Host and agent management, patching, monitoring, automation, PAM, ITSM, discovery, compliance, and vulnerability workflows.
Browse the full public manuals in Documentation.