Deployment models

Not by seats. But for the workflow where search, follow-up loops, and approval delays are costing the most money today.

Pilot

For teams that want to defuse the first expensive bottleneck with measurable goals instead of sitting through another non-committal demo.

On request/launch

including setup workshop

  • One prioritized confidential use case with clear success criteria
  • Two to four core sources for the first reliable working state
  • Initial answers, decisions, and approvals with evidence
  • Role and access model for the core team
  • Guided setup and enablement
  • Direct line to the product team
Plan pilot

Operations

For teams that want Cortex embedded across analysis, approval workflows, and handoffs so productivity does not depend on individuals.

On request/operations

ongoing use

  • Everything from pilot
  • More sources, more teams, more confidential working states
  • Decision history, evidence, open points, and next steps in daily work
  • Private deployment as required
  • Rollout support and admin enablement
  • Priority support
Plan operations

Sovereign

For companies with strict requirements around hosting, access, security reviews, approval workflows, and integration architecture.

On request/infrastructure

On-premise or private cloud

  • Everything from operations
  • On-premise or dedicated private environment
  • Security and architecture alignment with IT and leadership
  • Extended role, audit, approval, and governance models
  • Custom integration strategy
Plan sovereign deployment

Model comparison

From first ROI proof to fully integrated operations.

Pilot

On request/launch
Plan pilot

Operations

On request/operations
Plan operations

Sovereign

On request/infrastructure
Plan sovereign deployment
Prioritized starting point
✓
✓
✓
Number of core sources
2 to 4
Expanded
Custom
Answers and decisions with evidence
✓
✓
✓
Roles, audit, and approval workflows
✓
✓
✓
Private environment deployment
—
✓
✓
On-premise operations
—
Optional
✓
Implementation guidance
✓
✓
✓
Admin enablement
—
✓
✓
Security and architecture alignment
—
Optional
✓
Custom integration strategy
—
—
✓

FAQ

What determines the right model?

Mainly three things: how expensive the bottleneck is today, which sources need to be connected first, and what your IT team requires for operations and access control.

How does Cortex pay back?

Example: 12 people lose 30 minutes a day to search, follow-up loops, and approval delays. At 220 working days and 90 euros fully loaded cost per hour, that is around 118,800 euros a year. Those are exactly the leaks we prioritize in the pilot.

Can our data stay local?

Yes, if your environment requires it. That is exactly what the private and sovereign models are for, including local or dedicated deployment.

How does a pilot work?

With one prioritized confidential use case, a small number of core sources, and clear success criteria. The goal is not a demo, but a reliable first working state.

What is the next step?

We prioritize the critical workflow, review sources and security requirements, and then recommend the right deployment model for a controlled start.

Plan the deployment where Cortex pays back first.

Discuss deployment model