Source access
Authorised APIs, credentials, network routes and source access logs remain subject to customer security and jurisdiction requirements.
SECURITY AND CUSTOMER CONTROL
Control the information, the persistent context and the reasoning route.
Axiomyx security begins with a declared end-to-end processing boundary: source access, derived evidence, AI inference, human review, logs and retention—not a single claim about where one model call runs.
APPROVED SOVEREIGNTY POSITION
Separate persistent evidence from AI reasoning.
Axiomyx separates enterprise data and persistent context from AI reasoning. Customers retain control of their information and can use stateless AI processing within their approved infrastructure, jurisdiction and retention rules.
That position depends on the complete route below. Stateless processing is one possible inference property; it does not by itself prove sovereignty. Every source, derived store, model endpoint and log path must meet the approved customer boundary.
Persistent evidence
Derived text, canonical objects, indexes, read models, provenance and operational logs have declared storage, access, backup, deletion and retention controls.
AI reasoning
Evidence supplied to inference, the model provider, outputs and human feedback remain inside an explicitly approved processing arrangement.
Current Connect preview boundary
Connect currently uses external OpenAI processing. Evidence requested for a Connect interaction can leave the local or customer-hosted evidence store for that external inference route. Customer-contained inference requires implementation and qualification for the selected model, infrastructure and security requirements.
PUBLICLY SUPPORTABLE CONTROLS
Controls for customer-hosted evidence infrastructure.
Customer-selected source boundary
Only folders, fields, records and connected sources selected by the customer participate in the evidence route.
Customer-controlled persistent context
Derived canonical objects, indexes, read models and provenance use declared customer storage, access, backup and retention controls.
Source-system authority
Original systems remain authoritative; their APIs, credentials, network path and access logging remain part of the security design.
Model-processing boundary
Prompts, evidence excerpts and outputs follow the selected AI provider's terms and the customer's approved inference arrangement.
Hash-verified customer packages and manifests
Official customer archives and release manifests have published SHA-256 identities so supported builds can be verified.
KMS-signed local entitlements
The runtime verifies KMS-signed entitlements without shipping the signing private key in customer packages.
Separated signing environments
Staging and production KMS duties remain separated; private signing material is not distributed.
Bounded activation
Licence keys are not persisted by the runtime, and the activation service applies request, timeout and rate boundaries.
Sanitised support
Support uses synthetic or minimised reproductions and customer-reviewed sanitised diagnostics.
HOST-ADMINISTRATOR THREAT BOUNDARY
The customer controls the machine.
A customer administrator or root user can technically replace the runtime, public-key registry, database, local clock or complete installation state. Axiomyx does not claim local licensing is tamper-proof against deliberate administrator modification.
Deliberate modification or circumvention is unsupported and remains subject to the software licence. Normal Private Edition operation does not require permanent online validation, hardware attestation or appliance-style DRM. Compensating controls include verified packages and manifests, signed local entitlements, support limited to verified official builds, bounded activation, monitoring where available and contractual restrictions.
DATA LOCATION BY EDITION
Persistent context remains aligned to the selected product boundary.
Originals need no wholesale migration, but each edition still creates and manages derived evidence inside a declared storage and lifecycle boundary.
PERSONAL
On your computer
Selected files and derived evidence remain under the installed product's customer-controlled boundary; external AI use retains its own provider boundary.
BUSINESS
In your environment
Customer-controlled identity and storage connect selected systems while derived objects, indexes and logs follow the deployment lifecycle.
ENTERPRISE
Inside negotiated controls
Source APIs, persistent evidence, inference, human review, logs and retention are defined and qualified together.