advanexus

Pricing by controlled operating scope

Pay for the execution and evidence responsibility under control—not user seats.

Scope the systems, critical workflows, top-level executions, environments, retention, and operating responsibility involved. User access remains a security and administration requirement; it does not drive the public pricing recommendation.

Estimate the controlled scope Compare responsibility profiles

Four responsibility profiles

Start with the level of control the business outcome requires.

Prices are annual starting estimates billed annually. Capacity values describe proposed Order Form scope; they are not represented as a live usage or overage meter inside the current product.

Controlled Start

Starting from €48,000 per year

€4,000 / arithmetic monthly equivalent · billed annually

Put one bounded critical process or migration rehearsal under a complete control and evidence contract.

Review plan scope

Proposed contracted scope
A first accepted production process with customer-managed infrastructure.

  • Known inputs, versions, permissions and execution outcomes
  • Controlled movement, business checks and accepted data contracts
  • Governed analytics and project evidence context
  • Business-hours support for a bounded starting scope
One-time implementation
€18,000
Deployment planning allowance
€18,000
Tenants
1
Governed workspaces
3
Registered system connections
5
Controlled business processes or flows
10
Top-level controlled executions per year
50,000

Important boundary
Implementation, infrastructure and third-party consumption are separate.

Most common production scope

Operational Control

Starting from €96,000 per year

€8,000 / arithmetic monthly equivalent · billed annually

Extend the control and evidence path across several live processes, systems and business outputs.

Review plan scope

Proposed contracted scope
Recurring business-critical production with dashboards, SSO and controlled Python.

  • Multiple controlled processes and governed analytical outputs
  • Enterprise identity and domain-policy integration
  • Controlled Python runtime contract
  • Findings, Cases, Evidence Packages and operational follow-up
One-time implementation
€45,000
Deployment planning allowance
€30,000
Tenants
1
Governed workspaces
10
Registered system connections
15
Controlled business processes or flows
30
Top-level controlled executions per year
250,000

Important boundary
SAML, ANPy and evidence-package paths require target-environment acceptance.

Enterprise Evidence

Starting from €168,000 per year

€14,000 / arithmetic monthly equivalent · billed annually

Investigate supported outcomes across domains through tenant-wide Assurance and controlled Intelligence.

Review plan scope

Proposed contracted scope
Organizations that must explain change, execution, responsibility, exceptions and evidence.

  • Tenant Assurance Center and Evidence Explorer
  • User 360, Entity 360, Execution Story and bounded Graph
  • Version comparison, Controls, Integrity, Findings and Cases
  • Intelligence platform access; provider consumption excluded
One-time implementation
€90,000
Deployment planning allowance
€48,000
Tenants
1
Governed workspaces
25
Registered system connections
30
Controlled business processes or flows
75
Top-level controlled executions per year
1,000,000

Important boundary
Evidence Packages are technical exports; provider consumption and formal legal controls are separate.

Regulated & Mission-Critical

Starting from €288,000 per year

€24,000 / arithmetic monthly equivalent · billed annually

Design a dedicated or customer-controlled deployment and formal acceptance program.

Review plan scope

Proposed contracted scope
Regulated or mission-critical processes, multiple environments and scoped HA, recovery or residency.

  • Dedicated or customer-controlled architecture program
  • Scoped private networking, storage, HA/DR and residency
  • Extended retention profile for named object classes
  • System Assurance only after identity and gateway acceptance
One-time implementation
€180,000
Deployment planning allowance
€96,000
Tenants
1
Governed workspaces
50
Registered system connections
50
Controlled business processes or flows
150
Top-level controlled executions per year
5,000,000

Important boundary
The plan supports regulated operations; it does not confer certification or an unconditional SLA.

Controlled-scope estimator

Estimate the known operating footprint without a contact gate.

Select the published scope dimensions. The result updates locally, separates recurring and one-time costs, and identifies responsibility that still requires written acceptance.

Controlled operating scope
Show deployment and evidence fields

No data is sent to advanexus. User count does not determine this estimate.

What the buyer is scoping

Know what each value unit puts under control.

These units make a proposal reviewable. They are contractual planning dimensions, not a fabricated universal runtime billing ledger.

Tenant

One isolated organizational control and data boundary. Additional tenants require written architecture and price scope.

Registered system connection

One configured connection to a source or target system. A business system can require more than one configuration; capability remains connector-specific.

Controlled business process or flow

One agreed end-to-end path with a business outcome, owners, controls, failure path and evidence obligation.

Top-level controlled execution

One root run of an accepted process. Retries and child attempts are not presented as separate value units in the public estimate.

Production or non-production environment

A licensed operating scope with its own topology and acceptance boundary; managed infrastructure responsibility is priced separately.

Evidence and retention profile

The agreed review depth and lifecycle for named object classes. It does not imply universal WORM, legal hold, signing or regulatory retention.

Complete cost view

See what recurs, what happens once and what remains variable.

The approved Order Form, implementation statement and accepted support or SLA schedule remain the commercial authority.

Annual software

Responsibility profile, approved system/process/execution scope and selected software add-ons, after any eligible initial-term discount.

Deployment

Customer-managed at no platform surcharge, or a visible managed/dedicated planning allowance subject to topology acceptance.

Support

Standard business-hours support is included; enhanced support is a percentage of net annual software and requires an executed schedule.

Implementation

One-time discovery, configuration, integration, validation, recovery planning, enablement and operational handover. Migration Assurance is scoped here when required.

Premium and Mission Critical support, on-call coverage, availability targets and service credits apply only when written into an executed schedule after the target environment and operating model are accepted.

Extended retention is a contracted storage and lifecycle profile for named object classes. It is not an automatic claim of universal WORM, legal hold, KMS signing or regulatory retention.

Professional services

Add expertise only where the operating change needs it.

Day rates and packaged services are planning rates, exclusive of tax, travel and third-party fees.

Implementation engineer
€1,200 per day
Senior architect
€1,600 per day
Assurance and security specialist
€1,800 per day
Principal regulated specialist
€2,000 per day
Team training day
€3,500 per day
Discovery workshop
€7,500+
Two-week delivery sprint
€20,000–€30,000

Pricing questions

Read the commercial boundary before you compare totals.

Are these binding quotes?

No. They are non-binding public planning estimates. A written proposal and Order Form define the accepted scope, inclusions, exclusions and price.

Why is implementation separate?

Production value depends on system integration, permissions, controls, accepted outcomes, evidence coverage, recovery tests and operational handover—not only software access.

Is advanexus priced per user?

No. User access is governed and planned, but the public value model follows systems, controlled processes, top-level executions, environments, evidence obligations and accepted responsibility rather than seat count alone.

Are cloud, model-provider and third-party costs included?

No. Those costs remain excluded unless an executed proposal explicitly includes a named allowance or pass-through model.

Do capacity values represent automatic metering?

No. They are planning and Order Form allowances. The current product does not claim one universal cross-module billing ledger.

Is Regulated deployment a compliance certification?

No. It supports a scoped architecture and acceptance program for regulated operating requirements; it does not certify an organization or guarantee compliance.

Does a managed option include an SLA?

Only an executed SLA for an accepted topology can define availability measurement, exclusions, response objectives and service credits.

Non-binding planning estimate

Planning estimate, not an offer or invoice.

Values exclude VAT and other taxes, travel, provider consumption, cloud usage and unlisted third-party costs. Exchange rates, indexation, topology, data residency, acceptance criteria and legal terms can change the final proposal. Public estimates are reviewed periodically and may change without creating an obligation for either party.

Next step

Turn one critical process into an accepted control and evidence scope.

Bring the systems, owners, controls, execution volume, failure path, recovery expectation and evidence obligation. We will separate known public pricing from responsibility that needs written review.

Discuss a formal scope