advanexus is a control and evidence layer for business-critical data operations. It connects governed execution, quality, versioned assets, analytics, controlled Python work, permissions and available evidence across an existing data stack.
Frequently asked questions
Direct answers, including the important boundary.
These answers summarize the public product contract. Capability Status and the relevant deep page remain authoritative when a connector, deployment or workflow needs more detail.
No. It is designed to work across existing systems while adding a shared scope, version, execution and evidence contract. Advanexus also provides controlled operational modules where that contract is needed.
No. Source, driver and deployment contracts decide metadata, preview, query, transfer, write, quality and analytics behavior for the exact connector environment.
Not necessarily. A virtual version freezes the SQL and schema contract, while later runs can see newer live source rows. Exact historical rows require a retained artifact or materialized snapshot contract.
No universal claim is made. Assurance evaluates explicit criteria and reports reproducible, partially reproducible, not reproducible or not assessed with the missing criteria visible.
No. Current packages are bounded technical exports with manifest and checksum verification. Signing, WORM controls, legal hold and legal admissibility are separate requirements.
What is advanexus?
advanexus is a control and evidence layer for business-critical data operations. It connects governed execution, quality, versioned assets, analytics, controlled Python work, permissions and available evidence across an existing data stack.
Does it replace a warehouse, orchestrator, BI tool or notebook?
No. It is designed to work across existing systems while adding a shared scope, version, execution and evidence contract. Advanexus also provides controlled operational modules where that contract is needed.
Are connector capabilities identical?
No. Source, driver and deployment contracts decide metadata, preview, query, transfer, write, quality and analytics behavior for the exact connector environment.
Does DatasetVersion freeze the data rows?
Not necessarily. A virtual version freezes the SQL and schema contract, while later runs can see newer live source rows. Exact historical rows require a retained artifact or materialized snapshot contract.
Is a result completely reproducible?
No universal claim is made. Assurance evaluates explicit criteria and reports reproducible, partially reproducible, not reproducible or not assessed with the missing criteria visible.
Is an Evidence Package digitally signed or legally conclusive?
No. Current packages are bounded technical exports with manifest and checksum verification. Signing, WORM controls, legal hold and legal admissibility are separate requirements.
Can Intelligence read the whole screen or act autonomously?
No. It uses registered page and object context, permission-filtered capabilities and typed tools. State-changing registered actions follow their confirmation or approval contract.
Does a completed Intelligence response prove that an action ran?
Not by itself. A response-only Turn may complete with an explanation. A state-changing result is supported only by a completed Action or tool result linked to the responsible canonical module.
Does saving a Pipeline schedule start automatic execution?
No. The current Schedule stores interval or cron intent, timezone and enabled state, but there is no active schedule dispatcher or reliable next-run calculation. A persisted PipelineRun is the execution record.
How does Advanexus protect tenant and Project context?
The server revalidates session registry identity, tenant state, active Project, membership and permission context at protected boundaries. Browser headers, visible controls and page state cannot grant scope.
Is Service Desk a full ITSM platform?
No. It provides bounded tenant and admin ticket communication with category, priority, status, assignment, public reply and internal-note behavior. Attachments, SLA automation, notifications, immutable ticket versions and full ITSM or CMDB workflows are not current capabilities.
Is the current deployment automatically production certified?
No. Production sign-off requires the exact revision, immutable images, target infrastructure and recorded migration, authorization, recovery, storage, connector and operational acceptance.
How does pricing work?
Scope follows systems, workloads, controls, deployment and operating responsibility rather than a public seat-only table. Approved written terms define inclusions, exclusions and price.
How should an existing user open the product?
Use Open live platform to continue to live.advanexus.com. Prospective users should discuss a critical flow rather than assume public self-service access.
Next step
Start with the flow that cannot afford ambiguity.
Bring the systems, owners, rules, delivery obligations and evidence requirements that matter.
Discuss a critical flow